Author: hwright
Date: Tue Jun 28 21:10:35 2011
New Revision: 1140849
URL: http://svn.apache.org/viewvc?rev=1140849&view=rev
Log:
Release docs: Move the releasing-release section to be a step in the
release-creating section.
* publish/docs/community-guide/releasing.part.html
(releasing-release): Move, and make an h3 instead of an h2.
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=1140849&r1=1140848&r2=1140849&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Jun 28
21:10:35 2011
@@ -725,6 +725,103 @@ manager.</p>
</div> <!-- tarball-signing -->
+<div class="h3" id="releasing-release">
+<h3>The actual releasing
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE"
-->#releasing-release"
+ title="Link to this section">¶</a>
+</h3>
+
+<p>After the tarballs are created, and all the signatures are created and
+validated, the release is ready for publication. This section outlines the
+steps needed to publish a Subversion release.</p>
+
+<p>Subversion artifacts are distributed through the
+<a href="http://www.apache.org/dev/mirrors.html";>ASF mirror network</a>. The
+source code <a href="/download/">download page</a> automatically assists users
+in selecting mirrors closer to them. We usually host only the latest stable
+release for the supported release lines on the mirror network, while all
+previous Subversion releases are available in the
+<a href="http://archive.apache.org/dist/subversion/";>archives</a>.</p>
+
+<p>Uploading releases to the mirrors is rather straight forward: the RM simply
+copies the tarballs, signatures and checksums to the
+<tt>/www/www.apache.org/dist/subversion/</tt> directory on
+<tt>people.apache.org</tt>,
+ensuring they have 644 permissions. The main distribution directory should
+update within an hour, but it takes the mirrors up to 24 hours to get pick
+up the new release. The archive will also automatically pick up the release.
+</p>
+
+<p>At this point, the release may be publicly available, but its still a good
+idea to hold off on announcing it until after the mirrors have picked it up.
+After the 24 hour period has passed, giving the mirrors enough time to sync,
+the release manager will send the announcement and public the changes to the
+Subversion website, as described below. It's also a good time to reexamine
+the <tt>dist/</tt> directory from above, and clean out any old releases; only
+the most recent release for the supported release lines should be in that
+directory. The mirrors will eventually remove the older releases, but they
+will continue to remain available in the archives.</p>
+
+<p>It is then time for the release manager to go and enjoy his
+$favorite_beverage.</p>
+
+<div class="h4" id="releasing-announce">
+<h4>Announcing the release
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE"
-->#releasing-announce"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>Write a release announcement, referring to previous ones for
+guidance. Remember to include the URL and SHA1 checksums in the
+announcement! The <tt>release.py write-announcement</tt> subcommand
+creates a template announcement which can be customized for specific
+circumstances.</p>
+
+<p>Send the announcement to dev@, users@, and announce@ lists, from your
[email protected] email address. (Mail to announce@ will bounce if sent from any
+other address.) Ensure that your mailer doesn't wrap the URLs over multiple
+lines. The mail to [email protected] will also be forwarded to
[email protected].</p>
+
+<p>Update the topics in various Subversion-related IRC channels, such as
+<tt>#svn</tt> and <tt>#svn-dev</tt> on freenode.</p>
+
+</div> <!-- release-announce -->
+
+<div class="h4" id="releasing-update-website">
+<h4>Update the website
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE"
-->#"releasing-update-website
+ title="Link to this section">¶</a>
+</h4>
+
+<ol>
+ <li>Edit the <tt>^/subversion/site/publish/download/download.html</tt> page
+ to note the latest release.</li>
+ <li>Add new News item to <tt>^/subversion/site/publish/news.html</tt>
+ announcing the release. Add the same item to the News list on
+ <tt>^/subversion/site/publish/index.html</tt>, also removing the
+ oldest News item from that page. Use <tt>release.py write-news</tt> to
+ generate a template news item, which should then be customized.</li>
+ <li>List the new release on the
+ <tt>^/subversion/site/publish/docs/release-notes/release-history.html</tt>
+ page.</li>
+ <li>Ensure that the community release support levels on
+ <tt>^/subversion/site/publish/docs/release-notes/index.html</tt>
+ are still up-to-date, tweaking as necessary.</li>
+ <li>Commit the modifications.</li>
+ <li>Create or update the versioned documentation snapshots in
+ <tt>^/site/publish/docs/api/X.Y</tt> and
+ <tt>^/site/publish/docs/javahl/X.Y</tt>, and
+ ensure that the "latest" symlinks which are siblings of those
+ directories always point to the directories of the latest release
+ series. Commit those changes, too.</li>
+
+</ol>
+
+</div> <!-- release-update-website -->
+
+</div> <!-- releasing-release -->
+
</div> <!-- release-creating -->
@@ -1073,104 +1170,6 @@ so on.</p>
</div> <!-- rolling-release -->
-<div class="h2" id="releasing-release">
-<h2>The actual releasing
- <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE"
-->#releasing-release"
- title="Link to this section">¶</a>
-</h2>
-
-<p>After the tarballs are created, and all the signatures are created and
-validated, the release is ready for publication. This section outlines the
-steps needed to publish a Subversion release.</p>
-
-<p>Subversion artifacts are distributed through the
-<a href="http://www.apache.org/dev/mirrors.html";>ASF mirror network</a>. The
-source code <a href="/download/">download page</a> automatically assists users
-in selecting mirrors closer to them. We usually host only the latest stable
-release for the supported release lines on the mirror network, while all
-previous Subversion releases are available in the
-<a href="http://archive.apache.org/dist/subversion/";>archives</a>.</p>
-
-<p>Uploading releases to the mirrors is rather straight forward: the RM simply
-copies the tarballs, signatures and checksums to the
-<tt>/www/www.apache.org/dist/subversion/</tt> directory on
-<tt>people.apache.org</tt>,
-ensuring they have 644 permissions. The main distribution directory should
-update within an hour, but it takes the mirrors up to 24 hours to get pick
-up the new release. The archive will also automatically pick up the release.
-</p>
-
-<p>At this point, the release may be publicly available, but its still a good
-idea to hold off on announcing it until after the mirrors have picked it up.
-After the 24 hour period has passed, giving the mirrors enough time to sync,
-the release manager will send the announcement and public the changes to the
-Subversion website, as described below. It's also a good time to reexamine
-the <tt>dist/</tt> directory from above, and clean out any old releases; only
-the most recent release for the supported release lines should be in that
-directory. The mirrors will eventually remove the older releases, but they
-will continue to remain available in the archives.</p>
-
-<p>It is then time for the release manager to go and enjoy his
-$favorite_beverage.</p>
-
-<div class="h4" id="releasing-announce">
-<h4>Announcing the release
- <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE"
-->#releasing-announce"
- title="Link to this section">¶</a>
-</h4>
-
-<p>Write a release announcement, referring to previous ones for
-guidance. Remember to include the URL and SHA1 checksums in the
-announcement! The <tt>release.py write-announcement</tt> subcommand
-creates a template announcement which can be customized for specific
-circumstances.</p>
-
-<p>Send the announcement to dev@, users@, and announce@ lists, from your
[email protected] email address. (Mail to announce@ will bounce if sent from any
-other address.) Ensure that your mailer doesn't wrap the URLs over multiple
-lines. The mail to [email protected] will also be forwarded to
[email protected].</p>
-
-<p>Update the topics in various Subversion-related IRC channels, such as
-<tt>#svn</tt> and <tt>#svn-dev</tt> on freenode.</p>
-
-</div> <!-- release-announce -->
-
-<div class="h4" id="releasing-update-website">
-<h4>Update the website
- <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE"
-->#"releasing-update-website
- title="Link to this section">¶</a>
-</h4>
-
-<ol>
- <li>Edit the <tt>^/subversion/site/publish/download/download.html</tt> page
- to note the latest release.</li>
- <li>Add new News item to <tt>^/subversion/site/publish/news.html</tt>
- announcing the release. Add the same item to the News list on
- <tt>^/subversion/site/publish/index.html</tt>, also removing the
- oldest News item from that page. Use <tt>release.py write-news</tt> to
- generate a template news item, which should then be customized.</li>
- <li>List the new release on the
- <tt>^/subversion/site/publish/docs/release-notes/release-history.html</tt>
- page.</li>
- <li>Ensure that the community release support levels on
- <tt>^/subversion/site/publish/docs/release-notes/index.html</tt>
- are still up-to-date, tweaking as necessary.</li>
- <li>Commit the modifications.</li>
- <li>Create or update the versioned documentation snapshots in
- <tt>^/site/publish/docs/api/X.Y</tt> and
- <tt>^/site/publish/docs/javahl/X.Y</tt>, and
- ensure that the "latest" symlinks which are siblings of those
- directories always point to the directories of the latest release
- series. Commit those changes, too.</li>
-
-</ol>
-
-</div> <!-- release-update-website -->
-
-</div> <!-- releasing-release -->
-
-
<div class="h2" id="releasing-not">
<h2>How <em>not</em> to make a Subversion release
<a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE"
-->#releasing-not"
