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

[da...@apache.org]

Author: danielsh
Date: Thu Jul 28 18:43:22 2011
New Revision: 1151964

URL: http://svn.apache.org/viewvc?rev=1151964&view=rev
Log:
More work for Hyrum.

* docs/community-guide/releasing.part.html
  (release-branches): Need to update the Python tests' notion of SVN_MINOR_NUMBER too.

Automated by: danielsh

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=1151964&r1=1151963&r2=1151964&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Jul 28 18:43:22 2011
@@ -1077,6 +1077,11 @@ A.B with the version you're preparing, e
     created a branch (eg. 2.1.0 for the 2.0.x branch, and 1.4.0 for
     the 1.3.x branch).</p></li>
 
+<li><p>Edit <tt>build/run_tests.py</tt> and
+    <tt>subversion/tests/cmdline/svntest/main.py</tt> on trunk and
+    increment <tt>SVN_VER_MINOR</tt>.  Do not commit these changes
+    yet.</p></li>
+
 <li><p>Edit <tt>CHANGES</tt> on trunk to introduce a new section for the
     upcoming release.  The section starts with:</p>
     <pre>
@@ -1093,6 +1098,10 @@ A.B with the version you're preparing, e
 
       * subversion/include/svn_version.h: Increment version number.
 
+      * subversion/tests/cmdline/svntest/main.py (SVN_VER_MINOR),
+        build/run_tests.py (SVN_VER_MINOR):
+          Increment version number.
+
       * CHANGES: New section for A.B.0.
     </pre></li>
 </ul>