On Friday, March 7, 2003, at 08:12 PM, Daniel Rall wrote:
Geir Magnusson Jr. <[EMAIL PROTECTED]> writes:
1) I'll branch the 1.3.1rc2 tag on the 1.3 branch and to do a 1.3.1 release. I think it's important to release that as-is, pre the patches from Dan.
+1, ship it!
2) the recent commits on 1.3.1rc2 will go as a 1.3.2, to RC and get it out because Dan committed those for a reason, and I'm sure he needs a release of it.
I'm okay with that. I started the test cases, but haven't made much progress due to a chronic lack of time.
Which you can do, as that stuff will be 1.3.2, so no rush, no worries.
3) the current head will become 1.4rc1 and move that as our primary release target to get a v1.4 out there.
4) patches go into head, which will be 1.5-dev
Hmm, the overhead of having two live branches doesn't sit well with me, but it really does seem like we need the additional train of development. Private branches are another good way to handle this.
two live branches? No - we do this all the time. We declare one branch for the release candidate (in this case 1.4) and then keep working (that would be head, or 1.5-dev)
So in summary :
1.3.1 (release) 1.3.2 (Dan's patches, to be released eventually) 1.4 our new RC 1.5 our ongoing work
To better facilitate this process, I've added new versions and milestones to for Velocity to Bugzilla <http://issues.apache.org/bugzilla/>, our current issue tracking system. --
Daniel Rall <[EMAIL PROTECTED]>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Geir Magnusson Jr 203-956-2604(w) Adeptra, Inc. 203-434-2093(m) [EMAIL PROTECTED] 203-247-1713(m)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
