Hi, I don't know why it is a TAG. TAG means (to me) something "more" serious/final. ....and... that all 1.2.1 related fixes go into that as well. New "features" not.
That's why I asked, why is trunk still 1.2.1 (and not 1.22) -M On Jan 20, 2008 1:29 PM, Manfred Geiler <[EMAIL PROTECTED]> wrote: > On Jan 20, 2008 6:50 PM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > Hi, > > > > 2) > > The trunk says 1.2.1-SNAPSHOT. > > In case we use the above mentioned TAG, shouldn't it say 1.2.2-SNAPSHOT > > already? > > No, I think 1.2.1-SNAPSHOT on trunk is ok as long as there is no release. > > The "1_2_1_RC" (normally) is a working copy branch(!) that is used to > prepare the release without disturbing concurrent development. > BTW, why is "1_2_1_RC" a tag? It should be a branch of course. > > Leaving the version on trunk unchanged gives the release manager the > chance to throw away this working copy branch and start over with a > new copy from the trunk. > > "textbook example": > As soon as the release is out, all important fixes and changes on this > branch (including the pom updates to "1.2.2-SNAPSHOT") will be merged > back to the trunk. > > --Manfred > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
