Update 1.10 releasenotes

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

1 files changed, 53 insertions, 76 deletions

diff --git a/debian/svn_1.10_releasenotes.html b/debian/svn_1.10_releasenotes.html
index c30107a..c1e711b 100644
--- a/debian/svn_1.10_releasenotes.html
+++ b/debian/svn_1.10_releasenotes.html
@@ -118,13 +118,6 @@
 
 <h1 style="text-align: center">Apache Subversion 1.10 Release Notes</h1>
 
-<div class="notice">
-<p><span style="color: red"><b>This is work in progress.
-  Subversion 1.10 has not been released yet.<br>
-  2018-03-23 status: Blocker bugs found in RC1; RC2 coming soon (<a href="/roadmap.html">Roadmap</a>, <a href="https://issues.apache.org/jira/browse/SVN-4712">issue SVN-4712</a>)
-  </b></span></p>
-</div>
-
 <div class="h2" id="news">
 <h2>What's New in Apache Subversion 1.10
   <a class="sectionlink" href="#news"
@@ -139,7 +132,7 @@
   <li><a href="#lz4"
       >LZ4 Compression</a></li>
   <li><a href="#shelving"
-      >Shelving</a></li>
+      >Shelving (experimental)</a></li>
   <li><a href="#enhancements"
       >Many enhancements and bug fixes</a></li>
   <li><a href="#issues"
@@ -181,14 +174,6 @@ Subversion 1.10 servers can read and write to repositories created by
 earlier versions.  To upgrade an existing server installation, just install the
 newest libraries and binaries on top of the older ones.</p>
 
-<p>Please note that <tt>svnadmin create</tt> will by default create
-repositories using the new <a href="#fsfs-format8">filesystem format 8</a>.
-Until Subversion 1.10 is generally available, <b>no upgrade path is
-promised</b> for repositories with this new filesystem format.  Please do
-not use newly created repositories for any data meant for long-term
-safe-keeping.  See our <a href="/prerelease-caveats">policy for
-pre-releases</a> for additional information.</p>
-
 <p>Subversion 1.10 maintains API/ABI compatibility with earlier
 releases, by only adding new functions, never removing old ones.  A
 program written to any previous 1.x API can both compile
@@ -244,7 +229,7 @@ and what impact these changes may have.</p>
       <a href="#lz4">LZ4 compression in the backend storage</a>
     </td>
     <td>any</td>
-    <td>any</td>
+    <td>1.10</td>
     <td>1.10</td>
     <td>FSFS only</td></tr>
   <tr>
@@ -285,21 +270,22 @@ to the upgrade.</p>
 
 </div>  <!-- wc-upgrade -->
 
+<!-- TODO:
 <div class="h3" id="protocol-changes">
 <h3>Client-Server Protocol Changes
   <a class="sectionlink" href="#protocol-changes"
     title="Link to this section">&para;</a>
 </h3>
 
-<p>LZ4...</p>
-
-<p>Negotiating compression in RA-serf...</p>
+<p>LZ4 compression: see <a href="#fsfs-lz4-configuration">Configuring the
+repository to use LZ4 compression</a> below.</p>
 
 <p>List with search...</p>
 
 <p>...</p>
 
-</div>  <!-- protocol-changes -->
+</div>
+-->
 
 <div class="h3" id="compat-misc">
 <h3>Miscellaneous Compatibility Notes
@@ -643,10 +629,6 @@ with filesystem format 8.  Also, Subversion 1.10 adds support for automatic
 negotiation and use of LZ4 compression over the wire for http:// and svn://
 connections when it is supported by both endpoints.</p>
 
-<p><b>Note:</b> this does not apply to the pre-release
-<a href="https://lists.apache.org/thread.html/dd78432b301f3f95567930c242c46b308c8a017fd754c0f388245915@%3Cannounce.subversion.apache.org%3E">Subversion 1.10.0-alpha3</a>
-version, which still uses zlib compression by default.
-
 <div class="h4" id="fsfs-format8">
 <h4>Filesystem format bump
   <a class="sectionlink" href="#fsfs-format8"
@@ -664,15 +646,6 @@ format number of a repository.)</p>
 <p>Existing repositories can be upgraded to the new format with the
 <tt>svnadmin upgrade</tt> command.
 
-<div class="notice">
-  <p><span style="color: red"><b>WARNING:</b></span> Until Subversion 1.10
-  is generally available, no upgrade path is promised for repositories with
-  the filesystem format 8.  Please do not upgrade your existing repositories
-  used in production, and do not use newly created repositories for any data
-  meant for long-term safe-keeping.  See our <a href="/prerelease-caveats">policy
-  for pre-releases</a> for additional information.</p>
-</div>
-
 </div>  <!-- fsfs-format8 -->
 
 <div class="h4" id="fsfs-lz4-configuration">
@@ -711,14 +684,14 @@ cycle into a new format 8 repository created with Subversion 1.10.
 compressed with LZ4.  The actual choice of the compression algorithm depends
 on the used protocol, environment and its configuration &mdash; see below.</p>
 
-<p>For <b>http://</b> protocol, use of LZ4 compression depends on the values
+<p>For the <b>http://</b> protocol, use of LZ4 compression depends on the values
 of the server-side <tt>SVNCompressionLevel</tt> directive, client-side
 <tt>http-compression</tt> configuration option and on the network
 capabilities.  LZ4 compression generally offers much faster compression
 and decompression speeds, but slightly worse compression ratio than zlib.
 By default, it is only preferred for low latency networks where the
 overhead associated with transferring the additional amount of data is
