Release Plan

Return-Path: Delivered-To: apmail-cocoon-cvs-archive@www.apache.org Received: (qmail 62077 invoked from network); 27 May 2004 12:34:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 27 May 2004 12:34:49 -0000 Received: (qmail 99782 invoked by uid 500); 27 May 2004 12:34:49 -0000 Delivered-To: apmail-cocoon-cvs-archive@cocoon.apache.org Received: (qmail 99695 invoked by uid 500); 27 May 2004 12:34:47 -0000 Mailing-List: contact cvs-help@cocoon.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@cocoon.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list cvs@cocoon.apache.org Received: (qmail 99606 invoked by uid 500); 27 May 2004 12:34:47 -0000 Delivered-To: apmail-cocoon-2.1-cvs@apache.org Received: (qmail 99571 invoked by uid 98); 27 May 2004 12:34:46 -0000 Received: from cziegeler@apache.org by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(209.237.227.194):. Processed in 0.133341 secs); 27 May 2004 12:34:46 -0000 X-Qmail-Scanner-Mail-From: cziegeler@apache.org via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(209.237.227.194):. Processed in 0.133341 secs) Received: from unknown (HELO minotaur.apache.org) (209.237.227.194) by hermes.apache.org with SMTP; 27 May 2004 12:34:46 -0000 Received: (qmail 61976 invoked by uid 1260); 27 May 2004 12:34:42 -0000 Date: 27 May 2004 12:34:42 -0000 Message-ID: <20040527123442.61975.qmail@minotaur.apache.org> From: cziegeler@apache.org To: cocoon-2.1-cvs@apache.org Subject: cvs commit: cocoon-2.1/src/documentation/xdocs/plan roadmap.xml release.xml book.xml X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N cziegeler 2004/05/27 05:34:42 Modified: src/documentation/xdocs/plan release.xml book.xml Added: src/documentation/xdocs/plan roadmap.xml Log: Add roadmap doc Revision Changes Path 1.15 +1 -19 cocoon-2.1/src/documentation/xdocs/plan/release.xml Index: release.xml =================================================================== RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/plan/release.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- release.xml 19 May 2004 11:33:35 -0000 1.14 +++ release.xml 27 May 2004 12:34:41 -0000 1.15 @@ -31,24 +31,6 @@ - -

This is the current time frame for the next releases:

May, 24th 2004 : 2.1.5 (maintenance release)
Not schedulded yet : 2.2 Milestone 1
On request : 2.0.5 (maintenance release)

- - - -

Although this version might be long in the future, we already have some plans...

Design and implement blocks
Move to a new Avalon container implementation (Fortress)

The updating to 2.2 document contains more information - on how to prepare your application for the next major release.

We have many open 1.5 +1 -0 cocoon-2.1/src/documentation/xdocs/plan/book.xml Index: book.xml =================================================================== RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/plan/book.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- book.xml 8 May 2004 08:57:55 -0000 1.4 +++ book.xml 27 May 2004 12:34:41 -0000 1.5 @@ -26,6 +26,7 @@ +
1.1 cocoon-2.1/src/documentation/xdocs/plan/roadmap.xml Index: roadmap.xml ===================================================================
Release Plan Planning Documentation
This is the current time frame for the next releases:
- July/August 2004 : 2.1.6 (maintenance release)
- Not schedulded yet : 2.2 Milestone 1
In general, the next Cocoon version 2.2 can be seen as the "consolidation version". In the past a lot of new features, blocks and components were added which resulted in the fact that in some places concurring solutions were developed that could be combined a little bit.

One good example is form handling where we now are concentrating on CForms. We will try this in other areas as well. Of course this does not mean that we won't add new features to 2.2, but we try to consolidate what we currently have as well.

The follow is a list of items that are planned for the next minor release of Cocoon (2.2). This is a dynamic list that might change over time :)

We have come to the conclusion that real blocks might take a little bit longer than we have expected. So we agreed on not affecting the current development of Cocoon by the real blocks development. Which means we have to develop the blocks system separately from Cocoon until the block system is stable enough to be "merged" into Cocoon. This allows us to release new versions of Cocoon (like 2.2) without waiting for blocks to be working/finished.
- Official Versioning Guide (will be published soon).
- Move source repository to Subversion.
- Virtual sitemap components.
- First finished version of CForms.
- Deprecate XSP (and provide a viable alternative).
- Cleaning up the caching/store mess.
- Remove deprecated blocks etc.
- Deprecate blocks that haven't been maintained in a long while or don't serve any evident purpose. Web3, apples, python, php, asciiart might be some candidates. We will decide this on a case-by-case basis.
- Differentiate between blocks that provide a service to other blocks and blocks that contain just samples or small applications built upon cocoon (petstore, tour, linotpye). Maybe "samples-only" blocks should be a separate download.
- Review the implications and the implementation of pooling.
- Reduce unneeded dependencies on Avalon, where possible.
- Review the logging framework. Log4j is the de-facto standard and we have blocks that complain if Log4j is not properly configured, so let's accept it and stop reinventing the wheel.
- Drop that Excalibur datasource. Components that need a DS should get one provided by the container via JNDI. If we don't have a container (running via the CLI, for instance), let the environment provide one and bind it to a JNDI namespace.
- Write more tests (you knew this one was coming ;-) ).
The updating to 2.2 document contains more information on how to prepare your application for the next mino release.
We already have plans for further versions of Cocoon that might be long in the future...
- Design and implement blocks.
- Move to a new Avalon container implementation (Fortress).