You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ds...@apache.org on 2022/07/14 19:51:28 UTC
svn commit: r1902723 - /subversion/site/staging/docs/community-guide/releasing.part.html
Author: dsahlberg
Date: Thu Jul 14 19:51:28 2022
New Revision: 1902723
URL: http://svn.apache.org/viewvc?rev=1902723&view=rev
Log:
In site/staging:
Remove the option to run release.py in a shallow working copy.
release.py get-keys (as of r1902722) requires COMMITTERS to be part
of the WC.
We could update release.py to download COMMITTERS directly from the repository
but having less variations to the release process should decrease the chance
of an unnoticed snag.
* community-guide/releasing.part.html:
(#before-release-pristine-tools): As above
Modified:
subversion/site/staging/docs/community-guide/releasing.part.html
Modified: subversion/site/staging/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1902723&r1=1902722&r2=1902723&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Thu Jul 14 19:51:28 2022
@@ -827,8 +827,7 @@ time pass.</p>
the release. The details of the rolling process are automated by the
<a href="https://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py">release.py</a>
helper script. To run this script, you'll need a Subversion trunk working
-copy (or a shallow trunk working copy containing the <tt>tools/dist</tt> and
-<tt>build/generator</tt> directories). Run <tt>release.py -h</tt> to get a
+copy. Run <tt>release.py -h</tt> to get a
list of available subcommands.</p>
<p>Before you can actually roll the archives, you need to
Re: svn commit: r1902723 - /subversion/site/staging/docs/community-guide/releasing.part.html
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
dsahlberg@apache.org wrote on Thu, 14 Jul 2022 19:51 +00:00:
> +++ subversion/site/staging/docs/community-guide/releasing.part.html Thu Jul 14 19:51:28 2022
> @@ -827,8 +827,7 @@ time pass.</p>
> To run this script, you'll need a Subversion trunk working
> -copy (or a shallow trunk working copy containing the <tt>tools/dist</tt> and
> -<tt>build/generator</tt> directories).
> +copy.
How about keeping the parenthesized list and adding COMMITTERS to it?
This would make it easier to minimize dependencies on the trunk tree,
which would be a good thing (e.g., it would be harder to accidentally
use trunk's svn_version.h instead of a branch's).
Re: svn commit: r1902723 - /subversion/site/staging/docs/community-guide/releasing.part.html
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
dsahlberg@apache.org wrote on Thu, 14 Jul 2022 19:51 +00:00:
> +++ subversion/site/staging/docs/community-guide/releasing.part.html Thu Jul 14 19:51:28 2022
> @@ -827,8 +827,7 @@ time pass.</p>
> To run this script, you'll need a Subversion trunk working
> -copy (or a shallow trunk working copy containing the <tt>tools/dist</tt> and
> -<tt>build/generator</tt> directories).
> +copy.
How about keeping the parenthesized list and adding COMMITTERS to it?
This would make it easier to minimize dependencies on the trunk tree,
which would be a good thing (e.g., it would be harder to accidentally
use trunk's svn_version.h instead of a branch's).