We should have made a branches/1.1.0 copy from 1.1 , which could then be moved to Tags once the voting is done. If a major bug needed fixing due to a -1, then you fix it in branches/1.1.0 and branches/1.1, respin the 1.1.0 build, revote and then move it to Tags. That would let people continue working on branches/1.1 with known items that should go into 1.1.1 and gives you a way to fix any last minute 1.1.0 release bugs if needed....
-Donald David Blevins wrote:
On Jun 15, 2006, at 8:40 AM, Aaron Mulder wrote:Why not copied to tags/1.1.0 so that branches/1.1 would continue to be available for 1.1.1-SNAPSHOT? That would have the advantage of not disrupting anyone's work if there was code that wasn't checked in pending 1.1.1,[edit]Are there any advanatages at all to moving the branch away?Exactly that, to make sure people don't "move on" and checkin work on branches/1.1 for 1.1.1 where there is a freeze on branches/1.1 for preparing v1.1 (which may not pass it's vote and have to be redone).Probably should have created the 1.1.1 branch immediately, no biggie. I went ahead and made now.plus it wouldn't require everyone to do a full checkout of the identical code for 1.1.1.It doesn't require a full checkout. svn switch https://svn.apache.org/repos/asf/geronimo/branches/1.1.1 -David
smime.p7s
Description: S/MIME Cryptographic Signature
