Release Plan
http://xml.apache.org/http://www.apache.org/http://www.w3.org/

Main

Overview
Planning Overview

Documentation
Overview
Changes
To Do
Issues
Fix broken links

Other Planning
Release Plan
Cocoon Samples
Entity Catalogs
Proposed TOC

Timeframe

This is the current time frame for the next releases:

  • September 2002 : Release date for 2.0.4 (bug fix release)
  • August/September 2002 : Release date for 2.1 Alpha 1
ToDo List

For 2.1 Beta 1:

  • apply patches
  • test flowmap + docs + etc
  • documentation to forrest format
  • finish the document Updating Cocoon which describes the major changes since 2.0.2
  • finish the refactoring of samples
  • finish to move scratchpad stuff in main trunk
  • switch to LogEnabled
  • extended sitemap variable substitution, i.e. {request:foo}.
  • more tests and examples on the flowmap. Seems to me that this strategic stuff has been a set a bit aside due to lack of time.
Preparation for the next release of Apache Cocoon

The following is extracted from the thread [C2]: Release Candidate 2 ... 2001-10-29

> 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.
Copyright © 1999-2002 The Apache Software Foundation. All Rights Reserved.