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 AndrewPhillips: https://wiki.apache.org/jclouds/Releasing%20jclouds?action=diff&rev1=51&rev2=52 1. 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. The following command can help finding all those versions: 1. {{{find . -name pom.xml -exec grep -nH '1.6.3-SNAPSHOT' {} \; | grep -v '<version>'}}} 1. Commit the changes, as otherwise the following step will complain about uncommitted local modifications, but don't push them. - 1. For jclouds-labs-openstack.git, first run {{{mvn versions:update-parent -DparentVersion="[1.6.3]"}}} (or whatever the release version is) and commit the changes (don't push them yet). + 1. For jclouds-labs-openstack.git, first run {{{mvn versions:update-parent -DgenerateBackupPoms=false -DparentVersion="[1.6.3]"}}} (or whatever the release version is) and commit the changes (don't push them yet). 1. Run {{{mvn --version}}} and verify that you are using a Java 6 JDK for 1.6.x or newer releases 1. Give your build more memory. e.g. 1. {{{export MAVEN_OPTS="-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=1024m"}}} @@ -98, +98 @@ 1. We deliberately do not run the tests in the release build, since we already just ran them for the prepare build, and that just seems redundant. 1. JARs will be deployed to repository.apache.org, in a new staging repo (if this is the first of the repos you're building) or the existing one used for the previous repos (if you've already built jclouds.git). Remember that you need to have an account on repository.apache.org and your GPG key set up (as described above) or the build will fail. 1. For those repos where we added a commit to update {{{<jclouds.version>}}} and similar properties, bump the properties to the next development SNAPSHOT version and commit the change + 1. For jclouds-labs-openstack.git, this can be done by running {{{mvn versions:update-parent -DallowSnapshots=true -DgenerateBackupPoms=false -DparentVersion="[1.6.4-SNAPSHOT]"}}}. You will need to install {{{jclouds-project:1.6.4-SNAPSHOT}}} in your local repository first, though. 1. Push the tag and the release commit to the remote repos 1. We don't push the second commit the release plugin applies, changing the version to 1.6.4-SNAPSHOT, or the commits that change {{{<jclouds.version>}}} and similar properties, yet. If we need to spin a second release candidate, we'll do by creating a new 1.6.4 (or whatever) branch from the last commit before the version changed to the release version, and re-run subsequent RCs there. 1. Go to [[https://git-wip-us.apache.org/repos/asf?p=jclouds.git]] (or equivalent) and find the link to the tag you just pushed - copy that and the assoicated commit hash aside, since you'll need them for the vote email.
