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
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
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,
