Author: hwright
Date: Tue Jun 28 18:25:13 2011
New Revision: 1140773
URL: http://svn.apache.org/viewvc?rev=1140773&view=rev
Log:
Release docs: a couple of minor additions, as well as a reminder to clean out
the dist/ directory after announcing the release.
* publish/docs/community-guide/releasing.part.html
(tarball-signing): Note we require three sigs on *each* platform.
(releasing-release): Fix a typo, and add a paragraph about keeping dist/
clean.
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=1140773&r1=1140772&r2=1140773&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Jun 28
18:25:13 2011
@@ -670,8 +670,9 @@ in the same directory as the tarballs.</
<p>Before a release is officially made public, it must receive three +1 votes
from members of the Subversion PMC. In addition, as a matter of project
-policy, we require testing and signatures from PMC members on <em>each</em>
-of the major platforms we support: Windows and *nix. Members of the PMC,
+policy, we require testing and signatures from at least three PMC members on
+<em>each</em> of the major platforms we support: Windows and *nix.
+Members of the PMC,
as well as enthusiastic community members are encourages to download the
tarballs from the preliminary distribution location, run the tests, and then
provide their signatures. The public keys for these signatures should be
@@ -1092,12 +1093,26 @@ previous Subversion releases are availab
<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>,
+<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"
@@ -1153,8 +1168,6 @@ [email protected].</p>
</div> <!-- release-update-website -->
-<p>If you've made it this far, go and enjoy your $favorite_beverage now.</p>
-
</div> <!-- releasing-release -->
