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/11/01 12:25:22 UTC

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

Author: julianfoad
Date: Thu Nov  1 12:25:22 2018
New Revision: 1845458

URL: http://svn.apache.org/viewvc?rev=1845458&view=rev
Log:
* publish/docs/community-guide/releasing.part.html
  (the-changes-file): Briefly mention 'release.py write-changelog'.

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=1845458&r1=1845457&r2=1845458&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Nov  1 12:25:22 2018
@@ -1428,6 +1428,10 @@ release stabilization section</a>.</p>
 release, it must be brought up to date to list all changes since the
 last release.</p>
 
+<p>Below, we describe the manual process. For partial automation, see
+<pre>tools/dist/release.py write-changelog</pre>
+</p>
+
 <p>For patch-releases, this is fairly easy: you just need to walk
 through the commit logs for the branch since the last "golden"
 revision, and note all interesting merges.  For minor and major