Repository: aurora
Updated Branches:
  refs/heads/master 6edbac246 -> 03022a237


Prepare release notes for release.

Also update committers' guide with details on this step and on reverting 
auto-generated commits for
subsequent release candidates.

Reviewed at https://reviews.apache.org/r/52167/


Project: http://git-wip-us.apache.org/repos/asf/aurora/repo
Commit: http://git-wip-us.apache.org/repos/asf/aurora/commit/03022a23
Tree: http://git-wip-us.apache.org/repos/asf/aurora/tree/03022a23
Diff: http://git-wip-us.apache.org/repos/asf/aurora/diff/03022a23

Branch: refs/heads/master
Commit: 03022a237b5621ab425352e4616aad60d05778e2
Parents: 6edbac2
Author: Joshua Cohen <jco...@apache.org>
Authored: Thu Sep 22 14:08:36 2016 -0500
Committer: Joshua Cohen <jco...@apache.org>
Committed: Thu Sep 22 14:08:36 2016 -0500

----------------------------------------------------------------------
 RELEASE-NOTES.md                     |  2 +-
 docs/development/committers-guide.md | 11 ++++++++---
 2 files changed, 9 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/aurora/blob/03022a23/RELEASE-NOTES.md
----------------------------------------------------------------------
diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.md
index 854bcbd..82c9a1c 100644
--- a/RELEASE-NOTES.md
+++ b/RELEASE-NOTES.md
@@ -1,4 +1,4 @@
-0.16.0 (Not yet released)
+0.16.0
 ======
 
 ### New/updated:

http://git-wip-us.apache.org/repos/asf/aurora/blob/03022a23/docs/development/committers-guide.md
----------------------------------------------------------------------
diff --git a/docs/development/committers-guide.md 
b/docs/development/committers-guide.md
index ebf464b..eb17efe 100644
--- a/docs/development/committers-guide.md
+++ b/docs/development/committers-guide.md
@@ -64,6 +64,9 @@ To assign the fix version:
     * Select all issues > edit issue > set 'Change Fix Version/s' to the 
release version.
     * Make sure to uncheck 'Send mail for this update' at the bottom.
 
+2. Prepare RELEASE-NOTES.md for the release. This just boils down to removing 
the "(Not yet
+released)" suffix from the impending release.
+
 2. Create a release candidate. This will automatically update the CHANGELOG 
and commit it, create a
 branch and update the current version within the trunk. To create a minor 
version update and publish
 it run
@@ -78,9 +81,11 @@ by running
 
 4. Wait for the vote to complete. If the vote fails close the vote by replying 
to the initial [VOTE]
 email sent in step #3 by editing the subject to [RESULT][VOTE] ... and noting 
the failure reason
-(example [here](http://markmail.org/message/d4d6xtvj7vgwi76f)). Now address 
any issues and go back to
-step #1 and run again, this time you will use the -r flag to increment the 
release candidate
-version. This will automatically clean up the release candidate rc0 branch and 
source distribution.
+(example [here](http://markmail.org/message/d4d6xtvj7vgwi76f)). You'll also 
need to manually revert
+the commits generated by the release candidate script that incremented the 
snapshot version and
+updated the changelog. Once that is done, now address any issues and go back 
to step #1 and run
+again, this time you will use the -r flag to increment the release candidate 
version. This will
+automatically clean up the release candidate rc0 branch and source 
distribution.
 
                ./build-support/release/release-candidate -l m -r 1 -p
 

Reply via email to