tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: Time to organise svn
Date Fri, 05 Oct 2007 03:25:18 GMT
William A. Rowe, Jr. wrote:
> Actually, the way it typically works at httpd-space (which your new
> policy is based on) is that you would next create 6.1.0 as a forever
> development branch.  Committers apply each patch they believe belongs
> to the 6.2.0 release, and things are removed and readded as various
> votes and discussions proceed.

OK. I think I have it now. Does the the following make more sense?

svn cp

svn cp

and then
- Make all changes in trunk (CTR)
- Port those API changes we want in 6.2.x from trunk to 6.1.x (RTC)
- A beta release of 6.1.x
- Once we are happy with 6.1.x, freeze it, create 6.2.x and do a
stable release
- Continue to port non-API modifying changes from trunk to 6.2.x as RTC
- At some point in the future, trunk is branched to form 6.3.x which
is used as the basis for 6.4.x or 7.0.x


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message