-assumed to be negligible.<p>
+assumed to be negligible.</p>
 
 <ul>
   <li>
@@ -751,73 +724,77 @@ combination of the client- and server-side configuration options:</p>
     <th colspan="2">1.9 and older Server<br />with SVNCompressionLevel:</th>
   </tr>
   <tr>
-    <th>Subversion Client</th>
-    <th>0</th>
-    <th>1</th>
-    <th>2-9 (default:&nbsp;5)<sup>*</sup></th>
-    <th>0</th>
-    <th>1-9 (default:&nbsp;5)<sup>*</sup></th>
+    <th width="30%">Subversion Client</th>
+    <th width="10%">0</th>
+    <th width="10%">1</th>
+    <th width="10%">2-9 (default:&nbsp;5)<sup>*</sup></th>
+    <th width="10%">0</th>
+    <th width="10%">1-9 (default:&nbsp;5)<sup>*</sup></th>
   </tr>
   <tr>
     <td>1.10, <tt>http-compression: auto</tt><sup>*</sup>, low latency</td>
-    <td>No compression</td>
-    <td><b>LZ4</b> compression</td>
-    <td><b>LZ4</b> compression</td>
-    <td>No compression</td>
-    <td>zlib compression</td>
+    <td>None</td>
+    <td><b>LZ4</b></td>
+    <td><b>LZ4</b></td>
+    <td>None</td>
+    <td>zlib</td>
   </tr>
   <tr>
     <td>1.10, <tt>http-compression: auto</tt><sup>*</sup>, high latency</td>
-    <td>No compression</td>
-    <td><b>LZ4</b> compression</td>
-    <td>zlib compression</td>
-    <td>No compression</td>
-    <td>zlib compression</td>
+    <td>None</td>
+    <td><b>LZ4</b></td>
+    <td>zlib</td>
+    <td>None</td>
+    <td>zlib</td>
   </tr>
   <tr>
     <td>1.10, <tt>http-compression: yes</tt></td>
-    <td>No compression</td>
-    <td><b>LZ4</b> compression</td>
-    <td>zlib compression</td>
-    <td>No compression</td>
-    <td>zlib compression</td>
+    <td>None</td>
+    <td><b>LZ4</b></td>
+    <td>zlib</td>
+    <td>None</td>
+    <td>zlib</td>
   </tr>
   <tr>
     <td>1.10, <tt>http-compression: no</tt></td>
-    <td>No compression</td>
-    <td>No compression</td>
-    <td>No compression</td>
-    <td>No compression</td>
-    <td>No compression</td>
+    <td>None</td>
+    <td>None</td>
+    <td>None</td>
+    <td>None</td>
+    <td>None</td>
   </tr>
   <tr>
     <td>1.9 and older, <tt>http-compression: yes</tt><sup>*</sup></td>
-    <td>No compression</td>
-    <td>zlib compression</td>
-    <td>zlib compression</td>
-    <td>No compression</td>
-    <td>zlib compression</td>
+    <td>None</td>
+    <td>zlib</td>
+    <td>zlib</td>
+    <td>None</td>
+    <td>zlib</td>
   </tr>
   <tr>
     <td>1.9 and older, <tt>http-compression: no</tt></td>
-    <td>No compression</td>
-    <td>No compression</td>
-    <td>No compression</td>
-    <td>No compression</td>
-    <td>No compression</td>
+    <td>None</td>
+    <td>None</td>
+    <td>None</td>
+    <td>None</td>
+    <td>None</td>
   </tr>
 </table>
 
 <p><sup>*</sup>&nbsp;Default configurations</p>
 
-<!-- TODO: describe LZ4 over svn:// -->
+<p>For the <b>svn://</b> protocol, use of LZ4 compression depends on the value
+of the server-side <tt>-c/--compression</tt> option.  A value of <tt>0</tt>
+disables compression entirely; any other value causes lz4 or zlib compression
+to be used.  At this time, lz4 is always used in preference to zlib when both
+are supported by the remote end<!-- see svn_ra_svn__svndiff_version() -->.</p>
 
 </div>  <!-- lz4-over-the-wire -->
 
 </div>  <!-- lz4 -->
 
 <div class="h3" id="shelving">
-<h3>Shelving
+<h3>Shelving (experimental)
   <a class="sectionlink" href="#shelving"
      title="Link to this section">&para;</a>
 </h3>
@@ -883,7 +860,7 @@ which happen to contain upper-case and non-English characters.</tt>
 
 <p>You may now specify one or more glob patterns in a <tt>svn ls</tt>
 request.  Note that most shells require globs to be put in quotation
-marks to be passed as-is to SVN.  Example
+marks to be passed as-is to SVN.  Example:
    <pre>
    svn ls svn://server/repo --recursive --search "readme*"</pre>
 Against a Subversion 1.10 server, this command will be executed
@@ -1017,7 +994,7 @@ wildcards (the same as in 'svndumpfilter').</p>
 </div> <!-- server-side-improvements -->
 
 <div class="h3" id="client-server-improvements">
-<h3>Client-server improvements
+<h3>Client- and server-side improvements
   <a class="sectionlink" href="#client-server-improvements"
      title="Link to this section">&para;</a>
 </h3>