Author: danielsh
Date: Fri Aug 30 18:50:28 2019
New Revision: 1866169

URL: http://svn.apache.org/viewvc?rev=1866169&view=rev
Log:
* docs/community-guide/releasing.part.html
  (#release-stabilization): Mention nominate.pl and backport.pl interactive 
mode.

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

Modified: subversion/site/staging/docs/community-guide/releasing.part.html
URL: 
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1866169&r1=1866168&r2=1866169&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Fri Aug 30 
18:50:28 2019
@@ -730,6 +730,17 @@ directory.</p>
 <p>A temporary branch is also used in the rare case that a change should
 be made to the A.B.x branch that isn't a backport of a change from trunk.</p>
 
+<p>If you nominate an entry that causes merge conflicts until another
+nomination is merged, note that in the nomination.  Put a "Depends:" header
+in the entry; that will keep the hourly "detect nominations with merge
+conflict" buildbot job green.  (The value of the "Depends:" header is not
+parsed.)</p>
+
+<p>The tools/dist/nominate.pl script (in trunk) automates the process of adding
+a new nomination.  The same script also has a REPL loop that helps with the
+process of reviewing nominations and casting votes; see
+tools/dist/README.backport (in trunk).</p>
+
 <p>NOTE: Changes to <tt>STATUS</tt> regarding the temporary branch, including
 voting, are always kept on the main release branch.</p>
 


Reply via email to