Or you can just tag it x.y.z-rc0, and 'svn mv' it to the final tag spot without the rc designation if it is approved, else svn rm it. I'm not sure why you would need to create a branch for each release, rather than simply a tag for each release.
svn cp branches/0.23.x tags/0.23.1-rc0 cd tags/0.23.1-rc0 mvn versions:set . . . (to 0.23.1, then commit) svn commit (tag created with updated poms) vote passes .... svn mv tags/0.23.1-rc0 tags/0.23.1 The 'tags/0.23.1-rc0' above can be replaced with any svn path you wish that is temporary. On 11/22/11 5:03 PM, "Arun C Murthy" <[email protected]> wrote: > >On Nov 22, 2011, at 4:33 PM, Tom White wrote: >> I think 'mvn versions:set' should be called (and changes committed) >> before creating the release candidate tag. I.e. after step 4 of >> 'Updating Release Branch' on that wiki page. > >Furthermore, we need to create a branch for the actual version e.g. >branch-0.23.1 where we commit it. Then, branch-0.23 should have version >set to 0.23.2-SNAPSHOT. > >I'll update the wiki to reflect these. > >Arun
