Author: hwright
Date: Mon Jun 27 21:29:03 2011
New Revision: 1140329
URL: http://svn.apache.org/viewvc?rev=1140329&view=rev
Log:
Add something of a preface to the release management docs, and move the
paragraph about release.py to that section.
* publish/docs/community-guide/releasing.part.html:
Add the preface material.
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=1140329&r1=1140328&r2=1140329&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Mon Jun 27
21:29:03 2011
@@ -6,6 +6,27 @@
<!--#include virtual="releasing.toc.html" -->
+<p>This document can generally be broken in to three parts, in increasing
+order of specificity:</p>
+<ul>
+<li>High-level release planning and policies, such as version numbering and
+ compatibility. This answers questions like "When does a tarball get
+ created?" and "What should be the content of a tarball?"</li>
+<li>What steps to take when it is time to create a release. This section
+ addresses the question of "How do I manage a release?"</li>
+<li>How to constructing a set of release tarballs. This section discusses
+ the steps required to go from source code in the repository to a set of
+ distributable <code>.tar.gz</code> or <code>.zip</code> files with the
+ desired content.</li>
+<li>
+</ul>
+
+<p>Subversion release managers use a set of steps codified in a Python script
+named <code><a
href="http://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py";>release.py</a></code>.
+This script can be used to perform most of the automated steps in the steps
+in the release process. Run it with the <code>-h</code> 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"
@@ -773,12 +794,6 @@ branch when a patch release is made.</p>
title="Link to this section">¶</a>
</h2>
-<p>Subversion release managers use a set of steps codified in a Python script
-named <code><a
href="http://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py";>release.py</a></code>.
-This script can be used to perform most of the automated steps in the steps
-in the release process. Run it with the <code>-h</code> option to get more
-information.</p>
-
<p>So, a release branch has stabilized, and you are gearing up to roll
the release. Before you can actually roll the archives, you need to
set up a white-room rolling environment. This environment must
