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 EverettToews: https://wiki.apache.org/jclouds/Releasing%20jclouds?action=diff&rev1=49&rev2=50 1. Check out the branch you're going to be releasing from - e.g., 1.6.x 1. 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 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. {{{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. Run {{{mvn --version}}} and verify that you are using a Java 6 JDK for 1.6.x releases 1. Give your build more memory. e.g. - 1. {{{ export MAVEN_OPTS="-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=1024m" }}} + 1. {{{export MAVEN_OPTS="-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=1024m"}}} 1. Prepare the release. Remember to replace "jclouds-1.6.3-rcX" and the versions with the correct tag/version for the repo/release/RC you're building. e.g.: - 1. {{{ mvn release:clean release:prepare -DreleaseVersion=1.6.3 -Dtag=jclouds-1.6.3-rcX -DdevelopmentVersion=1.6.4-SNAPSHOT -DpushChanges=false }}} + 1. {{{mvn release:clean release:prepare -DreleaseVersion=1.6.3 -Dtag=jclouds-1.6.3-rcX -DdevelopmentVersion=1.6.4-SNAPSHOT -DpushChanges=false}}} 1. Maven will ask you some questions: 1. There are still some remaining snapshot dependencies. Do you want to resolve them now? yes 1. Dependency type to resolve,: specify the selection number: 0 @@ -106, +106 @@ === Starting the Vote === 1. Checkout https://dist.apache.org/repos/dist/dev/jclouds. Create a new directory for the RC, i.e., 1.6.3-rc1. 1. 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. - 1. {{{ ./fetch_jclouds_rc.sh 1.6.3 https://repository.apache.org/content/repositories/orgapachejclouds-016 1.6.3-rc1/ }}} + 1. {{{./fetch_jclouds_rc.sh 1.6.3 https://repository.apache.org/content/repositories/orgapachejclouds-016 1.6.3-rc1/}}} 1. 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. 1. svn add the new directory, as well as svn rm'ing any old RCs in the same line (i.e., any older 1.6.x RC). svn ci, and use that link under https://dist.apache.org/repos/dist/dev/jclouds/ for the release vote email. 1. 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. @@ -179, +179 @@ === Actually Releasing === 1. 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. + 1. {{{git tag jclouds-1.6.3 jclouds-1.6.3-rc1}}} + 1. {{{git push origin jclouds-1.6.3}}} 1. 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 1. For jclouds-labs-openstack, also run {{{mvn versions:update-parent -DparentVersion="[1.6.4-SNAPSHOT]"}}} or whatever the new version is, commit, push. 1. Checkout https://dist.apache.org/repos/dist/release/jclouds. Create a new directory for the release, i.e., 1.6.3. 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/jclouds]] shortly, but will take a while to propagate to the various mirrors.
