Hi all,
I'd like to make a number of "proposals" here for a release schedule.
Please comment and/or vote +- on each one of the items below.
Thanks,
-- leif
1. Feature freeze for 2.0.0 is 2/22 2010. Features that have not been
committed before this date will not make it into the 2.0.0
release. We create the 2.0.0 release branch on this day, and trunk
should be considered frozen the entire day (or until we declare it
open again on the mailing list).
2. We start preparing for an alpha release, following the release
management guidelines
(http://incubator.apache.org/guides/releasemanagement.html). This
includes the PPMC voting on the release, and bring it to IPMC for
voting as well. This might take several iterations until we get a
release approved, so we can't schedule much beyond this. Any bugs
filed to pass the IPMC release approval will obviously have to be
fixed on both 2.0 release and trunk.
3. On 2/23 2010, trunk is considered open for development again. John
and George can start merging dev branch to trunk at their
convenience now.
There are a number of steps for us to "resolve" in that guideline above,
including the format of the STATUS file, and how to branch Paul
suggested we do the branching and tagging like copy trunk to
branches/2.0.x, then copy branches/2.0.x to tags/2.0.0. The release
process above also has major dependencies on us closing all the bugs
related to release, including RAT reports, any incompatible licenses and
the TM issue.
