Update 1.14 release notes

Signed-off-by: James McCoy <jamessan@debian.org>

1 files changed, 97 insertions, 48 deletions

diff --git a/debian/svn_1.14_releasenotes.html b/debian/svn_1.14_releasenotes.html
index 3a7d904..8b8dd8d 100644
--- a/debian/svn_1.14_releasenotes.html
+++ b/debian/svn_1.14_releasenotes.html
@@ -125,15 +125,7 @@
 
 <h1 style="text-align: center">Apache Subversion 1.14 LTS Release Notes</h1>
 
-<div class="notice">
-<p><span style="color: red"><b>This is work in progress.
-  Subversion 1.14 has not been released yet.</b></span></p>
-</div>
-
 <!-- ### -->
-<p class="todo">TODO: If making an alpha release before branching
-1.14.x, links to files in ViewVC may need to be temporarily pointed at
-trunk.</p> <!-- And don't forget to change them back!!! -->
 
 <div class="h2" id="news">
 <h2>What's New in Apache Subversion 1.14
@@ -233,8 +225,8 @@ and what impact these changes may have.</p>
     <td><a href="#svnadmin-build-repcache"><tt>svnadmin build-repcache</tt></a></td>
     <td>n/a</td>
     <td>1.14</td>
-    <td>FSFS version 6</td>
-    <td></td></tr>
+    <td>FSFS format 4</td>
+    <td>see <tt>Filesystem Format</tt> in the output of <tt>svnadmin info /path/to/repo</tt></td></tr>
   <tr>
     <td>
       <a href="#shelving">Shelving (experimental)</a>
@@ -429,7 +421,7 @@ process all revisions.</p>
 
 <div class="h4" id="log-quiet-diff">
 <h4><tt>svn log </tt> improvements
-  <a class="sectionlink" href="#log-search"
+  <a class="sectionlink" href="#log-quiet-diff"
      title="Link to this section">&para;</a>
 </h4>
 
