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=3&rev2=4

  = How to release (and test RCs) for Apache jclouds (incubating) =
+ 
+ == Checklist Summary of Steps Involved in Releasing ==
+ 
+  1. Have a GPG signing key configured.
+  2. Clone all repos to be released, if you haven't already.
+  3. 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.
+  5. Run mvn release commands for each repo, in order, as described below.
+  6. Push the branches and RC tags to the remote repos.
+  7. Close the Nexus staging repository.
+  8. 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.
+  10. If the vote fails or there are issues that need to be addressed, rinse 
and repeat.
+  11. Once the PPMC vote passes, email the [email protected] list (cc'ing 
[email protected]) to start the 72 hour vote window for the IPMC.
+  12. If the vote fails, rinse, repeat - in most cases, a new PPMC vote will 
need to be held before a new IPMC vote.
+  13. Once the IPMC vote passes, release the Nexus staging repo.
+  14. Send a RESULT email in reply to the IPMC vote thread with the result.
+  15. Copy the RC tarballs etc to the release area.
+  16. Push non-RC tags to the remote repos.
+  17. Update the version on the branch in the repos to the next SNAPSHOT and 
push.
+  18. Update the jclouds.incubator.apache.org site with the release notes and 
noting the new version.
+  19. Publish the API docs for the release.
+  20. Mark the release as, well, released in JIRA and create the next release 
in JIRA, if it's not already there.
+  21. Send out an ANNOUNCE email to the appropriate lists (see below) to 
announce the release!
+ 
  
  == Prerequisites for doing a release ==
  

Reply via email to