You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ju...@apache.org on 2019/09/30 18:59:37 UTC

svn commit: r1867795 - /subversion/site/publish/docs/release-notes/1.13.html

Author: julianfoad
Date: Mon Sep 30 18:59:37 2019
New Revision: 1867795

URL: http://svn.apache.org/viewvc?rev=1867795&view=rev
Log:
* publish/docs/release-notes/1.13.html: Replace with a template.

Generated by: 'release.py write-release-notes'

Modified:
    subversion/site/publish/docs/release-notes/1.13.html

Modified: subversion/site/publish/docs/release-notes/1.13.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.13.html?rev=1867795&r1=1867794&r2=1867795&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.13.html (original)
+++ subversion/site/publish/docs/release-notes/1.13.html Mon Sep 30 18:59:37 2019
@@ -21,41 +21,231 @@
 <!-- or TODOs.  Remove them before release.           -->
 <!-- ************************************************ -->
 
-<p>Temporary release notes, from
-   <a href="http://svn.apache.org/repos/asf/subversion/branches/1.13.x/CHANGES">
-   1.13.x/CHANGES</a>:</p>
-
-<pre>
- User-visible changes:
-  - Minor new features and improvements:
-    * New 'svnadmin rev-size' command to report revision size (r1857624)
-    * In 'svn help', hide experimental commands and global options (issue #4828)
-    * Add a hint about mod_dav_svn misconfiguration (r1866738)
-    * Performance improvement for 'svn st' etc., in WC SQLite DB (r1865523)
-
-  - Client-side bugfixes:
-    * Windows: avoid delays in SSL certificate validation override (r1863018)
-    * Fix 'svn patch' setting mode 0600 on patched files with props (r1864440)
-    * Fix "svn diff --changelist ARG" broken in subdirectories (issue #4822)
-    * Fix misleading 'redirect cycle' error on a non-repository URL (r1866899)
-
-  - Server-side bugfixes:
-    * svnserve: Report some errors that we previously ignored (r1866062)
-    * Make server code more resilient to malformed paths and URLs (r1866318 et al)
-    * Make dump stream parser more resilient to malformed dump stream (r1866951)
-    * mod_dav_svn: Fix missing Last-Modified header on 'external' GET requests (r1866425)
-
-  - Client-side and server-side bugfixes:
-    * Fix excessive memory usage in some cases reading binary data (r1866950)
-    * Win32: fix svn_io_file_rename2() spinning in a retry loop (r1865518)
+<h1 style="text-align: center">Apache Subversion 1.13 Release Notes</h1>
 
-  - Other tool improvements and bugfixes:
-    * svn_load_dirs.pl: do not show password; fix cleanup (r1863262, r1863392)
+<div class="h2" id="news">
+<h2>What's New in Apache Subversion 1.13
+  <a class="sectionlink" href="#news"
+    title="Link to this section">&para;</a>
+</h2>
+
+<ul>
+  <!-- The main changes...
+  <li><a href="#"
+      >###</a></li>
+  -->
+  <li><a href="#enhancements"
+      >Many enhancements and bug fixes</a></li>
+  <li><a href="#issues"
+      >Known issues in the release</a></li>
+  <!--
+  <li><a href="#troubleshooting"
+      >Troubleshooting issues specific to this release</a></li>
+  -->
+</ul>
+
+<p>Apache Subversion 1.13 is a superset of all previous Subversion
+releases, and is as of the time of its release considered the current
+"best" release.  Any feature or bugfix in 1.0.x through 1.12.x is also
+in 1.13, but 1.13 contains features and bugfixes not present in any
+earlier release.  The new features will eventually be documented in a
+1.13 version of the free Subversion book
+(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+
+<p>This page describes only major changes.  For a complete list of
+changes, see the 1.13 section of the <a
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES" >CHANGES</a>
+file.</p>
+
+</div>  <!-- news -->
+
+<div class="h2" id="compatibility">
+<h2>Compatibility Concerns
+  <a class="sectionlink" href="#compatibility"
+    title="Link to this section">&para;</a>
+</h2>
+
+<p>Older clients and servers interoperate transparently with 1.13
+servers and clients.  However, some of the new 1.13 features may not be
+available unless both client and server are the latest version.  There are
+also cases where a new feature will work but will run less efficiently if
+the client is new and the server old.</p>
+
+<p>There is <strong>no need</strong> to <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+>dump and reload</a> your repositories. 
+Subversion 1.13 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>Subversion 1.13 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
+and run using 1.13 libraries.  However, a program written for 1.13
+cannot necessarily compile or run against older libraries.</p>
+
+<p>There may be limited cases where the behavior of old APIs has been
+slightly modified from previous releases.  These are cases where edge cases
+of the functionality has been deemed buggy, and therefore improved or removed.
+Please consult the
+<a href="https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.13/"
+>API errata</a> for more detailed information on what these APIs are
+and what impact these changes may have.</p>
+
+<div class="h3" id="new-feature-compatibility-table">
+<h3>New Feature Compatibility Table
+  <a class="sectionlink" href="#new-feature-compatibility-table"
+    title="Link to this section">&para;</a>
+</h3>
+<table border="1">
+  <tr>
+    <th>New Feature</th>
+    <th>Minimum Client<sup>1</sup></th>
+    <th>Minimum Server</th>
+    <th>Minimum Repository</th>
+    <th>Notes</th></tr>
+</table>
+
+</div>  <!-- new-feature-compatibility-table -->
+
+<div class="h3" id="wc-upgrade">
+<h3>Upgrading the Working Copy
+  <a class="sectionlink" href="#wc-upgrade"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>Subversion 1.13 uses the same working copy format as Subversion 1.8 through 1.12.</p>
+
+<p>Before using Subversion 1.13 with an existing Subversion 1.7 or older
+working copy, users will be required to run the <tt>svn upgrade</tt> command
+to upgrade working copy metadata to the new format. This command may take a
+while in some cases, and for some users, it may be more practical to simply
+checkout a new working copy.</p>
+
+<p><strong>Note:</strong> Subversion 1.13 cannot upgrade working copies that
+a 1.6 client would have refused to operate upon before an <tt>svn cleanup</tt>
+was run (with a 1.6 client).  In other words, before upgrading to 1.8 or newer,
+a 1.6
+or older client must be used to run <tt>svn cleanup</tt> on all 1.6 or older
+working copies that require cleanup.  Likewise, Subversion 1.13 cannot upgrade
+corrupt working copies. Unfixable problems can arise from missing or corrupt
+meta-data inside <tt>.svn</tt> directories.  Such damage to the working copy
+is permanent, and cannot be fixed even if <tt>svn cleanup</tt> is run prior
+to the upgrade.</p>
+
+<p>If your working copy does not upgrade cleanly, please check out a new one.
+</p>
+
+</div>  <!-- wc-upgrade -->
+
+<!-- (This section only makes sense when there are some issues listed in it.)
+<div class="h3" id="compat-misc">
+<h3>Miscellaneous Compatibility Notes
+  <a class="sectionlink" href="#compat-misc"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>There are some additional specific areas where changes made in this
+release might necessitate further adjustment by administrators or
+users.  We'll cover those in this section.</p>
+
+</div>  < !-- compat-misc -- >
+-->
+
+</div>  <!-- compatibility -->
+
+<div class="h2" id="new-features">
+<h2>New Features
+  <a class="sectionlink" href="#new-features"
+    title="Link to this section">&para;</a>
+</h2>
+
+</div>  <!-- new-features -->
+
+<div class="h2" id="enhancements">
+<h2>Enhancements and Bugfixes
+  <a class="sectionlink" href="#enhancements"
+    title="Link to this section">&para;</a>
+</h2>
+
+<!-- Don't need to highlight every bugfix, just major ones which aren't in
+     any patch release. -->
+
+<div class="h3" id="cmdline">
+<h3>Command-line client improvements (<em>client</em>)
+  <a class="sectionlink" href="#cmdline"
+    title="Link to this section">&para;</a>
+</h3>
+
+</div> <!-- cmdline -->
+
+<div class="h3" id="server-side-improvements">
+<h3>Server-side improvements
+  <a class="sectionlink" href="#server-side-improvements"
+     title="Link to this section">&para;</a>
+</h3>
+
+</div> <!-- server-side-improvements -->
+
+<div class="h3" id="client-server-improvements">
+<h3>Client- and server-side improvements
+  <a class="sectionlink" href="#client-server-improvements"
+     title="Link to this section">&para;</a>
+</h3>
+
+</div> <!-- client-server-improvements -->
+
+</div>  <!-- enhancements -->
+
+<div class="h2" id="issues">
+<h2>Known issues in the release
+  <a class="sectionlink" href="#issues"
+    title="Link to this section">&para;</a>
+</h2>
+
+<p>There are no known issues specific to this release at the moment.</p>
+
+<!--
+<p>There are some known issues in the Subversion 1.13 releases.  These
+may be fixed in later 1.13.x releases.</p>
+-->
+
+</div>  <!-- issues -->
+
+<!-- (This section only makes sense when there are some issues listed in it.)
+<div class="h2" id="troubleshooting">
+<h2>Troubleshooting issues specific to this release
+  <a class="sectionlink" href="#troubleshooting"
+    title="Link to this section">&para;</a>
+</h2>
+
+<p>Subversion 1.13 introduces new features and makes use of new techniques
+which can trigger problems not encountered in previous versions. In contrast to
+known issues, things listed here are not due to some bug or issue in Subversion
+itself and therefore cannot be fixed with a new patch release.
+This section lists all known problems and provides instructions to solve them,
+if they occur.</p>
+
+<p>There are no known issues specific to this release at the moment.</p>
+
+</div>  < !-- troubleshooting -- >
+-->
+
+<div class="h2" id="non-lts-release">
+<h2>Subversion 1.13.x is a Regular Release
+  <a class="sectionlink" href="#non-lts-release"
+    title="Link to this section">&para;</a>
+</h2>
+
+<p>1.13 is a regular release, not a Long-Term Support release.
+   This release does not change the status of existing LTS releases
+   (1.9 and 1.10).
+   See <a href="/roadmap.html#release-planning">How We Plan Releases</a>.</p>
+
+<p>Therefore, if you are running into an issue with the old stable
+version which has already been fixed in the latest version, we might
+ask you to upgrade to that version to resolve the issue.</p>
 
- Developer-visible changes:
-    * New svn_fs_ioctl() API for FSFS stats, dump/load index, rev-size (r1857435)
-
-</pre>
+</div>  <!-- non-lts-release -->
 
 <!-- ***************** END CONTENT ****************** -->
 </div> <!-- #site-content -->