@@ -441,7 +433,7 @@ in a range of revisions. (See <a href="http://svn.apache.org/r1871916">r1871916<
 
 <div class="h4" id="info-show-item-changelist">
 <h4><tt>svn info </tt> improvements
-  <a class="sectionlink" href="#log-search"
+  <a class="sectionlink" href="#info-show-item-changelist"
      title="Link to this section">&para;</a>
 </h4>
 
@@ -452,7 +444,7 @@ in a range of revisions. (See <a href="http://svn.apache.org/r1871916">r1871916<
 
 <div class="h4" id="editor-filename-escaping">
 <h4>Escaping/quoting of pathname arguments to the user-defined editor
-  <a class="sectionlink" href="#log-search"
+  <a class="sectionlink" href="#editor-filename-escaping"
      title="Link to this section">&para;</a>
 </h4>
 
@@ -672,14 +664,14 @@ To show experimental commands, use <tt>svn help -v</tt> or
 </div> <!-- help-hide-experimental -->
 
 <div class="h4" id="sqlite-omit-wal">
-<h4>Improved performance for working copy commands like <tt>svn st</tt>
+<h4>Improved performance for working copy commands like <tt>svn status</tt>
   <a class="sectionlink" href="#sqlite-omit-wal"
      title="Link to this section">&para;</a>
 </h4>
 
 <p>This change was first introduced in 1.13.</p>
 
-<p>Some local operations, such as <tt>svn st</tt> on a large working copy,
+<p>Some local operations, such as <tt>svn status</tt> on a large working copy,
 now perform more quickly as a result of reduced I/O. This is achieved by
 disabling SQLite's WAL (write-ahead logging) feature, which Subversion does
 not use, but which introduces more I/O when left enabled.
@@ -840,16 +832,6 @@ language.</p>
 <p>Subversion's SWIG Python bindings and Subversion's test suite now
 support Python 3.x (and newer).</p>
 
-<!-- ### -->
-<p class="todo">TODO: Describe which minor releases of Python 3.x we
-plan to support through the four-year LTS period of Subversion 1.14.
-Per recent discussions on the dev@ mailing list, that might be some
-form of "rolling" support: In each 1.14.x patch release, we would make
-an effort to support the oldest through newest minor lines of Python
-3.x that Python upstream supports at the time of our release. However,
-we could drop support for the oldest one if we have a compelling
-reason to do so.</p>
-
 <p>Of course, we welcome contributions that extend Subversion's Python
 support to include other versions, subject to the project's other needs.
 See the section
@@ -1040,6 +1022,12 @@ Also, changes have been made under the hood to support a related feature,
 Commit Checkpointing (<a href="https://issues.apache.org/jira/browse/SVN-3626"
 >issue #3626</a>).</p>
 
+<p>You can read <a href="https://cwiki.apache.org/confluence/x/MxbcC">a
+review</a> of the development of experimental support for shelving to find
+out more about the differences between the versions, and the further work
+that would be needed in Subversion to make shelving a first-class
+feature.</p>
+
 <div class="notice">
   <p>Shelving in 1.14 is incompatible with shelves created by 1.10. See
   <a href="#shelving-transition">Upgrading 1.10&ndash;1.13 shelves to 1.14</a>
@@ -1090,7 +1078,8 @@ two available shelving CLI implementations by setting an environment variable
 <p>The two implementations are "Shelving-v2" as introduced in 1.11, and
 "Shelving-v3" as introduced in 1.12. These are incompatible with each other,
 but both are offered because they have substantially different pros and
-cons.</p>
+cons. (See <a href="https://cwiki.apache.org/confluence/x/MxbcC">the
+review</a>.)</p>
 
 <p>The shelving CLI implementation is selected by an environment variable,
 <tt>SVN_EXPERIMENTAL_COMMANDS</tt>, as follows:</p>
@@ -1193,6 +1182,9 @@ the following kinds which it does not support:</p>
     <li>creating and deleting directories</li>
 </ul>
 
+<p>Shelves created by Shelving-v2 are stored under
+<tt><i>&lt;WC&gt;</i>/.svn/experimental/shelves/v2</tt>.</p>
+
 </div>  <!-- shelving-v2 -->
 
 <div class="h4 experimental-feature" id="shelving-v3">
@@ -1211,6 +1203,9 @@ under the hood to eventually support better shelving, commit checkpointing,
 and the possibility of future client-side features for manipulating and
 sharing committable changes.</p>
 
+<p>Shelves created by Shelving-v3 are stored under
+<tt><i>&lt;WC&gt;</i>/.svn/experimental/shelves/v3</tt>.</p>
+
 </div>  <!-- shelving-v3 -->
 
 <div class="h4 experimental-feature" id="shelving-transition">
@@ -1219,25 +1214,26 @@ sharing committable changes.</p>
     title="Link to this section">&para;</a>
 </h4>
 
-<p>The presence in the working copy of any shelves that were created by
-Subversion 1.10 has no effect on a Subversion 1.14 client. Subversion 1.14
-will ignore them; it cannot interoperate with them nor even list their
-presence.</p>
-
-<p>The <tt>svn upgrade</tt> command has no effect, as the working copy
-format is formally unchanged.</p>
+<p>The presence in the working copy of any shelves created by Subversion 1.10
+has no effect on a Subversion 1.14 client. Subversion 1.14 will ignore them;
+it cannot interoperate with them nor even list their presence.</p>
 
-<p>In Subversion 1.14, shelves are stored under
-<tt><i>&lt;WC&gt;</i>/.svn/experimental/shelves/</tt>. In Subversion 1.10,
-shelves were stored under <tt><i>&lt;WC&gt;</i>/.svn/shelves/</tt> as patch
-files.</p>
+<p>The <tt>svn upgrade</tt> command has no effect on shelves, as the
+working copy format is formally unchanged.</p>
 
 <p>To recover a shelf created by 1.10, either
 <ul><li>use a 1.10 client to find and unshelve it, or</li>
-    <li>find the patch file by hand and use any 1.10 or later
-        <tt>svn patch</tt> to apply it.</li>
+    <li>as 1.10 shelves are stored as patch files under
+        <tt><i>&lt;WC&gt;</i>/.svn/shelves/</tt>, find the patch file and
+        use any 1.10&ndash;1.14 or later <tt>svn patch</tt> to apply it.</li>
 </ul></p>
 
+<p>To access shelves created by 1.11, first select Shelving-v2 by setting the
+environment variable <tt>SVN_EXPERIMENTAL_COMMANDS=shelf2</tt>.</p>
+
+<p>To access shelves created by 1.12&ndash;1.13, first select Shelving-v3 by
+setting the environment variable <tt>SVN_EXPERIMENTAL_COMMANDS=shelf3</tt>.</p>
+
 </div>  <!-- shelving-transition -->
 
 <div class="h4 experimental-feature" id="shelving-checkpointing">
@@ -1353,14 +1349,49 @@ may be fixed in later 1.14.x releases.</p>
     title="Link to this section">&para;</a>
 </h3>
 
-Some Python scripts that are included in Subversion's release
-distribution do not support Python 3 yet. 
+<p>Some Python scripts that are included in Subversion's release
+distribution do not support Python 3 yet.</p>
 
-For an exhaustive list of all Python scripts and files that use
-Python, categorized by their Python 3 support status, see the
-<a href="https://cwiki.apache.org/confluence/display/SVN/Subversion%27s+Python+3+Support+Status"
->Subversion's Python 3 Support Status</a> wiki page.
-</p>
+<p>For an exhaustive list of all Python scripts and files that use
+Python, categorized by their Python 3 support status as of the
+1.14.0 release, see <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=138021580"
+>Subversion's Python 3 Support Status</a> wiki page.</p>
+
+<p>The <a href="https://cwiki.apache.org/confluence/display/SVN/Subversion%27s+Python+3+Support+Status"
+>latest version</a> of that page reflects changes made after
+the release, which may be included in future releases.</p>
+
+<div class="h4" id="autogen_sh-py2-py3">
+<h4>The build system prefers Python 2 to Python 3
+  <a class="sectionlink" href="#autogen_sh-py2-py3"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>Although <a href="#pythonoptional">Python is not required for building
+Subversion</a>, it <em>is</em> required for running the test suite, and
+therefore, on Unix-like systems, Subversion's build system looks for a Python
+executable.</p>
+
+<p>The build system checks the environment variables <tt>$PYTHON</tt>,
+<tt>$PYTHON2</tt>, and <tt>$PYTHON3</tt> in this order, followed by the command
+names <tt>python</tt>, </tt>python2</tt>, and <tt>python3</tt> (in
+<tt>$PATH</tt>) in this order.  The first of these that is an executable
+implementing Python version 2.7 or greater is used.</p>
+
+<p>Since <a href="#python2">support for Python 2.7 is being phased out</a>, we
+expect to change this to prefer Python 3 to Python 2.7 in a 1.14.x patch release.
+When we do, we will mention the change in the <tt>CHANGES</tt> file and update
+this section of the release notes.</p>
+
+<p>This affects both tarball builds (using <tt>configure</tt>) and working copy
+builds (using <tt>autogen.sh</tt>).  The release rolling scripts are also
+affected.</p>
+
+<p>As a workaround, the environment variable <tt>PYTHON</tt> may be set to the
+full path of a Python 3 executable prior to running <tt>configure</tt> (or
+<tt>autogen.sh</tt>, if you build from a working copy).</p>
+
+</div> <!-- autogen_sh-py2-py3 -->
 
 </div>  <!-- python3-work-in-progress -->
 
@@ -1428,6 +1459,20 @@ if they occur.</p>
 
 </div>  <!-- lts-release -->
 
+<div class="h3" id="svn-1.13-deprecation">
+<h3>Subversion 1.13.x is end of life
+  <a class="sectionlink" href="#svn-1.13-deprecation"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>The Subversion 1.13.x line is end of life (<abbr title="End Of Life">EOL</abbr>).
+This doesn't mean that your 1.13 installation is doomed; if it works
+well and is all you need, that's fine.  "End of life" just means we've
+stopped accepting bug reports against 1.13.x versions, and will not
+make any more 1.13.x releases.</p>
+
+</div>  <!-- svn-1.13-deprecation -->
+
 <div class="h3" id="svn-1.10-old-stable">
 <h3>Subversion 1.10.x is now the old stable version
   <a class="sectionlink" href="#svn-1.10-old-stable"
@@ -1493,10 +1538,14 @@ https://subversion.apache.org/mailing-lists.html</a></p>
 
 <p>Get the source:</p>
 <ul>
-  <li>Check out Subversion's source using Subversion:
+  <li>Check out Subversion's source:
     <pre>$ svn checkout https://svn.apache.org/repos/asf/subversion/trunk/</pre></li>
 
-  <li>or download the latest release tarball:
+  <!-- TODO: Use the URL to the *.apache.org mirror of subversion.git -->
+  <li>For those who prefer it, a Git mirror is also available:
+    <pre>$ git clone https://github.com/apache/subversion.git</pre></li>
+
+  <li>Or download the latest release tarball:
     <a href="https://subversion.apache.org/download.cgi"
     >https://subversion.apache.org/download.cgi</a></li>
 </ul>