I've created MRELEASE-341 and committed the associated release:stage Mojo please review.
2008/5/7 nicolas de loof <[EMAIL PROTECTED]>: > > My release:perform goal is NOT deploy .I don't use a maven repository for > delivery, as I build tar.gz and send it to my customer after testing. > > I also want to test the exact binary that will be delivered, so I CAN't > use rc, beta or any other "unused release". > > AFAIK apache releases use a "staging" repository for pre-release (RC) test > versions (see for example > http://cwiki.apache.org/GMOxPMGT/geronimo-release-process.html) > > Please note the manual step 4 : > Make a copy of the checked out project in this state in case you need to > roll back the release > > cd .. > cp -r trunk trunk-prepared > cd trunk > > > Also take a look at the maven release process - it also use a staging > repository (http://maven.apache.org/developers/release/releasing.html) but > doesn't explain how to rollback if the vote didn't pass. > > I'm not the only one that expect to rollback to my initial SNAPSHOT trunk > after a "staging" release. > > What about adding a "removeReleaseFiles" parameter (default-value=true) to > the PerformRelease Mojo ? > > Or maybe a new release:stage Mojo would be better ? > > > Nicolas. > > > 2008/5/7 Mark Struberg <[EMAIL PROTECTED]>: > > > > > > --- nicolas de loof <[EMAIL PROTECTED]> schrieb: > > > > > Hello, > > > > > > I'm planning my release process with help of the release plugin : > > > > > > 1. my project is version N-SNAPSHOT > > > 2. running release:prepare tags my project as version N and commit POM > > for > > > N+1-SNAPSHOT > > > 3. running release:perform creates the binary distribution from tag > > > 4. I deploy the binary to my validation server and start acceptance > > testing. > > > If all is OK, I can distribute the release > > > 5. If anything is wrong, running release:rollback reverts to > > N-SNAPSHOT and > > > I can fix the code and go back to step 1. I just rename the Tag in SVN > > to > > > "N-rcX" > > > > > > Looks good to me, but according to the documentation, release:perform > > > removes the release.properties and pom.backup files, so I'll not be > > able to > > > run the rollback. > > > > Thats because you'll get a release-version (not a snapshot) deployed > > into your distribution > > repository after release:perform has been executed successfully. And it > > is not a good idea to > > overwrite existing releases as you surely know. > > > > Can't you live with 'unused' releases? If the answer is no, then you'll > > probably have to do the > > testing with snapshot versions. Or maybe a 'rc' or 'beta' staging solves > > this management problem. > > > > LieGrü, > > strub > > > > > > Lesen Sie Ihre E-Mails auf dem Handy. > > www.yahoo.de/go > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
