svn commit: r1304402 - /subversion/site/publish/docs/community-guide/releasing.part.html

[st...@apache.org]

Author: stsp
Date: Fri Mar 23 15:02:42 2012
New Revision: 1304402

URL: http://svn.apache.org/viewvc?rev=1304402&view=rev
Log:
* site/publish/docs/community-guide/releasing.part.html: Fix mistaken
   release.py usage examples.

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=1304402&r1=1304401&r2=1304402&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Mar 23 15:02:42 2012
@@ -836,6 +836,14 @@ and copy from the working copy to the ta
 1.0.2 then <tt>svn_version.h</tt> should have the proper values for 1.0.3 and
 so on.</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>
+
 </div> <!-- rolling-release -->
 
 <div class="h3" id="tarball-signing">
@@ -954,7 +962,7 @@ to <a href="https://dist.apache.org/repo
 >https://dist.apache.org/repos/dist/release/subversion</a>
 There is a release.py subcommand that automates this step:
 <pre>
-release.py post-candidates 1.7.0
+release.py move-to-dist 1.7.0
 </pre>
 It takes the mirrors up to 24 hours to get pick up the new release.
 The archive will also automatically pick up the release.