That sounds like best practices for a situation where you're using Maven but not using the release plugin, yeah.
A. On Tue, Nov 22, 2011 at 4:33 PM, Tom White <[email protected]> wrote: > On Tue, Nov 22, 2011 at 3:32 PM, Arun C Murthy <[email protected]> > wrote: > > Andrew, > > > > > > On Nov 22, 2011, at 1:43 PM, Andrew Bayer wrote: > > > >> Hi all - > >> > >> I've been unable to find a revision in svn that actually corresponds > >> directly to the contents of hadoop-0.23.0-src.tar.gz. The POMs in the > >> tarball all have <version>0.23.0</version>, but the release-0.23.0 tag, > >> everything on branch-0.23, everything on branch-0.23.0, everything on > the > >> rc branches, etc have <version>0.23.0-SNAPSHOT</version>. Is this > something > >> which could be fixed? > >> > > > > It wasn't clear at that time, so I used 'mvn versions:set' to create the > release. I could go ahead and commit, Tom? > > > > I've documented that in > http://wiki.apache.org/hadoop/HowToReleasePostMavenization. > > 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. > > Cheers, > Tom > > > > >> Also, shouldn't <version> on branch-0.23 now be 0.23.1-SNAPSHOT? > > > > That's easy to do, but, again I'm sketchy about when we change it to > 0.23.1 - should that be done in a branch-0.23.1? > > > > Arun >
