svn commit: r1605571 - /subversion/site/publish/docs/community-guide/releasing.part.html

[da...@apache.org]

Author: danielsh
Date: Wed Jun 25 19:41:32 2014
New Revision: 1605571

URL: http://svn.apache.org/r1605571
Log:
* docs/community-guide/releasing.part.html
  (#release-branches): Add an item about -0/-1 votes in the previous branch's
    STATUS file.

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1605571&r1=1605570&r2=1605571&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Wed Jun 25 19:41:32 2014
@@ -1173,6 +1173,11 @@ A.B with the version you're preparing, e
 <ul>
 <li><p>Review the <a href="/roadmap">Roadmap</a>.  Should any of the outstanding
        items be addressed before branching?</p></li>
+<li><p>Review the incumbent stable branch's STATUS file for outstanding
+       -0 and -1 votes.  Was code that is going to be included in the new
+       branch objected to?  (Even if yes, that should not block branching, but
+       discussion should be started in order to resolve the issue before
+       rolling release branches.)</p></li>
 <li><p>Do any tree-wide, mechanical changes.  (Non-mechanical changes should
        have happened earlier to allow for review.)  This eases merging later.
        Examples include