I think it's okay to create a branch now and agree on a code freeze
(except severe bugs or doc patches) on the branch once the first RC is out.
And yes, discouraging big commits on trunk during the freeze is always a
good idea.
Michael
On 11/15/09 1:42 PM, Mark Miller wrote:
The reason I created the branch at the last minute was because the 2.9
release was so large. Having to commit the release check/fix flurry of
activity against trunk and a branch would have been quite a pain. The
hope was also to keep devs on making the release right, rather than
continue with trunk dev. I don't think we have the same concern with 3.0
though. You can really do whatever makes sense with consensus - I waited
to create the branch because I brought up the concern on the list and
got agreement without any disagreement. It was a one time discussion for
2.9 though - I wouldn't feel bound by anything that happened during the
2.9 release for 3.0.
- Mark
Uwe Schindler wrote:
Hallo Committers,
I want to start the release process tomorrow. The question:
Mark Miller created the branch after the release of 2.9.0, but the release
TODO says, that I should create the branch before the first RC. Robert also
wanted this today, because it would allow us to work for 3.1, while the
release process of 3.0 is running (but please no heavy commits like touching
all tests for junit4, it makes merging bugfixes to 3.0 and 2.9 harder).
So I would branch 3.0 tomorrow, so bug fixes in the RC must be also done on
the branch. I will also change the version numbers in trunk (3.1-dev) and
create a new trunk-BW-branch (30_bw_tests, also remove the Java 1.4 switch
for compiling BW branch).
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
