Author: hwright
Date: Mon Jun 27 21:02:11 2011
New Revision: 1140320
URL: http://svn.apache.org/viewvc?rev=1140320&view=rev
Log:
Start updating the release docs for our change to ASF infrastructure. I
generally suck at writing documentation, so appreciate any editing for style
or correctness that people would like to contribute.
* publish/docs/community-guide/releasing.part.html
(before-release): Add a blurb about release.py, and remove content regarding
downloading and building dependencies.
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=1140320&r1=1140319&r2=1140320&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:02:11 2011
@@ -773,12 +773,16 @@ 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
-contain pristine versions of some build tools, as well as all the
-relevant dependancies and other stuff that gets bundled into a
-release tarball.</p>
+contain pristine versions of some build tools.</p>
<p>You need to grab vanilla source tarballs of the following build
tools before proceeding:</p>
@@ -797,23 +801,6 @@ reconsidered and increased to the latest
the time leading up to an A.B.0 release. Changing the version within
an A.B.x series should only be done with careful considereration.</p>
-<p>Also grab the following source tarballs, parts of which will be
-bundled in the Subversion release packages:</p>
-
-<ul>
-<li><p>The latest Unix <b>APR</b> and <b>APR-util</b> of the 0.9.x
-line (currently 0.9.13)</p></li>
-<li><p>The latest Win32 <b>APR</b>, <b>APR-util</b> and
-<b>APR-iconv</b> of the 0.9.x line (currently 0.9.13)</p></li>
-<li><p>The latest <b>Neon</b> 0.25.x release (currently
-0.25.5)</p></li>
-<li><p>The latest <b>zlib</b> release (currently 1.2.3)</p></li>
-</ul>
-
-<p>Once you have all this, you can start the following procedure.
-When it is done, you will have a build environment ready to roll
-tarballs.</p>
-
<p><b>Autoconf, Libtool and SWIG</b>: Pick a directory to contain your
special build tools for Subversion RM duties - for example
<tt>/opt/svnrm</tt>. Configure, build and install the three pieces of
@@ -821,23 +808,8 @@ software with <tt>--prefix=/opt/svnrm</t
run <tt>dist.sh</tt> to be sure that <tt>/opt/svnrm/bin</tt> is at the
front of your <tt>PATH</tt>.</p>
-<p><b>Dependency source preparation</b>: You should create two
-directories which will hold the dependencies which will be repackaged
-with Subversion, one for Unix and one for Win32. You might, for
-example, choose <tt>/opt/svnrm/unix-dependencies</tt> and
-<tt>/opt/svnrm/win32-dependencies</tt>. Within the Unix one, you must
-unpack the Unix APR and APR-util tarballs, and the Neon and zlib
-tarballs, and then rename each top level directory so it does
-<b>not</b> contain a version number, resulting in a directory
-containing four directories: <tt>apr</tt>, <tt>apr-util</tt>,
-<tt>neon</tt> and <tt>zlib</tt>. Within the Win32 one, you must
-unpack the Apache HTTP Server zipfile, move the <tt>apr</tt>,
-<tt>apr-util</tt> and <tt>apr-iconv</tt> directories from the
-<tt>srclib</tt> directory of the <tt>httpd</tt> zipfile into the
-dependency directory, and delete the rest of the <tt>httpd</tt>
-extract. You must then copy the <tt>neon</tt> and <tt>zlib</tt>
-directories from the Unix dependency directory into the Win32 one too.
-Do not use symlinks, <tt>dist.sh</tt> does not support them.</p>
+<p>You can do all of the forgoing with the <code>build-env</code> subcommand
+of release.py.</p>
</div> <!-- before-release -->
