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

[ju...@apache.org]

Author: julianfoad
Date: Tue Sep 17 11:13:29 2019
New Revision: 1867049

URL: http://svn.apache.org/viewvc?rev=1867049&view=rev
Log:
* publish/docs/community-guide/releasing.part.html
  (rolling-release): Update 'release.py' command-lines, removing unnecessary
    'base-dir' and 'branch' options, the latter for compatibility with r1866944.

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=1867049&r1=1867048&r2=1867049&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Sep 17 11:13:29 2019
@@ -861,7 +861,7 @@ merged into the release branch, and that
 <p><b>Create the tarballs</b>:
 Run:</p>
 <pre>
-./release.py --base-dir /opt/svnrm roll --branch branches/X.Y.x X.Y.Z 1234
+./release.py roll X.Y.Z 1234
 </pre>
 When release.py is done you'll have tarballs within the
 <tt>/opt/svnrm/deploy</tt> directory.</p> 
@@ -984,7 +984,7 @@ and append gpg signatures to the corresp
 <p>Create the tag with the <tt>svn_version.h</tt> that reflects the final
 release.  You do this using:
 <pre>
-    release.py --base-dir /opt/svnrm create-tag X.Y.Z 1234
+    release.py create-tag X.Y.Z 1234
 </pre>
 
 <p>Note: Please always make a tag, even for release candidates.</p>
@@ -999,7 +999,7 @@ branch.  If you just did 1.0.2 then both
 >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
+release.py post-candidates 1.7.0
 </pre></p>
 
 <p>Announce that the candidates are available for testing and signing:</p>