subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1851048 - /subversion/site/publish/docs/release-notes/index.html
Date Fri, 11 Jan 2019 13:38:07 GMT
Author: julianfoad
Date: Fri Jan 11 13:38:07 2019
New Revision: 1851048

* publish/docs/release-notes/index.html
  (upcoming-patch-release): Improve the description. Link to the generator script.


Modified: subversion/site/publish/docs/release-notes/index.html
--- subversion/site/publish/docs/release-notes/index.html (original)
+++ subversion/site/publish/docs/release-notes/index.html Fri Jan 11 13:38:07 2019
@@ -77,17 +77,15 @@ official support status for the various
     title="Link to this section">&para;</a>
-<p>These are the changes that have been merged to the 1.11.x branch since the last
1.11.x patch release.</p>
+<p>The following changes have been merged to the 1.11.x branch since the last 1.11.x
patch release will almost certainly be included in the next 1.11.x patch release:</p>
-<p>These changes are almost certainly going to be in the next 1.11.x patch release;
any of them <i>may</i> be reverted before the release is made, but probably won't
be. More changes besides these may be added.</p>
+<!--#include virtual="/upcoming.part.html" -->
-<p>Further changes currently nominated for inclusion are listed in <a href="">1.11.x/STATUS</a>
along with their current voting status. These may get in to the next release if they reach
the 'Approved' category in time.</p>
+<p>Further changes currently under consideration are listed in <a href="">1.11.x/STATUS</a>.</p>
 <p>See also <a href="">trunk/CHANGES</a>,
where all significant-enough changes will summarized for each version by the time it is released.</p>
-<p>Different lists of changes are queued for older supported release lines (1.10.x,
1.9.x), not shown here.</p>
-<!--#include virtual="/upcoming.part.html" -->
+<p>The list above is generated daily by <a href="">^/subversion/site/tools/</a>.
You could find the changes queued for another supported release line by running that script
in a working copy of, for example, the 1.10.x branch.</p>
 </div> <!-- #upcoming-patch-release -->

View raw message