Author: julianfoad
Date: Mon Feb 26 20:49:47 2018
New Revision: 1825411
URL: http://svn.apache.org/viewvc?rev=1825411&view=rev
Log:
* publish/docs/community-guide/releasing.part.html
(releasing-release): A little more clarity.
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=1825411&r1=1825410&r2=1825411&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Mon Feb 26
20:49:47 2018
@@ -1088,12 +1088,17 @@ unless 24 hours have passed since they w
idea to hold off on announcing it until after the mirrors have picked it up.
After the 24 hour period has passed, giving the mirrors enough time to sync,
the release manager will send the announcement and publish the changes to the
-Subversion website, as described below. It's also a good time to reexamine
-the <tt>dist/</tt> directory from above, and clean out any old releases; only
-the most recent release for the supported release lines should be in that
+Subversion website, as described below.</p>
+
+<p>It's also a good time to clean out any old releases from
+<tt>^/release/subversion</tt>; only
+the most recent release for each supported release line should be in that
directory. The mirrors will eventually remove the older releases, but they
-will continue to remain available in the archives. (You can clean old
-releases using <tt>release.py clean-dist</tt>.)
+will continue to remain available in the archives. You can clean old
+releases using:
+<pre>
+release.py clean-dist
+</pre>
</p>
<div class="h4" id="releasing-press">
