Page History

...

• mvn release:prepare -DdryRun=true

Tag and

...

Increment Version

This step will set the version declared in the project's pom.xml files, commit the changes to trunk, tag the release, and finally, check in another trunk change that increments the next development version (e.g. x.y-SNAPSHOT) in the pom.xml files.

...

• mvn install
• mvn release:prepare -Dusername=YourSVNUsername -Dpassword=YourSVNPassword

If backing out of this step is needed for any reason, the following will restore the subversion repository and your working copy to the state it was previously in:

• mvn release:rollback -Dusername=YourSVNUsername -Dpassword=YourSVNPassword

...

• svn rm https://fedora-commons.org/svn/root/akubra/tags/akubra-x.y^{Image Added}

Deploy Artifacts to Staging

This step will push all release artifacts to the staging repository.

• Check out the tagged release from subversion and "mvn install" it.
• Change back to trunk
• mvn release:perform -Darguments="-Dgpg.keyname=YourKeyID YourKeyId -Dgpg.passphrase=YourKeyPassword"

This will push all release artifacts to the staging repository.

...

Verify and Promote Staged Artifacts

• Log into http://oss.sonatype.org/^{Image Added} UI, click Staging in the left column, then select the staged repository on the right. It will open below. Right click on it and select Close.
• Download and test that the artifacts in staging are exactly as they should be once deployed to central.

If anything is incorrect, right click the staged repository and select "Drop". After the problem is resolved, you can re-deploy the artifacts to staging and verify them again. To re-deploy and already-tagged release:

• mvn release:perform -Dtag=akubra-x.y -DconnectionUrl=scm:svn:https://fedora-commons.org/svn/root/akubra^{Image Added} -Darguments="-Dgpg.keyname=YourKeyId -Dgpg.passphrase=YourKeyPassword"

If everything looks good, right click on the repository and select "Promote". The artifacts should be synced to central within an hour.

Upload Static Documentation

The release:perform step should have created a static maven site for the release (including javadocs) in /tmp/akubra-site. This step will make that documentation available at the appropriate place on the fedora-commons.org website.

1. cd /tmp
2. mv akubra-site site
3. jar -cMf site.jar site
4. sftp fcrelman@fedora-commons.org
5. cd documentation/akubra
6. mkdir x.y
7. cd x.y
8. put site.jar
9. exit
10. ssh fcrelman@fedora-commons.org
11. cd documentation/akubra/x.y
12. jar -xvf site.jar
13. rm site.jar
14. exit

Verify the documentation is available at http://fedora-commons.org/documentation/akubra/x.y/site/^{Image Added}

Archive the Release

1. Make a local copy of all the artifacts, checksums, and signatures published to central for this release, putting them in a local directory called akubra-x.y. (If you find a scriptable way to do this, please add it here...)
2. jar -cMf akubra-x.y.jar akubra-x.y
3. sftp fcrelman@fedora-commons.org
4. cd /home/fedcommbkup/release-archive
5. cd YYYY (e.g. 2010, if it doesn't exist, create it)
6. mkdir MM-DD (e.g. 03-13, the release date)
7. cd MM-DD
8. put akubra-x.y.jar
9. exit
10. ssh fcrelman@fedora-commons.org
11. cd /home/fedcommbkup/release-archive/YYYY/MM-DD
12. jar -xvf akubra-x.y.jar
13. rm akubra-x.y.jar
14. exit

Update the Wiki

Add release notes an update all links on this page.