Author: julianfoad
Date: Fri Dec 15 20:26:29 2017
New Revision: 1818326
URL: http://svn.apache.org/viewvc?rev=1818326&view=rev
Log:
* publish/docs/community-guide/releasing.part.html
(release-branches): Note automation by create-minor-release-branch.py.
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=1818326&r1=1818325&r2=1818326&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Dec 15
20:26:29 2017
@@ -1201,10 +1201,6 @@ minor release is a good time to start pr
that this is flexible, depending on what features are being
developed.</p>
-<p>Once people agree that a new release branch should be made, the
-Release Manager creates it with the following procedure (substitute
-A.B with the version you're preparing, eg. 1.3, or 2.0):</p>
-
<ul>
<li><p>Review the <a href="/roadmap">Roadmap</a>. Should any of the
outstanding
items be addressed before branching?</p></li>
@@ -1228,6 +1224,15 @@ A.B with the version you're preparing, e
such as
<a
href="http://www.red-bean.com/svnproject/contribulyzer/detail/http%253A%252F%252Fscan.coverity.com%252F.html";>static</a>
<a href="https://svn.apache.org/r1469608";>analysis</a>.)</p></li>
+</ul>
+
+<p>Once people agree that a new release branch should be made, the
+Release Manager creates it with the following procedure (substitute
+A.B with the version you're preparing, eg. 1.3, or 2.0).</p>
+
+<p>This can be mostly automated using
+ <tt>tools/dist/create-minor-release-branch.py</tt>.</p>
+<ul>
<li><p>Create the new release branch with a server-side copy:</p>
<pre>
svn cp ^/subversion/trunk \
