subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bre...@apache.org
Subject svn commit: r1426327 - /subversion/site/publish/docs/community-guide/releasing.part.html
Date Thu, 27 Dec 2012 21:06:02 GMT
Author: breser
Date: Thu Dec 27 21:06:01 2012
New Revision: 1426327

URL: http://svn.apache.org/viewvc?rev=1426327&view=rev
Log:
Include a step for announcing candidates in our documentation.

* publish/docs/community-guide/releasing.part.html
  (rolling-release): Mention that you need to announce the candiates and
    wrap the post-candidates step in a paragraph element. 

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=1426327&r1=1426326&r2=1426327&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Dec 27 21:06:01 2012
@@ -857,13 +857,16 @@ release.  You do this using:
 branch.  If you just did 1.0.2 then both files should have the proper value for
 1.0.3 and so on.</p>
 
-Commit the tarballs, signatures and checksums to
+<p>Commit the tarballs, signatures and checksums to
 <a href="https://dist.apache.org/repos/dist/dev/subversion"
 >https://dist.apache.org/repos/dist/dev/subversion</a>
 There is a release.py subcommand that automates this step:
 <pre>
 release.py --base-dir /opt/svnrm post-candidates 1.7.0
-</pre>
+</pre></p>
+
+<p>Announce that the candidates are available for testing by sending an email
+to the dev@ list and by adjusting the topic on #svn-dev.</p>
 
 </div> <!-- rolling-release -->
 



Mime
View raw message