On Wed, 2010-06-09 at 17:13 +0100, sebb wrote: > I've just started looking at the release process documentation, which > I think is very comprehensive. > > I'd like to suggest a minor change to the process for creating a release tag. > > Rather than updating trunk and creating the tag from that, one can > create the tag directly from local workspace, i.e. > > 1. Create a clean SVN workspace for the release candidate > svn co https://.../trunk hc4.xRC1 > > 2. Update the poms etc in the new workspace > > 3. Create the new tag from the workspace > svn copy https:/..../tags/hc4.xRC1 > > This has the advantage that trunk is never in a transition state. > Also, if anyone else changes trunk during the release process it will > not affect the tag > (though of one can run "svn update" in the workspace if some late > changes are needed) > SVN history is preserved, and the commit message will show just the > changes to the poms etc. > > If the release vote succeeds, then of course trunk needs to be updated > to the next snapshot release and the tag can be renamed. If the vote > fails, the tag can just be deleted and the process resumed. >
I did not realize it was possible to create a tag from a local change-set. This resolves the biggest problem I have always had with Maven releases. I always disliked having to modify project poms in the trunk when creating release tags > Does that sound OK? > Sounds good to me. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
