aurora git commit: Add failed result email protocol.

[js...@apache.org]

Repository: aurora
Updated Branches:
  refs/heads/master 505f31005 -> 9b7c72eb6


Add failed result email protocol.

Hints of this protocol exist down in step 6 when a release succeeds,
but this places the failure action in-line in the step process to make
it more likely the reader does the right thing.

Also kill an incorrect instruction to send the successful release vote
result email to the private@ list.

Testing Done:
I have no clue if the instructions and provided example link are correct.
I did find variation when reading past [RESULT][VOTE] failures; so
guidance on what is required vs what is personal flair is appreciated.

Rendered here: https://github.com/jsirois/aurora/blob/jsirois/release-docs/more-fixes/docs/committers.md

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


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

Branch: refs/heads/master
Commit: 9b7c72eb68d124ba80f4a4ade8223bd96cace2b8
Parents: 505f310
Author: John Sirois <js...@apache.org>
Authored: Fri Feb 5 08:58:10 2016 -0700
Committer: John Sirois <js...@apache.org>
Committed: Fri Feb 5 08:58:10 2016 -0700

----------------------------------------------------------------------
 docs/committers.md | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/aurora/blob/9b7c72eb/docs/committers.md
----------------------------------------------------------------------
diff --git a/docs/committers.md b/docs/committers.md
index a0a3cf5..f69a898 100644
--- a/docs/committers.md
+++ b/docs/committers.md
@@ -62,11 +62,13 @@ it run
 send the [VOTE] email to the dev@ mailing list. You can verify the release signature and checksums
 by running
 
-				./build-support/release/verify-release-candidate
+               ./build-support/release/verify-release-candidate
 
-4. Wait for the vote to complete. If the vote fails 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.
+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.
 
                ./build-support/release/release-candidate -l m -r 1 -p
 
@@ -75,5 +77,5 @@ automatically clean up the release candidate rc0 branch and source distribution.
                ./build-support/release/release
 
 6. Update the draft email created fom the `release` script in step #5 to include the Apache ID's for
-all binding votes and send the [RESULT][VOTE] email to the dev@ and private@ mailing lists.
+all binding votes and send the [RESULT][VOTE] email to the dev@ mailing list.