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 11:59:45 UTC
svn commit: r1867631 -
/subversion/site/publish/docs/community-guide/releasing.part.html
Author: julianfoad
Date: Fri Sep 27 11:59:45 2019
New Revision: 1867631
URL: http://svn.apache.org/viewvc?rev=1867631&view=rev
Log:
* publish/docs/community-guide/releasing.part.html
Adjust release.py --target option, following r1867630.
Use consistent version numbers in 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=1867631&r1=1867630&r2=1867631&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Sep 27 11:59:45 2019
@@ -89,7 +89,7 @@ In order from least- to most-stable:</p>
<td>Beta</td>
<td>We don't expect there to be problems, but be wary just in case.</td>
<td><tt>subversion-1.7.0-beta1</tt></td>
- <td>version 1.7.0 (Beta 2)</td>
+ <td>version 1.7.0 (Beta 1)</td>
</tr>
<tr>
<td>RC (Release Candidate)</td>
@@ -976,7 +976,7 @@ When release.py is done you'll have tarb
<p><b>Use GnuPG to sign release:</b></p>
Use release.py to sign the release:
<pre>
- release.py sign-candidates --target /opt/svnrm/deploy X.Y.Z
+ release.py sign-candidates X.Y.Z
</pre>
This will run the equivalent of the following commands for you:
<pre>
@@ -1120,7 +1120,7 @@ Verify the release manager's PGP signatu
automates this step:
<pre>
release.py get-keys
- release.py check-sigs 1.7.8 --target /path/to/dist/working/copy
+ release.py --target <i>/path/to/dist/dev/subversion/wc</i> check-sigs <i>1.7.0-rc4</i>
</pre>
</p>
@@ -1133,7 +1133,7 @@ To append your signature to a .asc file,
</pre>
The release.py script can automate this step:
<pre>
- release.py sign-candidates --target /path/to/dist/dev/subversion/working/copy 1.7.0
+ release.py --target <i>/path/to/dist/dev/subversion/wc</i> sign-candidates <i>1.7.0-rc4</i>
</pre>
<p>After adding your signatures, commit the locally modified .asc files
@@ -1145,8 +1145,8 @@ to download and test it separately. The
<tt>.bz2</tt> file, and pack it using <tt>gzip</tt> like this:</p>
<pre>
- bzip2 -cd subversion-1.3.0-rc4.tar.bz2 \
- | gzip -9n > subversion-1.3.0-rc4.tar.gz
+ bzip2 -cd subversion-1.7.0-rc4.tar.bz2 \
+ | gzip -9n > subversion-1.7.0-rc4.tar.gz
</pre>
<p>The resulting file should be identical to the file generated by the