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 2018/07/12 13:39:27 UTC

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

Author: julianfoad
Date: Thu Jul 12 13:39:27 2018
New Revision: 1835737

URL: http://svn.apache.org/viewvc?rev=1835737&view=rev
Log:
* publish/docs/community-guide/releasing.part.html
  (rolling-release): Add a cross-reference.

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=1835737&r1=1835736&r2=1835737&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Jul 12 13:39:27 2018
@@ -770,6 +770,7 @@ mkdir -p /opt/svnrm &amp;&amp; cd /opt/s
 <li>Make sure that the latest version of the <tt>CHANGES</tt> file from trunk is
 merged into the release branch, and that the date at the top of
 <tt>CHANGES</tt> matches the planned release date of the tarball.
+(See <a href="#the-changes-file">Managing the CHANGES file</a>.)
 
 <li>Make sure that get-deps.sh works on the release branch.
 </ol>