[Jclouds Wiki] Update of "Releasing jclouds" by AndrewBayer

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jclouds Wiki" for change notification.

The "Releasing jclouds" page has been changed by AndrewBayer:
https://wiki.apache.org/jclouds/Releasing%20jclouds?action=diff&rev1=23&rev2=24

  
  === Running the RC build ===
   * The repo order to run the RC build is:
-   * incubating-jclouds.git
+   * jclouds.git
-   * incubating-jclouds-labs.git
+   * jclouds-labs.git
-   * incubating-jclouds-labs-openstack.git
+   * jclouds-labs-openstack.git
-   * incubating-jclouds-chef.git
+   * jclouds-chef.git
-   * incubating-jclouds-karaf.git
+   * jclouds-karaf.git
-   * incubating-jclouds-cli.git
+   * jclouds-cli.git
   * For each of those repos, in that order, do the following:
    * Check out the branch you're going to be releasing from - e.g., 1.6.x
    * Check that your [[https://help.github.com/articles/setting-your-username-in-git|Git username]] and [[https://help.github.com/articles/setting-your-email-in-git|email]] are set to match your Apache account
    * Check the <repo>/pom.xml and/or <repo>/project/pom.xml for any properties (typically {{{<jclouds.version>}}}) referencing the SNAPSHOT version we're leaving, and replace those with the release version. Commit the changes, as otherwise the following step will complain about uncommitted local modifications
+    * For jclouds-labs-openstack.git, first run {{mvn versions:update-parent -DparentVersion="[1.6.3]"}} (or whatever the release version is). Commit and push.
    * Run {{{mvn --version}}} and verify that you are using a Java 6 JDK for 1.6.x releases
    * Prepare the release. e.g.:
  {{{
@@ -179, +180 @@

  === Actually Releasing ===
   * First, in each of the repos, create and push a new tag, like jclouds-1.6.1-incubating, pointing at the same commit as the RC tag we included in the vote emails. Push those tags to the remote.
   * Push the second commit made by the release plugin (which updates the POM versions to the next SNAPSHOT), and commits made to update {{{<jclouds.version>}}} and similar properties
+   * For jclouds-labs-openstack, also run {{mvn versions:update-parent -DparentVersion="[1.6.4-SNAPSHOT]"}} or whatever the new version is, commit, push.
   * Checkout https://dist.apache.org/repos/dist/release/incubator/jclouds. Create a new directory for the release, i.e., 1.6.1-incubating. 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 svn rm'ing any old releases in the same line (i.e., any older 1.6.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/incubator/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.