cziegeler 2002/09/26 04:51:25
Modified: src/documentation/xdocs/plan release.xml
Log:
Changing release plan
Revision Changes Path
1.10 +28 -43 xml-cocoon2/src/documentation/xdocs/plan/release.xml
Index: release.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/plan/release.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- release.xml 22 Aug 2002 02:59:32 -0000 1.9
+++ release.xml 26 Sep 2002 11:51:25 -0000 1.10
@@ -15,13 +15,16 @@
<s1 title="Timeframe">
<p>This is the current time frame for the next releases:</p>
<ul>
- <li>September 2002 : Release date for 2.0.4 (bug fix release)</li>
- <li>August/September 2002 : Release date for 2.1 Alpha 1</li>
+ <li>October 2002 : 2.0.4 (bug fix release)</li>
+ <li>October 2002 : 2.1 Alpha</li>
+ <li>End of November 2002 : 2.1 Beta 1</li>
</ul>
</s1>
- <s1 title="ToDo List">
- <p>For 2.1 Beta 1:</p>
+ <s1 title="Version 2.0.4">
+ <p>See the todo list for more information.</p>
+ </s1>
+ <s1 title="Version 2.1 Beta 1">
<ul>
<li>apply patches</li>
<li>test flowmap + docs + etc</li>
@@ -39,48 +42,30 @@
strategic stuff has been a set a bit aside due to lack of time.</li>
</ul>
</s1>
-
- <s1 title="Preparation for the next release of Apache Cocoon">
-
- <p>
- The following is extracted from the thread
- [C2]: Release Candidate 2 ... 2001-10-29
- </p>
-
-<source><![CDATA[
-> The question is now, what has to be done until then?
->
-> 1) We have many open bugs in bugzilla. These must be reviewed
-> and then solved (or declared invalid etc).
->
-> 2) Documentation updates (this area lacks most)
-> We could move this to the final release.
+ <s1 title="Version 2.2 Beta 1">
+ <p>Although this version might be long in the future, we already have some
plans...</p>
+ <ul>
+ <li>Design and implement blocks</li>
+ <li>Move to a new Avalon container implementation (Merlin, Fortress or
whatever)</li>
+ </ul>
+ </s1>
+ <s1 title="General tasks for a release">
+<ul>
+<li>We have many open bugs in bugzilla. These must be reviewed
+ and then solved (or declared invalid etc).</li>
+<li>Documentation updates (this area lacks most).
+ We could move this to the final release.
Documentation must be happening all the time, and not left
-until last.
-
-> 3) Decide what to backport from the 2.1 head.
-> I'm +1 on removing the CodeFactories completly in 2.0, too.
-> This would avoid any backcompatibility problems.
->
-> 4) Layout the distribution
-> This is a point we haven't discussed yet. Currently our
-> distribution is a mixture of a source and a binary one.
-> We deliver the source and a compiled version, but in order
-> to run Cocoon, the user has to build a war file.
-> I propose to split this: one source distribution which is
-> similar to the current one but without the precompiled
-> cocoon jar and a binary distribution containing only the
-> war file. This war file should work in most servlet engines,
-> perhaps not in all.
->
-> So anything missing here?
-
-5) Ensure that licensing requirements have been met.
+until last.</li>
+<li>Checking what to backport. We have components in the
+latest developer versions, which might find their way into
+the bugfix version line (2.0.x).</li>
+<li>Ensure that licensing requirements have been met.
update jars.xml, ensure proper banner in *.java header,
verify the current LICENSE* files, ensure that external
- components have suitable licensing requirements.
-]]></source>
-
+ components have suitable licensing requirements.</li>
+<li>Everything we forgot...</li>
+</ul>
</s1>
</body>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
