You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jclouds.apache.org by Apache Wiki <wi...@apache.org> on 2013/12/18 22:12:07 UTC
[Jclouds Wiki] Update of "Releasing jclouds" by AndrewGaul
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 AndrewGaul:
https://wiki.apache.org/jclouds/Releasing%20jclouds?action=diff&rev1=30&rev2=31
1. Email the dev list to let them know the release process is beginning and ask all to clean up any JIRA issues they are familiar with.
1. Have a GPG signing key configured.
- 2. Clone all repos to be released, if you haven't already.
+ 1. Clone all repos to be released, if you haven't already.
- 3. Check out the branch to be released in each repo.
+ 1. Check out the branch to be released in each repo.
- 4. Update any POM properties in the repos pointing at the SNAPSHOT version and change those to the release version.
+ 1. Update any POM properties in the repos pointing at the SNAPSHOT version and change those to the release version.
- 5. Run mvn release commands for each repo, in order, as described below. If building a 1.6.x release, use a Java 6 JDK
+ 1. Run mvn release commands for each repo, in order, as described below. If building a 1.6.x release, use a Java 6 JDK
- 6. Push the release commits and RC tags to the remote repos.
+ 1. Push the release commits and RC tags to the remote repos.
- 7. Close the Nexus staging repository.
+ 1. Close the Nexus staging repository.
- 8. Copy the source release tarballs, signatures and hashes to a new release candidate directory.
+ 1. Copy the source release tarballs, signatures and hashes to a new release candidate directory.
- 9. Email the dev list, opening the 72 hour vote window on the RC.
+ 1. Email the dev list, opening the 72 hour vote window on the RC.
- 10. If the vote fails or there are issues that need to be addressed, rinse and repeat.
+ 1. If the vote fails or there are issues that need to be addressed, rinse and repeat.
- 11. Once the PMC vote passes, release the Nexus staging repo.
+ 1. Once the PMC vote passes, release the Nexus staging repo.
- 12. Send a RESULT email in reply to the PMC vote thread with the result.
+ 1. Send a RESULT email in reply to the PMC vote thread with the result.
- 13. Copy the RC tarballs etc to the release area.
+ 1. Copy the RC tarballs etc to the release area.
- 14. Push non-RC tags to the remote repos.
+ 1. Push non-RC tags to the remote repos.
- 15. Update the version on the branch in the repos to the next SNAPSHOT and push.
+ 1. Update the version on the branch in the repos to the next SNAPSHOT and push.
- 16. Update the jclouds.apache.org site with the release notes and noting the new version.
+ 1. Update the jclouds.apache.org site with the release notes and noting the new version.
- 17. Publish the API docs for the release.
+ 1. Publish the API docs for the release.
- 18. Mark the release as, well, released in JIRA and create the next release in JIRA, if it's not already there.
+ 1. Mark the release as, well, released in JIRA and create the next release in JIRA, if it's not already there.
- 19. Send out an ANNOUNCE email to the appropriate lists (see below) to announce the release!
+ 1. Send out an ANNOUNCE email to the appropriate lists (see below) to announce the release!
== Prerequisites for doing a release ==