Page History

...

• Write access to the Akubra git repository at https://github.com/akubra/akubra.
• Write access to the org.akubraproject groupId in the snapshot and staging repositories hosted at oss.sonatype.org.  If you don't already have this, you will need to:
  • Sign up for a Sonatype OSS account
  • Ask the previous release manager to request authorization for this account via the Akubra Project Hosting Ticket
• The login details for the fcrelman account at fedora-commons.org.  This is only required for official releases, not snapshots.  If you don't have this information yet, you can get it from the previous release manager.

Update Maven settings.xml

...

From a clean, up-to-date copy of trunk, run the following command:

• mvn clean javadoc:jar source:jar deploy

The snapshot will be immediately available in the public Sonatype repository: http://oss.sonatype.org/content/groups/public

...

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

mvn release:clean
mvn release:prepare -Dtag=v0.34.10
# If the above fails due to missing dependencies,
# run it again after first running 'mvn install'
git pull
git checkout v0.34.10
mvn clean install
git checkout master
mvn release:perform

Verify and Promote Staged Artifacts

1. Log into http://oss.sonatype.org/^{Image Removed} 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.
2. 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 an already-tagged release:via mvn release:perform -Dtag=v0.

...

4.0 and verify them again.

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

Upload

...

Site to Github

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 Removed}

Archive the Release

...

http://akubra.github.com/akubra/

git checkout gh-pages
cp -a /tmp/akubra-site/ .
git add .
git commit
git push

...

Update the Wiki

Add release notes and update all links on this page.