You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by cr...@apache.org on 2001/11/16 09:43:23 UTC
cvs commit: xml-cocoon2/documentation/xdocs/plan release.xml book.xml index.xml
crossley 01/11/16 00:43:23
Modified: documentation/xdocs/plan book.xml index.xml
Added: documentation/xdocs/plan release.xml
Log:
Add new document for "Release plan".
Revision Changes Path
1.2 +1 -0 xml-cocoon2/documentation/xdocs/plan/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/plan/book.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- book.xml 2001/11/13 04:50:10 1.1
+++ book.xml 2001/11/16 08:43:23 1.2
@@ -9,6 +9,7 @@
</menu>
<menu label="Planning Documents">
+ <menu-item label="Release Plan" href="release.html"/>
<menu-item label="To Avalon" href="to-avalon.html"/>
<menu-item label="Documentation" href="doc.html"/>
<menu-item label="Entity Catalogs" href="catalog.html"/>
1.2 +2 -0 xml-cocoon2/documentation/xdocs/plan/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/plan/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 2001/11/13 04:50:10 1.1
+++ index.xml 2001/11/16 08:43:23 1.2
@@ -44,6 +44,8 @@
<s1 title="Topics and Issues">
<ul>
+ <li><link href="release.html">Release Plan</link>
+ - major things to do before the 2.0 release</li>
<li><link href="to-avalon.html">Moving some Components to Avalon</link></li>
<li><link href="doc.html">Documentation</link>
- revisions and additions are required</li>
1.1 xml-cocoon2/documentation/xdocs/plan/release.xml
Index: release.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../dtd/document-v10.dtd">
<document>
<header>
<title>Release Plan 2.0</title>
<subtitle>Planning Documentation</subtitle>
<authors>
<person name="David Crossley" email="crossley@apache.org"/>
</authors>
</header>
<body>
<s1 title="Preparation for release of Apache Cocoon 2.0">
<p>The 2.0 final release is scheduled for the end of November 2001.
</p>
<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.
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.
update jars.xml, ensure proper banner in *.java header,
verify the current LICENSE* files, ensure that external
components have suitable licensing requirements.
]]></source>
</s1>
</body>
</document>
----------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org