...

TODO: These instructions need updating to reflect http://apache.org/dev/release-signing.html^{Image Removed} regarding i) key length, ii) signature strength.

...

1. Generate PGP code signing keys
2. Ensure that your PGP signing keys are available in: http://svn.apache.org/repos/asf/whirr/dist/KEYS^{Image Removed} More details can be found here.
3. Copy the new KEYS file to the release folder /www/www.apache.org/dist/whirr on people.apache.org

...

You need to be a member of the "incubator" unix group on people.apache.org. Ask for help on the incubator general@ list. Here's an example http://bit.ly/9Wkdzg^{Image Removed}

Ensure that you have setup your ssh keys on people.apache.org, otherwise you'll have to enter your login password a number of times (best use ssh-agent for this as well). A good overview of this process can be found here (ssh-copy-id and ssh-agent in particular)

...

• Update CHANGES.txt in trunk to replace Trunk (unreleased changes) with Release X.Y.0 - YYYY-MM-DD. Commit:

  No Format
  svn commit -m "Preparing for release X.Y.Z"

• Create a branch for the release series:

  No Format
  svn copy https://svn.apache.org/repos/asf/whirr/trunk \ https://svn.apache.org/repos/asf/whirr/branches/branch-X.Y -m "Branching for X.Y releases"

• Add back Trunk (unreleased changes) to CHANGES.txt in trunk.
• Bump the version number in trunk (the update-versions script mangles the whitespace in the root XML element):

  No Format
  for file in $(find . -name pom.xml); do sed -i "" -e "s/0.1.0-SNAPSHOT/0.2.0-SNAPSHOT/" $file; done

• Bump the version in src/site/xdoc/index.xml.
• Bump the version in src/site/confluencexdoc/whirr-in-5-minutes.confluencexml.
• Bump the version in src/site/site.xml.
• Commit these changes to trunk.
• Checkout the release branch

  No Format
  svn checkout https://svn.apache.org/repos/asf/whirr/branches/branch-X.Y

...

for file in $(find . -name pom.xml); do
  sed -i "" -e "s/0.1.0-SNAPSHOT/0.1.0/" $file;
done

• Fix the version numbers in src/site/xdoc/index.xml, src/site/xdoc/whirr-in-5-minutes.xml, src/site/site.xml.

Run Tests

Run all the unit and integration tests (which means you should have cloud credentials to run on a cloud provider) with the following:

...

JIRA has the ability to generate release notes automatically (this is why it is so important to keep the fix version number accurate).

https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12311110^{Image Removed}

Manually check this list for accuracy! I've repeatedly seen closed bugs that were not fixed (i.e., duplicate) marked with a fix version, so that they incorrectly show up in this list. Find those, edit them to remove the fix release (only actually fixed bugs should have a fix release) and re-run the report.

...

If this step fails with an Access denied error check that you have the required permissions on Nexus.

Login to https://repository.apache.org^{Image Removed} using your Apache credentials. Click on Staging on the left. Then click on org.apache.whirr in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Select this repository and click Close. This will close the repository from future deployments and make it available for others to view.

...

The last line is to remove the previous version, since only the most recent version on a particular branch should be in the dist directory (older versions are archived automatically, see http://archive.apache.org/dist/incubator/whirr/^{Image Removed} and http://www.apache.org/dev/mirrors.html^{Image Removed}).

Log in to https://repository.apache.org^{Image Removed}, click on Staging on the left. Select the repository that you closed earlier, and click Release, using a description like "Apache Whirr X.Y.Z artifacts". This will make the artifacts publicly available.

...

Add the next version number (e.g. 0.2.0 after 0.1.0) to JIRA using this
link: https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12311110^{Image Removed}.

In JIRA mark the released version as "released" on the "manage versions" page. Be sure to fill in a date if not already specified.

...

Update the top level site by checking out https://svn.apache.org/repos/asf/whirr/site^{Image Removed} (note that this is still in svn) and editing src/site/site.xml to update the version number. Then type:

...

and commit the changes. The updated website will be published to http://whirr.apache.org^{Image Removed} immediately (it uses svnpubsub).

...