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

[hwright]

Author: hwright
Date: Tue Jun 28 02:12:24 2011
New Revision: 1140399

URL: http://svn.apache.org/viewvc?rev=1140399&view=rev
Log:
Start encapsulating the various bits of the release document into the three
sections mentioned in the preface.  This is partly a test commit to see how
the styles shake out, since I don't have a full httpd instance running on my
laptop.  (Shame on me, I know.)

* publish/docs/community-guide/releasing.part.html
  (release-process): New h2-level section.
  (release-numbering, name-reuse, deprecation): Bump all these down one
    header level and put them in release-process.

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=1140399&r1=1140398&r2=1140399&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Jun 28 
02:12:24 2011
@@ -26,12 +26,19 @@ This script can be used to perform most 
 in the release process.  Run it with the <tt>-h</tt> option to get more
 information.</p>
 
-<div class="h2" id="release-numbering">
-<h2>Release numbering, compatibility, and deprecation
-  <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" 
-->#release-numbering"
+<div class="h2" id="release-process">
+<h2>Subversion release process
+  <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" 
-->#release-process"
     title="Link to this section">&para;</a>
 </h2>
 
+
+<div class="h3" id="release-numbering">
+<h3>Release numbering, compatibility, and deprecation
+  <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" 
-->#release-numbering"
+    title="Link to this section">&para;</a>
+</h3>
+
 <p>Subversion uses "MAJOR.MINOR.PATCH" release numbers, with the same
 guidelines as APR (see <a href="http://apr.apache.org/versioning.html";
 >http://apr.apache.org/versioning.html</a>), plus a few extensions,
@@ -192,11 +199,11 @@ reports.</p>
 code to get wider distribution than just those who build from working
 copies, we put out a prerelease.</p>
 
-<div class="h3" id="name-reuse">
-<h3>Reuse of release names
+<div class="h4" id="name-reuse">
+<h4>Reuse of release names
   <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" 
-->#name-reuse"
     title="Link to this section">&para;</a>
-</h3>
+</h4>
 
 <p>If a release or candidate release needs to be quickly re-issued due
 to some non-code problem (say, a packaging glitch), it's okay to reuse
@@ -208,11 +215,11 @@ old name must be tossed and the next nam
 
 </div> <!-- name-reuse -->
 
-<div class="h3" id="deprecation">
-<h3>Deprecation
+<div class="h4" id="deprecation">
+<h4>Deprecation
   <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" 
-->#deprecation"
     title="Link to this section">&para;</a>
-</h3>
+</h4>
 
 <p>When a new, improved version of an API is introduced, the old one
 remains for compatibility, at least until the next major release.
@@ -265,6 +272,8 @@ because its new name is fine.</p>
 
 </div> <!-- release-numbering -->
 
+</div> <!-- release-process -->
+
 
 <div class="h2" id="release-stabilization">
 <h2>Stabilizing and maintaining releases