jberry 2005/02/18 13:12:18
Modified: c/doc releases_plan.xml
Log:
Update release plan with tenative 3.0 list
Revision Changes Path
1.22 +193 -20 xml-xerces/c/doc/releases_plan.xml
Index: releases_plan.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/releases_plan.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- releases_plan.xml 29 Sep 2004 03:03:45 -0000 1.21
+++ releases_plan.xml 18 Feb 2005 21:12:18 -0000 1.22
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
<!--
- * Copyright 1999-2004 The Apache Software Foundation.
+ * Copyright 1999-2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
@@ -21,26 +21,199 @@
<s2 title="&XercesCName; Future Releases Plan">
<p>This document highlights the release plan for &XercesCName;.</p>
+
<s3 title="Current Status"><p>&XercesCName; 2.6.0 - released on September
29, 2004.</p></s3>
-<s3 title="Next Target Release"><p>&XercesCName; x.y.z - </p></s3>
-<s3 title="&XercesCName; Features list">
-<p> The following table lists the TODO items for &XercesCName; x.y.z. It
does not include fixing
-bugs that are opened in Jira; unless such Jira bug involves a major
development
-effort and requires an architectural redesign, or is an enhancement
suggestion.</p>
-
-<table>
- <tr>
- <th>Features</th>
- <th>Development Volunteer</th>
- </tr>
-
-
- <tr>
- <td>XML Catalog Support</td>
- <td>unassigned</td>
- </tr>
-
-</table>
+
+<s3 title="Next Target Release">
+ <p>The &XercesCName; team is currently working on plans for future
releases.
+ At present, we believe there will be a 3.0 release with new
functionality
+ targeted roughly at the second half of 2005. As a change in the major
version allows us
+ to break source compatibility, we are trying to take our time in order
to
+ break now what needs to be broken. There is some chance that changes
breaking
+ source compatibility will not be needed, and that "3.0" features will be
+ released in the 2.x line.</p>
+ <p>Further releases in the 2.x line are anticipated concurrent with 3.0
development
+ in order to fix issues or bugs in 2.6. Once 3.0 is released, we may
also issue
+ further 2.x releases as needed by the community.</p>
+ <p>&XercesCName; 2.y.z - as needed to address bugs or other issues.</p>
+ <p>&XercesCName; 3.0 - Targetted roughly for second half of 2005.</p>
+</s3>
+
+<s3 title="&XercesCName; 3.0 (tentative) Features list">
+
+ <p>The following table lists the potential TODO items for &XercesCName;
3.0.
+ It does not include fixing bugs that are opened in Jira; unless such
Jira bug
+ involves a major development effort and requires an architectural
redesign,
+ or is an enhancement suggestion,</p>
+
+ <p>This list tracks current ideas and developer sign-up for 3.0
features. Some items
+ on this list have no vontunteer. Items that have no volunteer will
receive no
+ development attention and therefore will not become part of 3.0. If you
would
+ like to volunteer for these or other items please email the
&XercesCName; mailing
+ list</p>
+
+ <table>
+ <tr>
+ <th>ID</th>
+ <th>Feature Description</th>
+ <th>Volunteer</th>
+ </tr>
+
+ <tr>
+ <td>1</td>
+ <td>Reorganization of public/private includes</td>
+ <td></td>
+ </tr>
+
+ <tr>
+ <td>2</td>
+ <td>Revisiting/sanity checking of install locations</td>
+ <td></td>
+ </tr>
+
+ <tr>
+ <td>3</td>
+ <td>Refactoring of x-platform support</td>
+ <td>
+ <ol>
+ <li>Initial cut - James</li>
+ <li>Basic posix support - James</li>
+ <li>Mac re-port/test - James</li>
+ <li>Windows re-port/test - Alberto</li>
+ <li>Linux re-port/test<br />
+ Gareth<br />
+ Alberto [VMWare (Red Hat 9, Red
Hat 7.3) and I can add more]<br />
+ Scott Cantor [test]<br />
+ David [w/ xlC]
+ </li>
+ <li>Solaris - Scott Cantor [test]</li>
+ <li>Cygwin - Neil</li>
+ <li>MingGW - Alberto</li>
+ <li>AIX - David</li>
+ <li>OS390 - David</li>
+ <ol>
+ </td>
+ </tr>
+
+ <tr>
+ <td>4</td>
+ <td>A true autoconf based build infrastructure</td>
+ <td>James,
+ Jason Stewart,
+ Scott Cantor,
+ John Snelson
+ </td>
+ </tr>
+
+ <tr>
+ <td>5</td>
+ <td>Add a libcurl based NetAccessor</td>
+ <td>James - as time permits</td>
+ </tr>
+
+ <tr>
+ <td>6</td>
+ <td>DOM 3.0 support</td>
+ <td>Alberto,
+ Gareth
+ </td>
+ </tr>
+
+ <tr>
+ <td>7</td>
+ <td>XPath</td>
+ <td></td>
+ </tr>
+
+ <tr>
+ <td>8</td>
+ <td>XInclude</td>
+ <td>Gareth,
+ Caroline Rioux
+ Graham Innocent
+ </td>
+ </tr>
+
+ <tr>
+ <td>9</td>
+ <td>Add a ACE-based NetAccessor</td>
+ <td>Alberto - as time permits</td>
+ </tr>
+
+ <tr>
+ <td>10</td>
+ <td>Add RelaxNG support</td>
+ <td>(Michael Fuller -- would provide some help)</td>
+ </tr>
+
+ <tr>
+ <td>11</td>
+ <td>Audit/Update of XML Schema support.</td>
+ <td>David</td>
+ </tr>
+
+ <tr>
+ <td>12</td>
+ <td>Const signature changes. [783, 1153, 1223]</td>
+ <td>David</td>
+ </tr>
+
+ <tr>
+ <td>13</td>
+ <td>XML Catalog Support</td>
+ <td></td>
+ </tr>
+
+ <tr>
+ <th></th><th colspan='2'>Features/APIs to be
removed</th>
+ </tr>
+
+ <tr>
+ <td>20</td>
+ <td>Remove Deprecated DOM altogether -
+ Whether we should actually do this is still
still being debated.
+ </td>
+ <td>Gareth</td>
+ </tr>
+
+ <tr>
+ <td>21</td>
+ <td>Remove and/or update deprecated enums</td>
+ <td>Gareth</td>
+ </tr>
+
+ <tr>
+ <td>22</td>
+ <td>Remove non-thread-safe psvi methods</td>
+ <td>Gareth</td>
+ </tr>
+
+ <tr>
+ <td>23</td>
+ <td>Remove Mac OS Classic Support</td>
+ <td>James</td>
+ </tr>
+
+ <tr>
+ <td>24</td>
+ <td>Remove OS/2 (or update it)</td>
+ <td>Alberto</td>
+ </tr>
+
+ <tr>
+ <td>25</td>
+ <td>Remove Borland C++ 4, CodeWarrior, VACPP40 and
Unsupported from Windows platform</td>
+ <td>Alberto</td>
+ </tr>
+
+ <tr>
+ <td>26</td>
+ <td>Audit/Potential removal of all deprecated
methods</td>
+ <td>David</td>
+ </tr>
+
+ </table>
+
</s3>
</s2>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
