Hi Zoe, This looks pretty good to me. I personally really don't like creating branches for releases. If you use scm copy you note you have to update the scm locations in the poms manually. You also have two scm locations claiming to have the same version. The release plugin won't correctly update the trunk version for you. You end up with an orphan branch that you can't really delete because it has the svn history of the release but will never be used for anything. So I strongly recommend NOT making a release branch.
If you keep doing it, though, you need to figure out a process for manually updating version numbers in the trunk after release. This is going to be a process that is probably beyond my abilities to follow... thanks david jencks On Aug 17, 2010, at 3:00 AM, zoe slattery wrote: > Hi - As I went through the process of creating the release I created > documentation here: > > https://cwiki.apache.org/confluence/display/ARIES/ReleasingAries > > It should be on the Aries web site in a couple of hours when it's been synced > with the wiki. > > It would be really great if people could check the doc - I'd like us to be in > a position where anyone can do a release with minimal effort and I don't > think we are quite there yet :-) > > Thanks to everyone who has helped out with this so far! > > Zoë > >
