Re: [JBoss-dev] Added Rel_2_2_1 tag to Branch_2_2
1. Check out the 2.2.1 version: cvs co -r Rel_2_2_1 jboss I think the best is to always checkout the most recent code on the branch, so cvs co -rBranch_2_2 jboss How does the Branch_2_2 tag always refer to the latest code on the branch? 4. Move the Rel_2_2_1 tag from within the jboss root directory cvs tag -F Rel_2_2_1 My idea of using the Rel_x_y_z tags was related to merging only, so those tags are "internal" and go their way, separated from the JBoss_x_y_z tags that instead represent a "public" release. So, instead of moving the tag with 'cvs tag -F' I would then just make another tag cvs tag Rel_2_2_2 (from jboss root directory) and then after another patch tag again, cvs tag Rel_2_2_3, and so on, and *then* a JBoss_2_2_1[_Final] tag. Given the last discussion about FINAL I agree we can drop it. This way we always have tags that refer to a particular patch, and we can checkout the code prior to the patch, after it, thing that would be not possible if we moved the tag with 'cvs tag -F'. Do you agree ? Yes, that allows for better management. I'm thinking of doing the 2.2.1 release next Monday night at which point we'll add a JBoss_2_2_1_Final tag. Right. Cheers, Simon ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Added Rel_2_2_1 tag to Branch_2_2
Wouldn't it make more sense to call these tags Rel_2_2_0_a, Rel_2_2_0_b, then, after JBoss_2_2_1, Rel_2_2_1_a, Rel_2_2_1_b, etc? well, this discussion was brought up earlier, and it was determined to use a three digit version number. hence when you create a new release of version 2.2 (release 2.2.x), it becomes 2.2.++x Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect [EMAIL PROTECTED] www.filip.net ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Added Rel_2_2_1 tag to Branch_2_2
I would agree. It is a cleaner naming convention in my mind. Bordet, Simone wrote: My idea of using the Rel_x_y_z tags was related to merging only, so those tags are "internal" and go their way, separated from the JBoss_x_y_z tags that instead represent a "public" release. So, instead of moving the tag with 'cvs tag -F' I would then just make another tag cvs tag Rel_2_2_2 (from jboss root directory) and then after another patch tag again, cvs tag Rel_2_2_3, and so on, and *then* a JBoss_2_2_1[_Final] tag. Given the last discussion about FINAL I agree we can drop it. This way we always have tags that refer to a particular patch, and we can checkout the code prior to the patch, after it, thing that would be not possible if we moved the tag with 'cvs tag -F'. Do you agree ? Wouldn't it make more sense to call these tags Rel_2_2_0_a, Rel_2_2_0_b, then, after JBoss_2_2_1, Rel_2_2_1_a, Rel_2_2_1_b, etc? Toby. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
