FYI ...
Begin forwarded message:
From: Martin Hollmichel <[EMAIL PROTECTED]>
Date: April 17, 2006 11:06:17 AM EDT
To: [email protected]
Cc: [EMAIL PROTECTED]
Subject: [project leads] A proposal for the planning process for
OpenOffice.org 3.0
Reply-To: [EMAIL PROTECTED]
Hi,
as you might already have heard and experienced the release model of
OpenOffice.org is changing a little bit.
The main tree is now open for UI Changes and new Features so that
there is the possibility to have a new feature integrated for a new
release within a few months.
The plan is to have the source code ready for a release every three
months:
Final bits of release: last Thursday of Feb., May, August and
November, last cws integration will be two week earlier, UI and
Feature freeze seven weeks before the final bits. The recommended date
for the integration of new feature and big UI changes will be around
12 weeks before the final bits so that there will be enough time for
early checking.
At this moment we still have not a detailed plan for a 3.0 release
date.
The release model turns from a 18-24 month time boxed model into an
train model: new feature will be integrated into the product when
there are ready and finished. This give us the possibility to release
new functionality as soon as possible and there will be no big drama
if a feature misses a major release. To make it clear that new
features will be in the product I would like to change the versioning
scheme from 2.0.4 on into 2.4 (August '06 release), 2.5 in November
'06 then ... etc.
For this reason I would like to introduce an additional target
milestone in IssueTracker named "2.x". This target milestone can be
used as "targeted as to be integrated as soon as possible" and avoids
the drifting of issues for 2.0.2 to 2.0.3 to 2.0.4.... . The actual
target milestone 2.0.x will then set if the item is ready for
integration or a must have for the next release. The 3.0 target stays
reserved for issues we want to have for a "big bang" release of for
features which makes a restructuring of the product necessary (I can't
think of such an feature in the moment but those may exist ;) ).
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
