Author: hwright
Date: Tue Jun 28 15:48:57 2011
New Revision: 1140689
URL: http://svn.apache.org/viewvc?rev=1140689&view=rev
Log:
Release-docs: Update the section on publishing and publicizing a release.
* publish/docs/community-guide/releasing.part.html
(releasing-release): Update to reflect our use of ASF infrastructure.
(releasing-announce, releasing-update-website): New sections to
encapsulate existing content.
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=1140689&r1=1140688&r2=1140689&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Jun 28
15:48:57 2011
@@ -1072,82 +1072,63 @@ so on.</p>
title="Link to this section">¶</a>
</h2>
-<!-- need to update ../../source-code.html#source-release when updating this
-->
-<p><b>Upload the tarballs to
- http://subversion.tigris.org/downloads/.</b></p>
-
-<p>We currently do this by adding and committing them to the
- <tt>/trunk/www/downloads</tt> directory of the Subversion repository
- associated with http://subversion.tigris.org/.</p>
-
-<p><b>Update Tigris "Documents & files" area</b></p>
-
-<p>Update the links to the tarballs in the Documents & files
-Tigris webapp.</p>
-
-<ol>
- <li>Log into <a href="http://subversion.tigris.org/";>Tigris</a></li>
- <li>Click on 'Documents & files'.</li>
- <li>Navigate to the 'subversion/Releases/Source code/' folder.</li>
- <li>For each of the 12 files:
- <ol>
- <li>Click on the 'Add new file' link.</li>
- <li>Fill in the following fields:
- <ul>
- <li>Name: <file name></li>
- <li>Status: Stable</li>
- <li>Description: <i>(one of:)</i>
- <ul>
- <li>Subversion release X.Y.Z (MD5: <md5sum of
- tarball>)</li>
- <li>PGP Signatures for Subversion release X.Y.Z.</li>
- </ul>
- </li>
- <li>Contents: <i>(choose 'Link', then enter:)</i>
- http://subversion.tigris.org/downloads/<file name>
- </li>
- </ul>
- </li>
- <li>Click Submit.</li>
- </ol>
- </li>
-</ol>
+<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> 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>
+
+<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><b>Announcements</b></p>
<p>Write a release announcement, referring to previous ones for
-guidance. Remember to include the URL and MD5 checksums in the
-announcement!</p>
-
-<p>Post a project news item <a
-href="http://subversion.tigris.org/servlets/ProjectNewsList";>here</a>.
-If the link reads "Suggest an announcement" instead of "Add new
-announcement", then you do not have the required permission - ask to
-be granted the 'Release Manager' Tigris role. Note that the
-Tigris news items are in HTML format not plain text.</p>
-
-<p>Send an announcement to dev@, users@, and announce@ lists. Ensure
-that your mailer doesn't wrap the URLs over multiple lines.</p>
-
-<p>You should also notify Freshmeat of the new release. For a regular
-final release, this involves adding the new release to the "Stable"
-Freshmeat project branch (click the "add release" link in the top
-navigation bar); alpha, beta, and RC releases get filed the say way,
-but under the "Development" branch. You need to be listed as a
-release manager or admin for the <a
-href="http://freshmeat.net/projects/subversion/"; >Subversion project
-on Freshmeat</a>. Contact one of the folks who are already listed if
-you need access. Your submission will also be tweaked by the
-freshmeat crew before it goes public.</p>
+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>
-<p><b>Update the website</b></p>
<ol>
- <li>Edit the <tt>^/subversion/site/publish/source-code.html</tt> page to note
- the latest release.</li>
+ <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.</li>
+ 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>
@@ -1164,6 +1145,8 @@ freshmeat crew before it goes public.</p
</ol>
+</div> <!-- release-update-website -->
+
<p>If you've made it this far, go and enjoy your $favorite_beverage now.</p>
</div> <!-- releasing-release -->
