subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From danie...@apache.org
Subject svn commit: r1850267 - /subversion/site/staging/docs/release-notes/index.html
Date Thu, 03 Jan 2019 20:33:09 GMT
Author: danielsh
Date: Thu Jan  3 20:33:09 2019
New Revision: 1850267

URL: http://svn.apache.org/viewvc?rev=1850267&view=rev
Log:
[in staging]
* docs/release-notes/index.html
  (#upcoming-patch-release): Add the merges since 1.11.0 (currently, a rough sketch).

Modified:
    subversion/site/staging/docs/release-notes/index.html

Modified: subversion/site/staging/docs/release-notes/index.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/index.html?rev=1850267&r1=1850266&r2=1850267&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/index.html (original)
+++ subversion/site/staging/docs/release-notes/index.html Thu Jan  3 20:33:09 2019
@@ -71,6 +71,22 @@ official support status for the various
 <p>For a detailed history of every release, please see
    <a href="release-history.html">release history</a>.</p>
 
+<div class="h3" id="upcoming-patch-release">
+<h3>Coming up in the next patch release
+  <a class="sectionlink" href="#upcoming-patch-release"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p class="todo">Write something explaining these <i>may</i> be reverted
(but probably won't be), that the list may different between 1.11.next and 1.10.next, and
that more changes besides these may be added</p>
+
+<p class="todo">Link to STATUS</p>
+
+<p class="todo">The generating script hardcodes 1.11.0; make it find the last patch
release by itself.</p>
+
+<iframe src="/upcoming.part.html"/>
+
+</div> <!-- #upcoming-patch-release -->
+
 </div> <!-- #release-notes -->
 
 <div class="h2" id="supported-versions">



Mime
View raw message