Quoting Martin Cooper <[EMAIL PROTECTED]>: > On Wed, 25 Feb 2004, Joe Germuska wrote: > > > Perhaps this is understood, but I'm assuming that we also want to say > > that the RM "owns" the release tags for the release he or she is > > managing, and only the RM should *ever* move the tags? > > It's never been stated as such, but that's not a bad idea at all. I can't > think of a good reason to move tags, other than to tweak things as part of > the release process, and only the RM should be doing that. > > Now, where can we document this? ;-) >
Why, in the "Struts Release Management Process" pages, of course :-) In reality, it's sort of a sad commentary that we haven't done enough releases for this to be a noticeable issue :-). FWIW, I'm a fan of letting the RM decide on one of two alternative approaches for each release: * Announce a freeze of the HEAD branch (as was done here). * Create a CVS branch for this release, which starts as a snapshot of the development tree when the release candidate is initially created, and allows the RM to incorporate whatever subsequent HEAD branch commits make sense (by either doing a CVS join or manually interpoating the fixes). The latter strategy has worked very well for me lately ... it's worth trying on the Struts release process as well. (CVS branches are essentially free.) Craig > -- > Martin Cooper > > > > > > Joe > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
