You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ju...@apache.org on 2019/09/27 15:04:04 UTC
svn commit: r1867638 -
/subversion/site/publish/docs/community-guide/releasing.part.html
Author: julianfoad
Date: Fri Sep 27 15:04:04 2019
New Revision: 1867638
URL: http://svn.apache.org/viewvc?rev=1867638&view=rev
Log:
* publish/docs/community-guide/releasing.part.html
Adjust release.py usage, following r1867623, and minor tweaks.
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=1867638&r1=1867637&r2=1867638&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Sep 27 15:04:04 2019
@@ -842,7 +842,7 @@ special build tools for Subversion RM du
software with the <tt>release.py build-env</tt> command.
<pre>
-mkdir -p /opt/svnrm && cd /opt/svnrm && $HOME/wc/svn/tools/dist/release.py build-env X.Y.Z
+mkdir -p /opt/svnrm && cd /opt/svnrm && $SVN_SRC_DIR/tools/dist/release.py build-env X.Y.Z
</pre>
</div> <!-- before-release -->
@@ -1437,7 +1437,7 @@ A.B with the version you're preparing, e
<h4>Automated</h4>
<p>Run this in an empty-ish directory where it will make some temporary checkouts:</p>
-<pre>$SVN_SRC_DIR/tools/dist/create-minor-release-branch.py create-release-branch --verbose A.B.0</pre>
+<pre>release.py --verbose create-release-branch A.B.0</pre>
<div class="notice">Some steps are not automated—highlighted below.</div>
<h4>Manual Steps</h4>
@@ -1548,7 +1548,7 @@ release, it must be brought up to date t
last release.</p>
<p>Below, we describe the manual process. For partial automation, see
-<pre>tools/dist/release.py write-changelog</pre>
+<pre>release.py write-changelog</pre>
</p>
<p>For patch-releases, this is fairly easy: you just need to walk