Author: hartmannathan
Date: Fri Dec 1 04:39:35 2023
New Revision: 1914249
URL: http://svn.apache.org/viewvc?rev=1914249&view=rev
Log:
In site/staging:
* docs/community-guide/releasing.part.html:
(#adding-changes): Add a clarifying paragraph and a hint for future
patch-release managers about an easy way to list backports that
deserve mention in CHANGES.
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=1914249&r1=1914248&r2=1914249&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Fri Dec 1
04:39:35 2023
@@ -1766,6 +1766,20 @@ should also add an item to <tt>CHANGES</
guidelines outlined above. This list will then be merged to the release
branch when a patch release is made.</p>
+<p>In practice, CHANGES does not get updated each time a fix is
+backported to the release branch. Normally, the release manager updates
+CHANGES as one of the first steps to make a patch release.</p>
+
+<p>A convenient way to get the list of backports that should be mentioned
+in CHANGES is to use the same tool that populates
+<a
href="https://subversion.apache.org/docs/release-notes/#upcoming-patch-release";
+>Coming up in the next patch release</a> on the Subversion website. This is
+the <tt>upcoming.py</tt> script in
+<a href="https://svn.apache.org/repos/asf/subversion/site/tools";
+>https://svn.apache.org/repos/asf/subversion/site/tools</a>. Run it while
+the current working directory is the root of a working copy of the minor
+branch.</p>
+
</div> <!-- adding-changes -->
</div> <!-- the-changes-file -->
