subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From julianf...@apache.org
Subject svn commit: r1469372 - /subversion/site/publish/docs/community-guide/releasing.part.html
Date Thu, 18 Apr 2013 15:28:21 GMT
Author: julianfoad
Date: Thu Apr 18 15:28:21 2013
New Revision: 1469372

URL: http://svn.apache.org/r1469372
Log:
* publish/docs/community-guide/releasing.part.html
  (release-branches): Update the release process instructions: tweak the
    CHANGES file procedure, since we now normally start the new section well
    in advance of branching; and remember to create a STATUS file on the new
    branch.

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=1469372&r1=1469371&r2=1469372&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Apr 18 15:28:21 2013
@@ -1159,15 +1159,19 @@ A.B with the version you're preparing, e
     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>
+    upcoming release if it is not already there, and also a new section
+    for the next minor release to be made in the future.  Each section
+    starts with:</p>
     <pre>
-      Version A.B.0 (released ?? ????? 20XX, from /branches/A.B.x)
+      Version A.B.0
+      (?? ??? 20XX, from /branches/A.B.x)
       http://svn.apache.org/repos/asf/subversion/tags/A.B.0
     </pre>
     <p>Leave the release date blank for now. It will remain this way
     until rolling time.</p></li>
 
-<li><p>Commit both these changes with the following log message:</p>
+<li><p>Commit these changes with a log message something like the
+    following:</p>
     <pre>
       Increment the trunk version number, and introduce a new CHANGES
       section for the upcoming A.B.0 release.
@@ -1180,6 +1184,8 @@ A.B with the version you're preparing, e
 
       * CHANGES: New section for A.B.0.
     </pre></li>
+
+<li><p>Create a new <tt>STATUS</tt> file on the release branch.</p></li>
 </ul>
 
 </div> <!-- release-branches -->



Mime
View raw message