...
Cutting an RC
Running the RC build
...
Checkout https://dist.apache.org/repos/dist/dev/jclouds. Create a new directory for the RC, i.e., 1.9.0-rc1.
- Go to the candidate directory and run the following, substituting the correct version and the now-closed staging repository accordingly. This will copy down all the source tarballs, their signatures and their checksums.
./fetch_jclouds_rc.sh 1.9.0 https://repository.apache.org/content/repositories/orgapachejclouds-016 1.9.0-rc1/
It's not a bad idea to try taking each of the tarballs, blowing them up and then building, with a standard mvn clean install. Remember that RAT checks are done as part of the Maven build, so you don't need to run those separately.
svn add the new directory , as well as and svn rm 'ing any old RCs (i.e., any older 1.9.x RC). svn ci, and use that link under https://dist.apache.org/repos/dist/dev/jclouds/ for the release vote email.
Get the JIRA release notes for the release by going to https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12314430 and choosing HTML and the version you're releasing. Save that link for inclusion in the vote/discuss emails.
Send two emails to dev@jclouds.apache.org, a [VOTE] thread and a [DISCUSS] thread. Set an end time for the vote, generally 72 hours from when you're sending it (but it's generally considerate to round up, and not a bad idea to give an extra day if the release vote window goes over the weekend). Example templates for the emails are below. Replace links, versions, RC numbers, release note link, etc.
- [VOTE] email:
...
- First, in each of the repos, create and push a new tag, like jclouds-1.6.3, pointing at the same commit as the RC tag we included in the vote emails. Push those tags to the remote.
git tag rel/jclouds-1.9.0 rel/jclouds-1.9.0-rc1
git push origin rel/jclouds-1.9.0
Push the release branch. It contains the commit that updates all versions to the next SNAPSHOT and all jclouds.version properties
- git push origin 1.9.x
Checkout https://dist.apache.org/repos/dist/release/jclouds. Create a new directory for the release, i.e., 1.9.0. Copy the release artifacts from the RC into that directory. Point the stable symlink to that new directory. svn add the new directory and the stable symlink, as well as and svn rm 'ing any old releases (i.e., any older 1.9.x releases) - these are archived on archive.apache.org, but shouldn't be in the primary dist area. svn ci - your added files should show up on http://www.apache.org/dist/jclouds shortly, but will take a while to propagate to the various mirrors.
While waiting, go to https://repository.apache.org, log in, and go to Staging Repositories. Select the staging repo for the RC, and click Release - this will move the artifacts into the releases repo, and from there they'll be synced to Maven Central as well.
- If you've got admin access to JIRA, mark the version you just released as, well, released, and if the next version in the train doesn't already exist, create it. If you're not in the JIRA admins for jclouds, drop an email to the dev list asking for someone to do this.
- Create the release notes in the jclouds main site and update the DOAP file to include the new release there.
Once the release bits have shown up on the mirrors, send the following email, updating the content accordingly, to announce@apache.org, dev@jclouds.apache.org and user@jclouds.apache.org:
Subject: [ANNOUNCE] Apache jclouds 2.1.1 released Body: The Apache jclouds team is pleased to announce the release of jclouds 2.1.1. Apache jclouds is an open source multi-cloud toolkit for the Java platform that gives you the freedom to create applications that are portable across clouds while giving you full control to use cloud-specific features. The source archives for the release are available here: https://jclouds.apache.org/start/install/ The Maven artifacts for the release are available in Maven Central, under the org.apache.jclouds group ID.
The release notes are available here:
https://jclouds.apache.org/releasenotes/2.1.1/ We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at: https://jclouds.apache.org/ The Apache jclouds Team