Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification.
The following page has been changed by RahulAkolkar: http://wiki.apache.org/commons/CreatingReleases The comment on the change is: Add m2 release procedure proposal per discussion on dev list ------------------------------------------------------------------------------ * Remember to do 'mvn release:clean ' before you start the real release process. + ---- + + == Maven2 Release Procedure == + + As discussed here: http://markmail.org/message/3emjaadwpf7cr5q3 + + === A. Release prep === + + Including preparing the POM(s) -- see above. + + === B. Stage artifacts and site === + + 1. {{{mvn -Prc release:prepare}}} + + 1. {{{mvn -Prc release:perform}}} + + 1. {{{mvn -Prc site-deploy}}} + + (decouple site-deploy from release:perform via parent POM) + + ''-- or --'' + + i. {{{mvn -Prc deploy}}} + + i. {{{mvn -Prc site-deploy}}} + + The parent POM should define repositories such that when using the {{{rc}}} profile, uploaded artifacts go to: + * The Apache {{{m2-snapshot-repository}}} if a SNAPSHOT version is used (to permit easy testing of RCs by community, for instance) + * A staging repository under {{{p.a.o/builds/commons/{component.id}/}}} if a final version is used + + === C. Vote === + + If vote fails, undo and redo previous steps as appropriate. + + === D. Go live === + + 1. {{{mvn stage:copy -Dsource="...staging-repo-url..." -Dtarget="...rsync-repo-url..."}}} + + 1. {{{mvn site-deploy}}} + + ---- + - == Procedure for creating a release using M2 == + == Procedure for creating a release using M2 (outdated by above) == This assumes that the Commons Proxy is about to vote on 1.0-RC3. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
