svn commit: r1693409 - /sling/site/trunk/content/documentation/development/release-management.mdtext

[ro...@apache.org]

Author: rombert
Date: Thu Jul 30 11:04:43 2015
New Revision: 1693409

URL: http://svn.apache.org/r1693409
Log:
Clarify that release repositories must not be updated during votes

See discussion at http://markmail.org/thread/jvbbtujrfe6aulox for details

Modified:
    sling/site/trunk/content/documentation/development/release-management.mdtext

Modified: sling/site/trunk/content/documentation/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1693409&r1=1693408&r2=1693409&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Thu Jul 30 11:04:43 2015
@@ -159,7 +159,7 @@ If the vote is successful, post the resu
 
 Be sure to include all votes in the list and indicate which votes were binding. Consider \-1 votes very carefully. While there is technically no veto on release votes, there may be reasons for people to vote \-1. So sometimes it may be better to cancel a release when someone, especially a member of the PMC, votes \-1.
 
-If the vote is unsuccessful, you need to fix the issues and restart the process - see *Canceling the Release*.
+If the vote is unsuccessful, you need to fix the issues and restart the process - see *Canceling the Release*. Note that any changes to the artifacts under vote require a restart of the process, no matter how trivial. When restarting a vote version numbers must not be reused, since binaries might have already been copied around.
 
 If the vote is successful, you need to promote and distribute the release - see *Promoting the Release*.