accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1490461 - /accumulo/site/branches/git/content/git.mdtext
Date Thu, 06 Jun 2013 22:12:02 GMT
Author: elserj
Date: Thu Jun  6 22:12:02 2013
New Revision: 1490461

ACCUMULO-1498 Minor-release steps based on [~ctubbsii]'s write-up.


Modified: accumulo/site/branches/git/content/git.mdtext
--- accumulo/site/branches/git/content/git.mdtext (original)
+++ accumulo/site/branches/git/content/git.mdtext Thu Jun  6 22:12:02 2013
@@ -169,6 +169,30 @@ that requires input from all developers 
 ## Release Management
+Releases, although not a day to day task, have their own unique steps which are
+to be followed. Releases can be categorized in to minor and major releases.
+### A minor release
+A minor release is some set of changes `z\'` on top of a version `x.y.z`.
+Typically, `z'` is simply `z + 1`, e.g. given a release named '1.6.0', and the
+next minor release is '1.6.1'. These changes for `z'` should not break any
+client code which works against `z` and should absolutely not change the public
+By convention, the branch containing the changes `z'` should be named
+`x.y.z'-SNAPSHOT`. The steps to take are as follows:
+1. Prepare the release candidate. _reference release instructions_
+2. Create a tag of the release candidate from the `x.y.z'-SNAPSHOT` branch,
+named something like `x.y.z'-RC-N`.
+3. Test and Vote
+4. Create a tag with the correct final name: `x.y.z'`
+5. Push a delete of the remote branch `x.y.z'-SNAPSHOT` (_this should be fine
+   with ASF policy since the history is still intact_)
+### A major release
 # The infrastructure

View raw message