subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cmpil...@apache.org
Subject svn commit: r1879655 - in /subversion/site/staging: ./ docs/community-guide/ docs/release-notes/
Date Wed, 08 Jul 2020 13:35:00 GMT
Author: cmpilato
Date: Wed Jul  8 13:34:59 2020
New Revision: 1879655

URL: http://svn.apache.org/viewvc?rev=1879655&view=rev
Log:
In 'staging': catch-up merge from 'publish'

Modified:
    subversion/site/staging/   (props changed)
    subversion/site/staging/.message-ids.tsv
    subversion/site/staging/doap.rdf
    subversion/site/staging/docs/community-guide/general.part.html
    subversion/site/staging/docs/community-guide/releasing.part.html
    subversion/site/staging/docs/community-guide/roles.part.html
    subversion/site/staging/docs/release-notes/1.10.html
    subversion/site/staging/docs/release-notes/1.11.html
    subversion/site/staging/docs/release-notes/1.12.html
    subversion/site/staging/docs/release-notes/1.13.html
    subversion/site/staging/docs/release-notes/1.14.html
    subversion/site/staging/docs/release-notes/index.html
    subversion/site/staging/docs/release-notes/release-history.html
    subversion/site/staging/download.html
    subversion/site/staging/faq.html
    subversion/site/staging/index.html   (contents, props changed)
    subversion/site/staging/news.html   (contents, props changed)
    subversion/site/staging/roadmap.html   (props changed)
    subversion/site/staging/upcoming.part.html

Propchange: subversion/site/staging/
------------------------------------------------------------------------------
  Merged /subversion/site/publish:r1872629-1879654

Modified: subversion/site/staging/.message-ids.tsv
URL: http://svn.apache.org/viewvc/subversion/site/staging/.message-ids.tsv?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/.message-ids.tsv (original)
+++ subversion/site/staging/.message-ids.tsv Wed Jul  8 13:34:59 2020
@@ -1,5 +1,5 @@
 # Message-ids of archived emails that are referenced by a svn.haxx.se URL.
-# Generated by tools/haxx-url-to-message-id.sh on 2019-09-19
+# Generated by tools/haxx-url-to-message-id.sh on 2020-05-28
 https://svn.haxx.se/dev/archive-2003-01/1125.shtml	20030116213052.314004c1.ttimo@idsoftware.com
 https://svn.haxx.se/dev/archive-2003-02/0068.shtml	87wuki4fpy.fsf@codematters.co.uk
 https://svn.haxx.se/dev/archive-2003-10/0136.shtml	200310031235.h93CZgIV064765@bigtex.jrv.org
@@ -44,10 +44,12 @@ https://svn.haxx.se/dev/archive-2017-07/
 https://svn.haxx.se/dev/archive-2019-03/0012.shtml	FBBD2C2C-0287-4486-9177-E532BA45FDF6@ikoder.com
 https://svn.haxx.se/dev/archive-2019-04/0020.shtml	0ca0045a-7f19-b22b-b184-535275371ffe@apache.org
 https://svn.haxx.se/dev/archive-2019-07/0072.shtml	CALq3gdNT2z3eh8DffprebV+XzifAR8CqbgGgs7id1NA4Ui=zYg@mail.gmail.com
+https://svn.haxx.se/dev/archive-2020-05/0151.shtml	20200527155606.GC45157@ted.stsp.name
 https://svn.haxx.se/users/archive-2004-03/0488.shtml	1078601435.31293.104.camel@Madison.badger.com
 https://svn.haxx.se/users/archive-2004-07/1662.shtml	003c01c4763b$180511f0$800000c0@blazepoint.local
 https://svn.haxx.se/users/archive-2010-01/0001.shtml	69B68910-B4D0-428E-A4BB-FB7D6E87B24F@barrys-emacs.org
 https://svn.haxx.se/users/archive-2012-03/0147.shtml	20120308190221.GA4925@jack.stsp.name
 https://svn.haxx.se/users/archive-2012-09/0236.shtml	20120921085850.GG24524@ted.stsp.name
 https://svn.haxx.se/users/archive-2019-04/0041.shtml	9739e241-f88c-8a79-11f5-783a7f119ce2@neuf.fr
+https://svn.haxx.se/users/archive-2020-04/0040.shtml	20200422065424.GL81597@ted.stsp.name
 http://svn.haxx.se/dev/archive-2010-08/0362.shtml	4C65756C.8070104@collab.net

Modified: subversion/site/staging/doap.rdf
URL: http://svn.apache.org/viewvc/subversion/site/staging/doap.rdf?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/doap.rdf (original)
+++ subversion/site/staging/doap.rdf Wed Jul  8 13:34:59 2020
@@ -36,9 +36,9 @@
     <category rdf:resource="http://projects.apache.org/category/build-management" />
     <release>
       <Version>
-        <name>Current 1.13 regular release</name>
-        <created>2019-10-30</created>
-        <revision>1.13.0</revision>
+        <name>Current 1.14 LTS release</name>
+        <created>2020-05-27</created>
+        <revision>1.14.0</revision>
       </Version>
     </release>
     <release>
@@ -48,13 +48,6 @@
         <revision>1.10.6</revision>
       </Version>
     </release>
-    <release>
-      <Version>
-        <name>Current 1.9 release</name>
-        <created>2019-07-24</created>
-        <revision>1.9.12</revision>
-      </Version>
-    </release>
     <repository>
       <SVNRepository>
         <location rdf:resource="http://svn.apache.org/repos/asf/subversion/trunk"/>

Modified: subversion/site/staging/docs/community-guide/general.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/general.part.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/general.part.html (original)
+++ subversion/site/staging/docs/community-guide/general.part.html Wed Jul  8 13:34:59 2020
@@ -71,8 +71,8 @@ to contribute, then look at:</p>
 
 <ul>
 <li><p>The bugs/issues database
-       <a href="http://subversion.tigris.org/issue-tracker.html"
-               >http://subversion.tigris.org/issue-tracker.html</a></p></li>
+       <a href="https://issues.apache.org/jira/projects/SVN/issues"
+               >https://issues.apache.org/jira/projects/SVN/issues</a></p></li>
 </ul>
 
 <p>To submit code, simply send your patches to

Modified: subversion/site/staging/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Wed Jul  8 13:34:59 2020
@@ -156,7 +156,7 @@ alpha or beta release is announced.</p>
 
 <p>When the alpha or beta is publicly announced, distribution packagers
 should be firmly warned off packaging it.  See <a
-href="http://subversion.tigris.org/servlets/ReadMsg?list=announce&amp;msgNo=264"
+href="https://mail-archives.apache.org/mod_mbox/subversion-announce/201106.mbox/%3CBANLkTi%3DhFhXwpyGKp7XOsL4j39tssD363A%40mail.gmail.com%3E"
 >this mail from Hyrum K. Wright</a> for a good model.</p>
 
 </div> <!-- alphas-betas -->
@@ -817,6 +817,12 @@ time pass.</p>
     title="Link to this section">&para;</a>
 </h3>
 
+<div class="h4" id="before-release-pristine-tools">
+<h4>Install pristine versions of some build tools
+  <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#before-release-pristine-tools"
+    title="Link to this section">&para;</a>
+</h4>
+
 <p>So, a release branch has stabilized, and you are gearing up to roll
 the release. The details of the rolling process are automated by the
 <a href="https://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py">release.py</a>
@@ -834,7 +840,7 @@ of this software as they are often patch
 portable.  The version numbers given above should normally be
 reconsidered and increased to the latest stable upstream release in
 the time leading up to an A.B.0 release.  Changing the version within
-an A.B.x series should only be done with careful considereration.</p>
+an A.B.x series should only be done with careful consideration.</p>
 
 <p><b>Autoconf, Libtool and SWIG</b>: Pick a directory to contain your
 special build tools for Subversion RM duties - for example
@@ -845,6 +851,28 @@ software with the <tt>release.py build-e
 mkdir -p /opt/svnrm &amp;&amp; cd /opt/svnrm &amp;&amp; $SVN_SRC_DIR/tools/dist/release.py build-env X.Y.Z
 </pre>
 
+</div> <!-- before-release-pristine-tools -->
+
+<div class="h4" id="before-release-dependencies">
+<h4>Install pristine versions of some build tools
+  <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#before-release-dependencies"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>The rolling scripts also require the following commands to be available:
+<tt>pax</tt>,
+<tt>xgettext</tt>,
+<tt>m4</tt>,
+and 
+<tt>python -c 'import yaml'</tt>.</p>
+
+<p>Install these from your OS packages.
+(On Debian systems, that'd be
+<tt>apt install pax gettext m4 python-yaml subversion</tt>.)</p>
+<!-- Feel free to add here the equivalent incantations for other platforms. -->
+
+</div> <!-- before-release-dependencies -->
+
 </div> <!-- before-release -->
 
 <div class="h3" id="rolling-release">
@@ -1094,7 +1122,7 @@ upload the signatures to the preliminary
 in the same directory as the tarballs.</p>
 
 <p>
-Members of the PMC, as well as enthusiastic community members are encourages to
+Members of the PMC, as well as enthusiastic community members are encouraged to
 download the tarballs from the preliminary distribution location, run the
 tests, and then provide their signatures.  The public keys for these signatures
 should be included in the ASF LDAP instance through
@@ -1263,16 +1291,37 @@ release, be sure to update the <tt>recom
 before using it to generate the announcement.</p>
 
 <p>Send the announcement from your @apache.org email address.
-(Mail to announce@ will bounce if sent from any other address.)
+(Mail to announce@ will bounce if sent from any other address.
+For best results, follow the instructions on the
+<a href="https://infra.apache.org/committer-email.html">committer email</a>
+page and send your message through the official mail relay.)
 Ensure that your mailer doesn't wrap the URLs over multiple lines.</p>
 
 <p>NOTE: We announce the release before updating the website since the website
 update links to the release announcement sent to the announce@ mailing list.</p>
 
+<p>There are two announce@ mailing lists where the release announcement gets
+posted: The Subversion project's announce@subversion.apache.org list, and the ASF-wide announce@apache.org
+list. It is possible that your message to the ASF-wide announce@ list will be
+rejected. This generates a moderation notification with a Subject line such as:
+<tt>Returned post for announce@apache.org</tt>. The moderator who ordered the
+mailing list software to reject the message may neglect to sign their name to
+the rejection message, making the rejection anonymous, and the grounds for the
+rejection may be invalid. Be that as it may, keep calm and forward the
+rejection to the dev@ mailing list so the project can discuss whether anything
+needs to be done about it. (If necessary, announce@ mailing list moderators can
+be contacted via the announce-owner@ handle.)</p>
+
 <p>Update the topics in various Subversion-related IRC channels, such as
 <tt>#svn</tt> and <tt>#svn-dev</tt> on freenode.</p>
 
-</div> <!-- release-announce -->
+<p>If this is an X.Y.0 release, update the community support level at the very
+top of the <tt>STATUS</tt> files of any branches that have changed support
+status.  This would usually be <tt>X.Y.x/STATUS</tt>,
+<tt>X.$((Y-1)).x/STATUS</tt>, and if the new release is an LTS release, then
+the oldest supported LTS branch's <tt>STATUS</tt> file as well.</p>
+
+</div> <!-- releasing-announce -->
 
 <div class="h4" id="releasing-update-website">
 <h4>Update the website
@@ -1432,23 +1481,31 @@ developed.</p>
 </h3>
 
 <p>Once people agree that a new release branch should be made, the
-Release Manager creates it with the following procedure (substitute
+Release Manager creates it with one of the following procedures (substitute
 A.B with the version you're preparing, eg. 1.3, or 2.0).</p>
 
-<h4>Automated</h4>
+<h4>Automated Procedure with release.py</h4>
+<p>Most of the work to create a release branch can be automated by
+tools/dist/release.py:</p>
 <p>Run this in an empty-ish directory where it will make some temporary checkouts:</p>
 <pre>
 release.py --verbose create-release-branch A.B.0
 </pre>
-<p>Write a release notes template:</p>
+<p>If not done previously, create the release notes template for the project
+website:</p>
 <pre>
 release.py --verbose write-release-notes A.B.0 &gt; .../docs/release-notes/A.B.html
 svn add .../docs/release-notes/A.B.html
 svn ci -m "Add release notes template." .../docs/release-notes/A.B.html
 </pre>
-<div class="notice">Some steps are not automated&mdash;highlighted below.</div>
-
-<h4>Manual Steps</h4>
+<div class="notice">Some steps are not automated by release.py and must be
+done manually&mdash;skip to the end of the following section, where they are
+highlighted:</div>
+
+<h4>Manual Procedure</h4>
+<p>Most of the steps in this section can be automated by
+tools/dist/release.py&mdash;see above&mdash;but are documented here in case
+the Release Manager wants to do them manually:</p>
 <ul>
 <li><p>Create the new release branch with a server-side copy:</p>
     <pre>
@@ -1510,7 +1567,8 @@ svn ci -m "Add release notes template."
        <tt>site/publish/docs/release-notes/A.B.html</tt></p></li>
 </ul>
 
-<div class="notice">The following steps are not automated:</div>
+<div class="notice">The following steps must be done manually, even when
+using release.py to automate most of the other steps:</div>
 <ul>
 <li>
     <p>Ask someone with appropriate access to add the A.B.x branch to the

Modified: subversion/site/staging/docs/community-guide/roles.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/roles.part.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/roles.part.html (original)
+++ subversion/site/staging/docs/community-guide/roles.part.html Wed Jul  8 13:34:59 2020
@@ -114,8 +114,8 @@ href="<!--#echo var="GUIDE_GENERAL_PAGE"
 >section on lightweight branches</a>, and this mail:</p>
 
 <pre>
-   <a href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=132746"
->http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=132746</a>
+   <a href="https://svn.haxx.se/dev/archive-2007-11/0848.shtml"
+>https://svn.haxx.se/dev/archive-2007-11/0848.shtml</a>
    From: Karl Fogel &lt;kfogel@red-bean.com&gt;
    To: dev@subversion.tigris.org
    Subject: branch liberalization (was: Elego tree conflicts work)

Modified: subversion/site/staging/docs/release-notes/1.10.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.10.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.10.html (original)
+++ subversion/site/staging/docs/release-notes/1.10.html Wed Jul  8 13:34:59 2020
@@ -854,7 +854,7 @@ patch</tt>.</p>
 
 <p><tt>svn log --search</tt> is now case-insensitive and ignores diacriticals
 when matching words. This makes it easier to match paths and log messages
-which happen to contain upper-case and non-English characters.</tt>
+which happen to contain upper-case and non-English characters.</p>
 
 </div> <!-- log-search -->
 

Modified: subversion/site/staging/docs/release-notes/1.11.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.11.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.11.html (original)
+++ subversion/site/staging/docs/release-notes/1.11.html Wed Jul  8 13:34:59 2020
@@ -139,6 +139,10 @@ and what impact these changes may have.<
     <td>any</td>
     <td>any</td>
     <td></td></tr>
+  <tr>
+    <td colspan="5"><sup>1</sup>Reminder: when using the <tt>file://</tt>
+    repository access method, the Subversion program is both the client
+    <em>and</em> the server.</td></tr>
 </table>
 
 </div>  <!-- new-feature-compatibility-table -->

Modified: subversion/site/staging/docs/release-notes/1.12.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.12.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.12.html (original)
+++ subversion/site/staging/docs/release-notes/1.12.html Wed Jul  8 13:34:59 2020
@@ -128,6 +128,10 @@ and what impact these changes may have.<
     <td>any</td>
     <td>any</td>
     <td></td></tr>
+  <tr>
+    <td colspan="5"><sup>1</sup>Reminder: when using the <tt>file://</tt>
+    repository access method, the Subversion program is both the client
+    <em>and</em> the server.</td></tr>
 </table>
 
 </div>  <!-- new-feature-compatibility-table -->
@@ -375,10 +379,11 @@ have always been stored in an encrypted
 <p>Behaviour of copy operations with a repository source and a working copy
 target has been improved:</p>
 <ul>
-<li>Existing parent directories are now handled correctly.
+<li>Existing parent directories are now handled correctly.</li>
 <li>Peg and operative revisions are now handled correctly (see
 <a href="https://issues.apache.org/jira/browse/SVN-4785">issue #4785</a>
-for details).
+for details).</li>
+</ul>
 </div> <!-- repos-wc-copy -->
 
 <div class="h4" id="svn-list">

Modified: subversion/site/staging/docs/release-notes/1.13.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.13.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.13.html (original)
+++ subversion/site/staging/docs/release-notes/1.13.html Wed Jul  8 13:34:59 2020
@@ -109,6 +109,10 @@ and what impact these changes may have.<
     <td>1.13</td>
     <td>any FSFS repo</td>
     <td></td></tr>
+  <tr>
+    <td colspan="5"><sup>1</sup>Reminder: when using the <tt>file://</tt>
+    repository access method, the Subversion program is both the client
+    <em>and</em> the server.</td></tr>
 </table>
 
 </div>  <!-- new-feature-compatibility-table -->

Modified: subversion/site/staging/docs/release-notes/1.14.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.14.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.14.html (original)
+++ subversion/site/staging/docs/release-notes/1.14.html Wed Jul  8 13:34:59 2020
@@ -23,15 +23,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
@@ -66,6 +58,10 @@ releases, and is as of the time of its r
 in 1.14, but 1.14 contains features and bugfixes not present in any
 earlier release.</p>
 
+<p>Because 1.14 is the next LTS release following 1.10, these release
+notes describe major changes since 1.10, including changes released in
+1.11.x through 1.13.x.</p>
+
 <p>This page describes only major changes.  For a complete list of
 changes, see the 1.14 section of the <a
 href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES" >CHANGES</a>
@@ -117,6 +113,47 @@ and what impact these changes may have.<
     <th>Minimum Server</th>
     <th>Minimum Repository</th>
     <th>Notes</th></tr>
+  <tr>
+    <td><a href="#svnadmin-rev-size"><tt>svnadmin rev-size</tt></a></td>
+    <td>n/a</td>
+    <td>1.13</td>
+    <td>any FSFS repo</td>
+    <td></td></tr>
+  <tr>
+    <td><a href="#svnadmin-build-repcache"><tt>svnadmin build-repcache</tt></a></td>
+    <td>n/a</td>
+    <td>1.14</td>
+    <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>
+    </td>
+    <td>1.12</td>
+    <td>any</td>
+    <td>any</td>
+    <td>shelves created by 1.10 are not compatible&mdash;see
+        <a href="#shelving-transition">Upgrading 1.10&ndash;1.13 shelves to 1.14</a></td></tr>
+  <tr>
+    <td>
+      <a href="#shelving-checkpointing">Commit checkpointing (experimental)</a>
+    </td>
+    <td>1.12</td>
+    <td>any</td>
+    <td>any</td>
+    <td></td></tr>
+  <tr>
+    <td>
+      <a href="#viewspec-output">Viewspec output command (experimental)</a>
+    </td>
+    <td>1.11</td>
+    <td>any</td>
+    <td>any</td>
+    <td></td></tr>
+  <tr>
+    <td colspan="5"><sup>1</sup>Reminder: when using the <tt>file://</tt>
+    repository access method, the Subversion program is both the client
+    <em>and</em> the server.</td></tr>
 </table>
 
 </div>  <!-- new-feature-compatibility-table -->
@@ -151,6 +188,26 @@ to the upgrade.</p>
 
 </div>  <!-- wc-upgrade -->
 
+<div class="h3 experimental-feature" id="compatibility-shelving">
+<h3>Changes to Experimental Shelving Feature
+  <a class="sectionlink" href="#compatibility-shelving"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>Since 1.10, Subversion provides an experimental "Shelving" feature aimed
+at addressing <a href="https://issues.apache.org/jira/browse/SVN-3625">issue
+#3625</a>. There is no promise of backward compatibility for features
+designated "experimental."</p>
+
+<p>Shelving in 1.14 has changed significantly since 1.10 and is incompatible
+with shelves created by 1.10. See <a href="#shelving">Shelving and
+Checkpointing (experimental)</a> for the major changes and differences in
+commands. See its subsection, <a href="#shelving-transition">Upgrading
+1.10&ndash;1.13 shelves to 1.14</a> to learn how to recover 1.10 shelves in
+an existing working copy.</p>
+
+</div>  <!-- compatibility-shelving -->
+
 <!-- (This section only makes sense when there are some issues listed in it.)
 <div class="h3" id="compat-misc">
 <h3>Miscellaneous Compatibility Notes
@@ -173,6 +230,76 @@ users.  We'll cover those in this sectio
     title="Link to this section">&para;</a>
 </h2>
 
+<div class="h3" id="svnadmin-rev-size">
+<h3>New <tt>svnadmin rev-size</tt> command
+  <a class="sectionlink" href="#svnadmin-rev-size"
+     title="Link to this section">&para;</a>
+</h3>
+
+<p>This change was first introduced in 1.13.</p>
+
+<p>Add an <tt>svnadmin rev-size</tt> command to report the total size in
+bytes of the representation on disk of a revision, including rev-props,
+but excluding FSFS indexes. For example:</p>
+
+<pre>
+    $ svnadmin rev-size /path/to/repo -r1
+            1337 bytes in revision 1
+</pre>
+
+<p>(See <a href="http://svn.apache.org/r1857624">r1857624</a>.)</p>
+</div> <!-- svnadmin-rev-size -->
+
+<div class="h3" id="svnadmin-build-repcache">
+<h3>New <tt>svnadmin build-repcache</tt> command
+  <a class="sectionlink" href="#svnadmin-build-repcache"
+     title="Link to this section">&para;</a>
+</h3>
+
+<p>Representation Sharing (also called rep-sharing) is a data storage
+de-duplication feature first introduced in Subversion 1.6. It reduces the disk
+size of a repository by storing duplicate data only once. (See <a
+href="https://issues.apache.org/jira/browse/SVN-2286">issue #2286</a>.)</p>
+
+<p>This optional feature is enabled by default. It relies on a rep-cache
+database, which Subversion automatically maintains with the repository, to
+identify duplicate pieces of data.</p>
+
+<p>Over time, some administrators have disabled and/or re-enabled rep-sharing,
+which has the effect of excluding from the rep-cache any revisions that were
+committed while the feature was disabled.</p>
+
+<p>Subversion 1.14 introduces a new <tt>svnadmin build-repcache</tt>
+subcommand, which administrators can use to populate any missing entries in
+the rep-cache database for a specified revision range (or all revisions). (See
+<a href="http://svn.apache.org/r1875921">r1875921</a>.)</p>
+
+<p>For example, to process revisions 20 through 25, inclusive, and ensure that
+their data is known to the rep-cache:</p>
+
+<pre>
+    $ svnadmin build-repcache /path/to/repo -r20:25
+    * Processed revision 20.
+    * Processed revision 21.
+    * Processed revision 22.
+    * Processed revision 23.
+    * Processed revision 24.
+    * Processed revision 25.
+</pre>
+
+<p>If only one revision argument is given, <tt>svnadmin build-repcache</tt>
+will process that revision only:</p>
+
+<pre>
+    $ svnadmin build-repcache /path/to/repo -r20
+    * Processed revision 20.
+</pre>
+
+<p>If no revision argument is given, <tt>svnadmin build-repcache</tt> will
+process all revisions.</p>
+
+</div> <!-- svnadmin-build-repcache -->
+
 </div>  <!-- new-features -->
 
 <div class="h2" id="enhancements">
@@ -190,6 +317,266 @@ users.  We'll cover those in this sectio
     title="Link to this section">&para;</a>
 </h3>
 
+<div class="h4" id="log-quiet-diff">
+<h4><tt>svn log </tt> improvements
+  <a class="sectionlink" href="#log-quiet-diff"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p><tt>svn log --quiet </tt> and <tt>--diff </tt> options are no longer
+mutually exclusive. This makes it easier to display only the differences
+in a range of revisions. (See <a href="http://svn.apache.org/r1871916">r1871916</a>.)</p>
+
+</div> <!-- log-quiet-diff -->
+
+<div class="h4" id="info-show-item-changelist">
+<h4><tt>svn info </tt> improvements
+  <a class="sectionlink" href="#info-show-item-changelist"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>New <tt>changelist </tt> argument to <tt>svn info --show-item </tt>
+(<a href="http://svn.apache.org/r1869481">r1869481</a>).</p>
+
+</div> <!-- info-show-item-changelist -->
+
+<div class="h4" id="editor-filename-escaping">
+<h4>Escaping/quoting of pathname arguments to the user-defined editor
+  <a class="sectionlink" href="#editor-filename-escaping"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>When invoking the user-defined editor, such as during interactive conflict
+resolution, Subversion now performs escaping of any special characters in the
+pathname of the file to be edited. This corrects a problem that would occur
+previously when the file to be edited (and/or the path leading to it)
+contained spaces or other special characters. (See
+<a href="http://svn.apache.org/r1874057">r1874057</a>,
+<a href="http://svn.apache.org/r1874093">r1874093</a>, and
+<a href="http://svn.apache.org/r1875230">r1875230</a>.)</p>
+
+<p>Note that escaping is performed only on the pathname argument. As before,
+the editor itself is invoked through the shell and the user must properly
+quote/escape the command line used to launch it. This is intentional, as it
+allows the user to construct a shell command which itself contains command
+line arguments. See the related
+<a href="https://subversion.apache.org/faq.html#svn-editor">FAQ entry</a> for
+more on spaces and/or command line options in the editor path.</p>
+
+<p>The user-defined editor can be specified in the following ways, in this
+order of precedence:</p>
+
+<ul>
+  <li>The <tt>--editor-cmd</tt> command-line option</li>
+  <li>The <tt>$SVN_EDITOR</tt> environment variable</li>
+  <li>The <tt>editor-cmd</tt> runtime configuration option</li>
+  <li>The <tt>$VISUAL</tt> environment variable</li>
+  <li>The <tt>$EDITOR</tt> environment variable</li>
+</ul>
+
+<p>The escaped pathname of the file to be edited is passed to the editor as
+its last command line argument.</p>
+
+<p>For example, suppose that <tt>$SVN_EDITOR</tt> is set as follows:</p>
+
+<pre>SVN_EDITOR='vim -N --'
+export SVN_EDITOR
+</pre>
+
+<p>Furthermore, suppose 'svn up' finds a text conflict in a file called
+<tt>foo bar.txt</tt>:</p>
+
+<pre>
+$ svn up 
+Updating '.':
+C    foo bar.txt
+Updated to revision 2.
+Summary of conflicts:
+  Text conflicts: 1
+Merge conflict discovered in file 'foo bar.txt'.
+Select: (p) Postpone, (df) Show diff, (e) Edit file, (m) Merge,
+        (s) Show all options: <b>e</b>
+</pre>
+
+<p>When Subversion launches the editor, the spaces in <tt>vim -N --</tt> will
+<strong>not</strong> be escaped, allowing vim to be invoked with <tt>-N</tt>
+and <tt>--</tt> as its first two arguments, but the space in
+<tt>foo bar.txt</tt> <strong>will</strong> be escaped.</p>
+
+</div> <!-- editor-filename-escaping -->
+
+<div class="h4" id="conflict-resolver">
+<h4>Improvements to the interactive conflict resolver
+  <a class="sectionlink" href="#conflict-resolver"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>Since its introduction in 1.10, the new interactive conflict resolver has
+received various improvements.</p>
+
+<p>Starting in 1.11, the interactive conflict resolver supports more conflict
+situations which involve moved files and directories. Specifically, many tree
+conflicts which report a "locally missing" item, as a result of an item having
+moved on the merge source branch, can now be resolved automatically.</p>
+
+<p>For example, when a file edit is cherry-picked from a branch on which
+the edited file has been renamed, the edit will now be applied to the file's
+location in the merge target branch, provided it has not been renamed
+on that branch as well. For details, see
+<a href="https://issues.apache.org/jira/browse/SVN-4694">issue #4694</a>,
+"Unresolvable tree conflict when cherrypicking a file-edit after file was
+moved on source branch".</p>
+
+<p>Furthermore, since 1.12, the interactive conflict resolver supports some
+cases where items were moved to disparate locations. Support for unversioned
+items in the working copy has been improved as well. The table below lists
+these cases and available resolution options for each.</p>
+
+<table border="1">
+  <tr>
+    <th>local change</th>
+    <th>incoming change</th>
+    <th>operation</th>
+    <th>resolution options</th>
+  </tr>
+  <tr>
+    <td><ul>
+      <li>move file</li>
+    </ul></td>
+    <td><ul>
+      <li>move file</li>
+    </ul></td>
+    <td>update, merge</td>
+    <td><ul>
+      <li>merge<br>(applies textual changes only and leaves the tree structure
+      of the working copy as it is)
+      <li>move and merge<br>(changes the file's location in the working copy
+      to match that of the merge source before merging changes)
+    </ul></td>
+  </tr>
+  <tr>
+    <td><ul>
+      <li>move directory</li>
+    </ul></td>
+    <td><ul>
+      <li>move directory</li>
+    </ul></td>
+    <td>merge</td>
+    <td><ul>
+      <li>merge<br>(applies changes to the corresponding directory and leaves
+       the tree structure of the working copy as it is)
+      <li>move and merge<br>(changes the directory's location in the working
+       copy to match that of the merge source before merging changes)
+    </ul></td>
+  <tr>
+    <td><ul>
+      <li>unversioned file</li>
+    </ul></td>
+    <td><ul>
+      <li>add file</li>
+    </ul></td>
+    <td>update, switch </td>
+    <td><ul>
+      <li>merge<br>(merges the unversioned file with the incoming file)
+    </ul></td>
+  </tr>
+  <tr>
+    <td><ul>
+      <li>unversioned directory</li>
+    </ul></td>
+    <td><ul>
+      <li>add directory</li>
+    </ul></td>
+    <td>update, switch </td>
+    <td><ul>
+      <li>merge<br>(re-adds directory to working copy but leaves any on-disk
+      files as they were)
+    </ul></td>
+  </tr>
+</table>
+
+<p>During <tt>svn update</tt>, the deletion of a directory which contains
+unversioned items but is otherwise unmodified no longer causes a tree
+conflict. This avoids tree conflicts caused by software build artifacts
+in the working copy, for example.</p>
+
+<p>Several bugs have been fixed in the conflict resolver, including:
+<ul>
+<li><a href="https://issues.apache.org/jira/browse/SVN-4744">Issue #4744</a>
+&quot;assertion failed (start_rev &gt; end_rev)&quot;</li>
+<li><a href="https://issues.apache.org/jira/browse/SVN-4766">Issue #4766</a>
+&quot;resolver adds unrelated moves to move target list&quot;</li>
+<li>A problem where the resolver mistakenly
+<a href="https://svn.apache.org/r1839662">searched back through
+the entire history of the repository</a></li>
+<li>A case where text conflicts were created with the incoming changes 
+theirs) and local changes (mine) swapped within text conflict markers. This
+caused unexpected results when the <tt>svn resolve</tt> command was used with
+the <tt>--accept theirs</tt> or <tt>--accept mine</tt> options. This is fixed
+as of 1.12.</li>
+</ul>
+</p>
+
+<p>Fixes for conflict resolver bugs found during the development of
+Subversion 1.11 and 1.12 have been backported to the
+<a href="1.10.html">Subversion 1.10</a> release series as well.</p>
+
+</div> <!-- conflict-resolver -->
+
+<div class="h4" id="info-show-item">
+<h4>Additions to <tt>svn info --show-item</tt>
+  <a class="sectionlink" href="#info-show-item"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.11.</p>
+
+<p>Add '<tt>schedule</tt>' and '<tt>depth</tt>' items to '<tt>svn info --show-item</tt>' (<a href="http://svn.apache.org/r1827032">r1827032</a>).</p>
+
+</div> <!-- info-show-item -->
+
+<div class="h4" id="save-client-cert-pw">
+<h4>Allow the client cert password to be saved
+  <a class="sectionlink" href="#save-client-cert-pw"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.11.</p>
+
+<p>Allow the client cert password to be saved (<a href="http://svn.apache.org/r1836762">r1836762</a>).</p>
+
+</div> <!-- save-client-cert-pw -->
+
+<div class="h4" id="help-hide-experimental">
+<h4><tt>svn help</tt> hides experimental commands by default
+  <a class="sectionlink" href="#help-hide-experimental"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.13.</p>
+
+<p>By default, <tt>svn help</tt> no longer lists experimental commands.
+To show experimental commands, use <tt>svn help -v</tt> or
+<tt>svn help --verbose</tt>. (See <a href="https://issues.apache.org/jira/browse/SVN-4766">issue #4828</a>.)</p>
+
+</div> <!-- help-hide-experimental -->
+
+<div class="h4" id="sqlite-omit-wal">
+<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 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.
+(See <a href="http://svn.apache.org/r1865523">r1865523</a>.)</p>
+
+</div> <!-- sqlite-omit-wal -->
+
 </div> <!-- cmdline -->
 
 <div class="h3" id="server-side-improvements">
@@ -198,6 +585,49 @@ users.  We'll cover those in this sectio
      title="Link to this section">&para;</a>
 </h3>
 
+<div class="h4" id="issue-4767">
+<h4><tt>svnadmin dump</tt> shouldn't canonicalize <tt>svn:date</tt>
+  (<a href="https://issues.apache.org/jira/browse/SVN-4767">issue #4767</a>)
+  <a class="sectionlink" href="#issue-4767"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.11.</p>
+
+<p><tt>svnadmin dump</tt> no longer attempts to canonicalize the
+  <tt>svn:date</tt> revision property value in its output. The dump output
+  will now contain the value exactly as it exists in the repository.</p>
+
+</div> <!-- issue-4767 -->
+
+<div class="h4" id="authz-groups">
+<h4>Empty group definitions in authz rules
+  <a class="sectionlink" href="#authz-groups"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.12.</p>
+
+<p>Subversion servers will now ignore empty group definitions in their
+path-based authorization rules. The <tt>svnauthz</tt> command will print
+a warning if it detects empty group definitions.</p>
+</div> <!-- authz-groups -->
+
+<div class="h4" id="mod-dav-svn-twice-hint">
+<h4>Provide a hint about a possible mod_dav_svn misconfiguration
+  <a class="sectionlink" href="#mod-dav-svn-twice-hint"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.13.</p>
+
+<p>Add a hint about a possible mod_dav_svn misconfiguration: When warning
+about an overlapping configuration, if two configuration blocks are for the
+same URL, then hint that the problem may be including the same configuration
+twice. (See <a href="http://svn.apache.org/r1866738">r1866738</a>.)</p>
+
+</div> <!-- mod-dav-svn-twice-hint -->
+
 </div> <!-- server-side-improvements -->
 
 <div class="h3" id="client-server-improvements">
@@ -206,6 +636,79 @@ users.  We'll cover those in this sectio
      title="Link to this section">&para;</a>
 </h3>
 
+<div class="h4" id="plaintext-passwords-disabled">
+<h4>Plaintext passwords on disk disabled by default
+  <a class="sectionlink" href="#plaintext-passwords-disabled"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.12.</p>
+
+<p>On Unix-like systems, client-side storage of passwords in plaintext on
+disk is now disabled by default <em>at compile-time</em>.
+Password caching mechanisms based on Gnome Keyring, Kwallet, or GPG-Agent,
+are recommended instead.</p>
+
+<p>This change does not affect Windows or Mac OS platforms, where passwords
+have always been stored in an encrypted representation.</p>
+</div> <!-- plaintext-passwords-disabled -->
+
+<div class="h4" id="repos-wc-copy">
+<h4>Improved copying from repository source to working copy target
+  <a class="sectionlink" href="#repos-wc-copy"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.12.</p>
+
+<p>Behaviour of copy operations with a repository source and a working copy
+target has been improved:</p>
+
+<ul>
+<li>Existing parent directories are now handled correctly.</li>
+<li>Peg and operative revisions are now handled correctly (see
+<a href="https://issues.apache.org/jira/browse/SVN-4785">issue #4785</a>
+for details).</li>
+</ul>
+</div> <!-- repos-wc-copy -->
+
+<div class="h4" id="svn-list">
+<h4><tt>svn list</tt> improvements
+  <a class="sectionlink" href="#svn-list"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.12.</p>
+<p>The <tt>svn list</tt> command now avoids truncation of long author names
+by dynamically adjusting the width of columns displayed.</p>
+<p>The <tt>svn list</tt> command now supports a <tt>--human-readable</tt>
+(<tt>-H</tt>) option which will display sizes in human-readable units
+(Bytes, Kilobytes, Megabytes, Gigabytes, Terabytes and Petabytes).</p>
+</div> <!-- svn-list -->
+
+<div class="h4" id="svn-info">
+<h4><tt>svn info</tt> improvements
+  <a class="sectionlink" href="#svn-info"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.12.</p>
+<p>The <tt>svn info</tt> command can now display the size of files in the
+repository. The file size is only displayed if the target of <tt>svn info</tt>
+is a file URL.</p>
+</div> <!-- svn-info -->
+
+<div class="h4" id="svn-cleanup">
+<h4><tt>svn cleanup</tt> improvements
+  <a class="sectionlink" href="#svn-cleanup"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.12.</p>
+<p>The <tt>svn cleanup</tt> command, when asked to remove unversioned or
+ignored items, will now remove directories even if they are write-protected.</p>
+</div> <!-- svn-cleanup -->
+
 </div> <!-- client-server-improvements -->
 
 <div class="h3" id="apis">
@@ -227,16 +730,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
@@ -356,12 +849,387 @@ of Subversion's dependencies, see the
 
 </div>  <!-- py3c -->
 
+<div class="h4" id="swig4-on-py3">
+<h4>Support for building with SWIG 4 on Python 3.x
+  <a class="sectionlink" href="#swig4-on-py3"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p><em>This section only affects those who build Subversion from a working
+  copy.  If you build Subversion from a tarball or zip file, you may skip
+  this section.</em></p>
+
+<p>Subversion's SWIG Python bindings can be built with SWIG 4 on Python 3.
+The bindings can be built with SWIG 3.x on Python 3 as well (the
+<tt>-modern</tt> argument to SWIG is automatically used). (See
+<a href="http://svn.apache.org/r1869853">r1869853</a>.)</p>
+
+</div>  <!-- swig4-on-py3 -->
+
+<div class="h4" id="javahl">
+<h4>JavaHL Updates
+  <a class="sectionlink" href="#javahl"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.11.</p>
+
+<p>The JavaHL bindings have been updated to be compatible with Java 10.  Due
+  to required build changes, JavaHL now requires at least Java 8 to compile.</p>
+
+</div>  <!-- javahl -->
+
 </div>  <!-- apis -->
 
 </div>  <!-- enhancements -->
 
+<div class="h2" id="experimental">
+<h2>Experimental Features
+  <a class="sectionlink" href="#experimental"
+    title="Link to this section">&para;</a>
+</h2>
+
+<!--
+<p>There are no experimental features in this release at the moment.</p>
+-->
+
+<div class="notice">
+  <p>The Subversion 1.14.x release includes several "EXPERIMENTAL" features.
+  These are released in an early form for purposes of testing, feedback, and
+  to entice interested users to <a href="#enthusiastic-contributors"
+  >contribute</a> to their further development.</p>
+
+  <p><span style="color: red"><b>WARNING:</b></span> Features and APIs which
+  are designated "EXPERIMENTAL" are considered incomplete and may change
+  significantly during and after the 1.14.x series. There is no promise of
+  backward compatibility, even from one point release to another, while they
+  remain experimental.</p>
+</div>
+
+<div class="h3 experimental-feature" id="shelving">
+<h3>Shelving and Checkpointing (experimental)
+  <a class="sectionlink" href="#shelving"
+     title="Link to this section">&para;</a>
+</h3>
+
+<p>Shelving (<a href="https://issues.apache.org/jira/browse/SVN-3625">issue
+#3625</a>), first introduced in Subversion 1.10, has been developed further to
+handle more kinds of changes more robustly. Two different versions of shelving
+CLIs, each with different pros and cons, are available for experimentation.
+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>
+  to learn how to recover 1.10 shelves in a working copy.</p>
+</div>
+
+<p>Shelving commands (see their help for details):</p>
+<ul>
+    <li><tt>svn x-shelf-diff</tt></li>
+    <li><tt>svn x-shelf-drop</tt></li>
+    <li><tt>svn x-shelf-list, x-shelves</tt></li>
+    <li><tt>svn x-shelf-list-by-paths</tt></li>
+    <li><tt>svn x-shelf-log</tt></li>
+    <li><tt>svn x-shelf-save</tt></li>
+    <li><tt>svn x-shelve</tt></li>
+    <li><tt>svn x-unshelve</tt></li>
+</ul>
+
+<p>Differences in the main shelving commands since 1.10:</p>
+
+<table>
+<tr><th>Subversion 1.10 command</th>
+    <th>Subversion 1.14 equivalent</th></tr>
+<tr><td><tt>svn [x-]shelve [--keep-local] SHELF [PATH...]</tt></td>
+    <td>works similarly; saves a new version each time it is used</td></tr>
+<tr><td><tt>svn [x-]unshelve [SHELF]</tt></td>
+    <td><tt>svn x-unshelve --drop [SHELF]</tt></td></tr>
+<tr><td><tt>svn [x-]unshelve --keep-shelved [SHELF]</tt></td>
+    <td><tt>svn x-unshelve [SHELF]</tt></td></tr>
+<tr><td><tt>svn [x-]shelve --delete SHELF</tt></td>
+    <td><tt>svn x-shelf-drop SHELF</tt></td></tr>
+<tr><td><tt>svn [x-]shelves</tt> or <tt>svn [x-]shelve --list</tt></td>
+    <td><tt>svn x-shelves</tt> or <tt>svn x-shelf-list</tt></td></tr>
+</table>
+
+<div class="h4 experimental-feature" id="shelving-enabling">
+<h4>Choosing and Enabling a Shelving CLI
+  <a class="sectionlink" href="#shelving-enabling"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>Because shelving is a work-in-progress, the shelving CLI is disabled by
+default. Users who wish to experiment with shelving should enable one of the
+two available shelving CLI implementations by setting an environment variable
+(see <a href="http://svn.apache.org/r1875037">r1875037</a> and
+<a href="http://svn.apache.org/r1875039">r1875039</a>.)</p>
+
+<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. (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>
+
+<table border="1">
+  <tr>
+    <th>environment variable</th>
+    <th>shelving CLI implementation</th>
+  </tr>
+  <tr>
+    <td><tt>SVN_EXPERIMENTAL_COMMANDS=shelf3</tt></td>
+    <td>Shelving-v3, as introduced in 1.12</td>
+  </tr>
+  <tr>
+    <td><tt>SVN_EXPERIMENTAL_COMMANDS=shelf2</tt></td>
+    <td>Shelving-v2, as introduced in 1.11</td>
+  </tr>
+  <tr>
+    <td><tt>SVN_EXPERIMENTAL_COMMANDS=</tt></td>
+    <td>No shelving CLI</td>
+  </tr>
+  <tr>
+    <td>Environment variable not set</td>
+    <td>No shelving CLI</td>
+  </tr>
+</table>
+
+<p>The following table summarizes the kinds of changes that can be shelved by
+the two implementations:</p>
+
+<table border="1">
+  <tr>
+    <th>WC State or Change</th>
+    <th>Shelving-v2</th>
+    <th>Shelving-v3</th>
+  </tr>
+  <tr>
+    <td>file text, file delete/add, most properties</td>
+    <td>yes</td>
+    <td>yes</td>
+  </tr>
+  <tr>
+    <td>mergeinfo changes</td>
+    <td>yes</td>
+    <td>yes</td>
+  </tr>
+  <tr>
+    <td>copies and moves</td>
+    <td>no</td>
+    <td>as copies<sup>1</sup></td>
+  </tr>
+  <tr>
+    <td>directories (mkdir/rmdir/...)</td>
+    <td>no</td>
+    <td>yes</td>
+  </tr>
+  <tr>
+    <td>binary files & properties</td>
+    <td>yes</td>
+    <td>yes</td>
+  </tr>
+  <tr>
+    <td colspan="3"><sup>1</sup>On shelving, a move is converted to
+    copy-and-delete, just like it is on commit.
+    </td>
+  </tr>
+</table>
+
+</div>  <!-- shelving-enabling -->
+
+<div class="h4 experimental-feature" id="shelving-v2">
+<h4>Shelving-v2
+  <a class="sectionlink" href="#shelving-v2"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>Shelving-v2, first introduced in 1.11, improves upon the initial shelving
+feature introduced in 1.10. The main improvements and changes are:</p>
+<ul>
+    <li>checkpointing support: a shelf stores multiple versions of a
+        change; shelving adds a new version to the named shelf; you can
+        unshelve an older version instead of the newest&mdash;see the
+        <a href="#shelving-checkpointing">commit checkpointing</a> feature</li>
+    <li>'binary' files (and property values) are fully supported</li>
+    <li>patch files are no longer used as the storage mechanism;
+        limitations and bugs due to patch file format are gone, such as
+        handling svn:mergeinfo properties, binary data, and end-of-line
+        characters</li>
+    <li>shelving and unshelving both warn and refuse to run if they detect
+        states that they cannot handle (e.g. copies or moves)</li>
+    <li>unshelving applies the changes to the WC using a mechanism similar
+        to merging, so that changes can be more robustly applied when the
+        WC has been modified (e.g. updated) since the shelf was saved</li>
+</ul>
+
+<p>Shelving-v2 can shelve committable changes to files and properties, except
+the following kinds which it does not support:</p>
+<ul>
+    <li>copies and moves</li>
+    <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">
+<h4>Shelving-v3
+  <a class="sectionlink" href="#shelving-v3"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>Shelving-v3, first introduced in 1.12, can handle more kinds of changes
+than Shelving-v2. In particular, it supports shelving of all committable
+changes. However, it performs much more slowly than Shelving-v2 and uses more
+disk space, especially when used with large working copies.</p>
+
+<p>This version of shelving represents a series of significant refactorings
+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">
+<h4>Upgrading 1.10&ndash;1.13 shelves to 1.14
+  <a class="sectionlink" href="#shelving-transition"
+    title="Link to this section">&para;</a>
+</h4>
+
+<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>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>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">
+<h4>Commit checkpointing (experimental)
+  <a class="sectionlink" href="#shelving-checkpointing"
+     title="Link to this section">&para;</a>
+</h4>
+
+<p>This change was first introduced in 1.11.</p>
+
+<p>Since 1.11, Subversion provides an experimental first cut at solving some
+of the use cases envisioned in <a
+href="https://issues.apache.org/jira/browse/SVN-3626">issue #3626</a> named
+"Commit checkpointing".</p>
+
+<p>It provides the ability to save a snapshot of an uncommitted change from
+time to time, and later restore one of those previous versions of your
+change back into the working copy.</p>
+
+<p>It does not provide the kind of exact WC state roll back that is also
+discussed in that issue, that could make it possible after a messy update to
+roll back to the exact WC state that existed just before. This remains a
+future possibility.</p>
+
+<p>The ability to checkpoint and roll back an uncommitted change is provided
+within the shelving feature, by letting a shelf hold multiple versions of
+your change. Therefore, see also <a href="#shelving"> Shelving</a>.</p>
+
+<p>The main checkpointing operations are accomplished by the following
+commands, as also listed in
+<a href="https://cwiki.apache.org/confluence/x/70cYBQ">the Wiki page</a>:</p>
+
+<table>
+<tr><th>Save a checkpoint and continue</th>
+    <td><tt>svn x-<b>shelf-save</b> foo</tt></td>
+    <td>copy the local changes into a new version of shelf 'foo';<br/>
+        doesn't revert the changes from the WC</td>
+</tr>
+<tr><th>Save a checkpoint and shelve</th>
+    <td><tt>svn x-<b>shelve</b> foo</tt></td>
+    <td>move the local changes into a new version of shelf 'foo'<br/>
+        and revert the changes from the WC</td>
+</tr>
+<tr><th>Restore / roll back</th>
+    <td>first revert your unwanted changes; then<br/>
+        <tt>svn x-<b>unshelve</b> foo 3</tt></td>
+    <td>apply version 3 of shelf 'foo' to the WC<br/>
+        and delete any newer versions</td>
+</tr>
+<tr><th>Review checkpoints</th>
+    <td><tt>svn x-<b>shelf-log</b> foo</tt></td>
+    <td>list all the versions of shelf 'foo'</td>
+</tr>
+<tr><th></th>
+    <td><tt>svn x-<b>shelf-diff</b> foo 3</tt></td>
+    <td>show version 3 as a diff</td>
+</tr>
+</table>
+
+</div>  <!-- shelving-checkpointing -->
+
+<p>Further information can be found in the Subversion Wiki under
+<a href="https://cwiki.apache.org/confluence/display/SVN/Shelving+and+Checkpointing"
+>Shelving and Checkpointing</a>, including internal design and development
+notes.</p>
+
+</div>  <!-- shelving -->
+
+<div class="h3 experimental-feature" id="viewspec-output">
+<h3>Viewspec output command (experimental)
+  (<a href="https://issues.apache.org/jira/browse/SVN-4753">issue #4753</a>)
+  <a class="sectionlink" href="#viewspec-output"
+     title="Link to this section">&para;</a>
+</h3>
+
+<p>This change was first introduced in 1.11.</p>
+
+<p>There is an experimental command to write out a view spec describing the
+current WC shape.</p>
+
+<p>A view spec describes whether each subtree is at a limited depth, excluded,
+switched to a different URL, or updated to a different revision number,
+compared with its parent directory. This information is sometimes referred
+to as the shape or the layout of a WC.</p>
+
+<p>'<tt>svn info --x-viewspec=classic</tt>' writes in the format used by the old script
+<a href="http://svn.apache.org/viewvc/subversion/trunk/tools/client-side/svn-viewspec.py">tools/client-side/svn-viewspec.py</a>.</p>
+
+<p>'<tt>svn info --x-viewspec=svn11</tt>' writes a series of '<tt>svn</tt>'
+command lines. You can create a new WC of the same layout by running these
+commands.</p>
+
+</div> <!-- viewspec-output -->
+
+</div>  <!-- experimental -->
+
 <div class="h2" id="issues">
-<h2>Known issues in the release
+<h2>Known Issues in the Release
   <a class="sectionlink" href="#issues"
     title="Link to this section">&para;</a>
 </h2>
@@ -379,17 +1247,77 @@ may be fixed in later 1.14.x releases.</
     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 -->
 
+<div class="h3" id="ruby-swig-issue-602">
+<h3>Ruby bindings require swig 3.0.9
+  <a class="sectionlink" href="#ruby-swig-issue-602"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>This change was first introduced in 1.11.</p>
+
+<p><em>This section only affects those who build Subversion from a working
+  copy.  If you build Subversion from a tarball or zip file, you may skip
+  this section.</em></p>
+
+<p>The Ruby bindings are known not to build with swig version 3.0.8 (and only
+that version) due to <a href="https://github.com/swig/swig/issues/602">swig
+issue #602</a>.  We recommend to use swig 3.0.9 or newer.</p>
+
+<p>The failure is detected by the test suite.
+To test whether your version of swig is affected, run
+<tt>make check-swig-rb</tt>.  (Some distros might have backported the swig
+patch into their swig-3.0.8 packages.)</p>
+
+<p>The Perl and Python bindings are not affected.</p>
+
+</div>  <!-- ruby-swig-issue-602 -->
+
 </div>  <!-- issues -->
 
 <!-- (This section only makes sense when there are some issues listed in it.)
@@ -411,18 +1339,74 @@ if they occur.</p>
 </div>  <!- - troubleshooting - ->
 -->
 
-<div class="h2" id="lts-release">
-<h2>Subversion 1.14.x is a Long-Term Support (LTS) Release
+<div class="h2" id="support">
+<h2>Support and Release Planning
   <a class="sectionlink" href="#lts-release"
     title="Link to this section">&para;</a>
 </h2>
 
+<div class="h3" id="lts-release">
+<h3>Subversion 1.14.x is a Long-Term Support (LTS) Release
+  <a class="sectionlink" href="#lts-release"
+    title="Link to this section">&para;</a>
+</h3>
+
 <p>1.14 is a Long-Term Support (LTS) release.
    See <a href="/docs/release-notes/#supported-versions">Supported Versions</a>
    and <a href="/roadmap.html#release-planning">How We Plan Releases</a>.</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"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>The Subversion 1.10.x line is now the old stable version.  This means
+that 1.10.x will still receive security relevant fixes as well as
+bugfixes. While we will evaluate any bugreport with regards to its
+severity, there might be issues with a lower severity which will
+only get fixed in 1.14.x, particularly if the patches would be invasive,
+destabilizing, and/or require a significant investment to get backported to the
+old stable version.</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>
+
+</div>  <!-- svn-1.10-old-stable -->
+
+<div class="h3" id="svn-1.9-deprecation">
+<h3>Subversion 1.9.x is end of life
+  <a class="sectionlink" href="#svn-1.9-deprecation"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>The Subversion 1.9.x line is end of life (<abbr title="End Of Life">EOL</abbr>).
+This doesn't mean that your 1.9 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.9.x versions, and will not
+make any more 1.9.x releases.</p>
+
+</div>  <!-- svn-1.9-deprecation -->
+
+</div>  <!-- support -->
+
 <div class="h2" id="enthusiastic-contributors">
 <h2>Enthusiastic Contributors Welcome!
   <a class="sectionlink" href="#enthusiastic-contributors"
@@ -435,9 +1419,10 @@ if they occur.</p>
 volunteers, we are always happy to welcome enthusiastic participants
 to the community.</p>
 
-<p>Whether you'd like to see support for additional versions of Python
-or have ideas for some big new features, if you're willing to invest
-the effort, Subversion can be anything you imagine.</p>
+<p>Whether you'd like to see support for additional versions of Python,
+want to help finish Shelving and Checkpointing, or have ideas for some big
+new features, if you're willing to invest the effort, Subversion can be
+anything you imagine.</p>
 
 <p>Join the conversation by email: For our mailing lists, see
 <a href="https://subversion.apache.org/mailing-lists.html">
@@ -451,10 +1436,14 @@ https://subversion.apache.org/mailing-li
 
 <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>

Modified: subversion/site/staging/docs/release-notes/index.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/index.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/index.html (original)
+++ subversion/site/staging/docs/release-notes/index.html Wed Jul  8 13:34:59 2020
@@ -47,7 +47,7 @@ official support status for the various
 <p>Here are the release notes for the major Subversion releases:</p> 
 
 <ul id="release-notes-list">
-<li><a href="1.14.html">Subversion 1.14</a> – <i>in progress</i></li>
+<li><a href="1.14.html">Subversion 1.14</a> – (<i>first released – May 27, 2020</i>)</li>
 <li><a href="1.13.html">Subversion 1.13</a> – (<i>first released – October 30, 2019</i>)</li>
 <li><a href="1.12.html">Subversion 1.12</a> – (<i>first released – April 24, 2019</i>)</li>
 <li><a href="1.11.html">Subversion 1.11</a> – Improved shelving, checkpointing, improved tree conflict resolution (<i>first released – October 30, 2018</i>)</li>

Modified: subversion/site/staging/docs/release-notes/release-history.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/release-history.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/release-history.html (original)
+++ subversion/site/staging/docs/release-notes/release-history.html Wed Jul  8 13:34:59 2020
@@ -31,6 +31,9 @@ Subversion 2.0.</p>
 
 <ul>
   <li>
+    <b>Subversion 1.14.0</b> (Wednesday, 27 May 2020): Feature and bugfix release, see the <a href="/docs/release-notes/1.14.html">release notes</a>.
+  </li>
+  <li>
     <b>Subversion 1.13.0</b> (Wednesday, 30 October 2019): Feature and bugfix release, see the <a href="/docs/release-notes/1.13.html">release notes</a>.
   </li>
   <li>

Modified: subversion/site/staging/download.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/download.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/download.html (original)
+++ subversion/site/staging/download.html Wed Jul  8 13:34:59 2020
@@ -17,23 +17,21 @@
 
 <h1>Download Source Code</h1>
 
-[define version]1.14.0[end]
+[define version]1.14[end]
 
 <div class="notice">
 <p>Learn about our new 6-month regular and 2-year LTS release schedule: see
 <a href="/roadmap.html#release-planning">How We Plan Releases</a>.</p>
 </div>
 
-<!--
 <div class="bigpoint">
-<p>The latest regular release of Apache Subversion
+<p>The latest and recommended LTS (long-term support) release of Apache Subversion
    is:&nbsp;<a href="#recommended-release">[version]</a></p>
 </div> <!-- .bigpoint -->
--->
 
 <div class="bigpoint">
-<p>The latest LTS (long-term support) release of Apache Subversion
-   is:&nbsp;<a href="#supported-releases">1.14 LTS</a></p>
+<p>The older still supported release of Apache Subversion
+   is:&nbsp;<a href="#supported-releases">1.10</a></p>
 </div> <!-- .bigpoint -->
 
 <p>Use the links below to download Apache Subversion from one of our mirrors.
@@ -98,27 +96,12 @@ Other mirrors:
    files.  Users of all other operating systems should
    download <tt>.tar.gz</tt> or <tt>.tar.bz2</tt> files.</p>
 
-<!--
 <div class="h3" id="recommended-release">
-<h3>Latest Regular Release
+<h3>Recommended Release
   <a class="sectionlink" href="#recommended-release"
     title="Link to this section">&para;</a>
 </h3>
 
-<p><a href="/roadmap.html#release-planning">Regular releases</a>
-   are supported for <b>6 months</b>.</p>
-
-</div> --> <!-- #recommended-release -->
-
-<div class="h3" id="supported-releases">
-<h3>LTS Releases
-  <a class="sectionlink" href="#supported-releases"
-    title="Link to this section">&para;</a>
-</h3>
-
-<p><a href="/roadmap.html#release-planning">LTS releases</a>
-   receive Long-Term Support for <b>4 years</b>.</p>
-
 <p style="font-size: 150%; text-align: center;">Apache Subversion 1.14.0 LTS</p>
 <table class="centered">
 <tr>
@@ -145,6 +128,14 @@ Other mirrors:
 </tr>
 </table>
 
+</div> <!-- #recommended-release -->
+
+<div class="h3" id="supported-releases">
+<h3>Older still supported Releases
+  <a class="sectionlink" href="#supported-releases"
+    title="Link to this section">&para;</a>
+</h3>
+
 <p style="font-size: 150%; text-align: center;">Apache Subversion 1.10.6 LTS</p>
 <table class="centered">
 <tr>
@@ -236,8 +227,7 @@ Other mirrors:
    Subversion as to HTTP Server.)</p>
    
 <p>The PGP signatures can be verified using PGP or GPG. First download
-   the <a href="https://www.apache.org/dist/subversion/KEYS"
-   >KEYS</a> as well as the <code>asc</code> signature file for the
+   the keyring (<code>*.KEYS</code>) and detached signatures (<code>*.asc</code>) files for the
    particular distribution. Make sure you get these files from the
    <a href="https://www.apache.org/dist/subversion/" >main distribution
    directory</a>, rather than from a mirror. Then verify the

Modified: subversion/site/staging/faq.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/faq.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/faq.html (original)
+++ subversion/site/staging/faq.html Wed Jul  8 13:34:59 2020
@@ -2249,7 +2249,7 @@ the following should work:
 
 <p>In case a command line option would be needed for the invocation
 of the editor, just add that after the editor name in the SVN_EDITOR
-environment variable just like you would us on the command line.&nbsp;
+environment variable just like you would use on the command line.&nbsp;
 For example, if the options <code>-nx -r</code> would be wanted for
 the above editors, the following will provide those options:
 </p>

Modified: subversion/site/staging/index.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/index.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/index.html (original)
+++ subversion/site/staging/index.html Wed Jul  8 13:34:59 2020
@@ -66,47 +66,42 @@
 
 <!-- In general, we'll keep only the most recent 3 or 4 news items here. -->
 
-<div class="h3" id="news-20191030"> 
-<h3>2019-10-30 &mdash; Apache Subversion 1.13.0 Released
- <a class="sectionlink" href="#news-20191030"
+<div class="h3" id="news-20200527"> 
+<h3>2020-05-27 &mdash; Apache Subversion 1.14.0 Released
+ <a class="sectionlink" href="#news-20200527"
  title="Link to this section">&para;</a> 
 </h3> 
  
-<p>We are pleased to announce the release of Apache Subversion 1.13.0.
+<p>We are pleased to announce the release of Apache Subversion 1.14.0.
  This is the most complete Subversion release to date, and we encourage
  users of Subversion to upgrade as soon as reasonable.
  Please see the
- <a href="https://lists.apache.org/list.html?announce@subversion.apache.org"
- >release announcement</a> and the
- <a href="/docs/release-notes/1.13"
+ <a href="https://svn.haxx.se/dev/archive-2020-05/0151.shtml"
+ >release announcement</a>,
+ <a href="https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces62"
+ >press release</a>, and the
+ <a href="/docs/release-notes/1.14"
  >release notes</a> for more information about this release.</p> 
  
 <p>To get this release from the nearest mirror, please visit our
  <a href="/download.cgi#recommended-release">download page</a>.</p> 
  
-</div> <!-- #news-20191030 --> 
-
-<div class="h3" id="news-20190930"> 
-<h3>2019-09-30 &mdash; Apache Subversion 1.13.0-rc1 Released
- <a class="sectionlink" href="#news-20190930"
+</div> <!-- #news-20200527 --> 
+<div class="h3" id="news-20200227"> 
+<h3>2020-02-27 &mdash; Celebrating 20 Years of Subversion
+ <a class="sectionlink" href="#news-20200227"
  title="Link to this section">&para;</a> 
 </h3> 
- 
-<p>We are pleased to announce the release of Apache Subversion 1.13.0-rc1. This
- release is not intended for production use, but is provided as a milestone
- to encourage wider testing and feedback from intrepid users and maintainers.
- Please see the
- <a href="https://lists.apache.org/list.html?announce@subversion.apache.org">release
- announcement</a> for more information about this release, and the
- <a href="/docs/release-notes/1.13.html">release notes</a> and 
- <a href="https://svn.apache.org/repos/asf/subversion/tags/1.13.0-rc1/CHANGES"> 
- change log</a> for information about what will eventually be
- in the 1.13.0 release.</p> 
- 
-<p>To get this release from the nearest mirror, please visit our
- <a href="/download.cgi#pre-releases">download page</a>.</p> 
- 
-</div> <!-- #news-20190930 --> 
+
+<p>The very first CVS commit in what would become Apache Subversion
+ was recorded on a very special Leap Day, 29 February 2000.</p>
+
+<p>This year, celebrate with us as we mark Subversion's 20th Anniversary.
+ Read the <a href="https://s.apache.org/ApacheSVN20">Press Release</a> and
+ <a href="contributing.html">join our community</a> in writing the next
+ chapter of the Subversion story.</p>
+
+</div> <!-- #news-20200227 --> 
 
 <div class="h3" id="news-20190731">
 <h3>2019-07-31 &mdash; Apache Subversion Security Advisory
@@ -230,7 +225,7 @@
 
 <!-- see https://www.apache.org/foundation/marks/pmcs -->
 <p>The rest of this site is about Subversion &mdash; but Subversion doesn't
-   operate in vaccum.  It is part of the <a href="https://www.apache.org/"
+   operate in a vacuum.  It is part of the <a href="https://www.apache.org/"
    >Apache Software Foundation (ASF)</a>, which &mdash; in addition to the
    servers that run this site and our mailing lists &mdash; provides financial,
    technical, and legal backing.  The "About the ASF" section contains links

Propchange: subversion/site/staging/index.html
------------------------------------------------------------------------------
  Merged /subversion/site/publish/index.html:r1870064-1879654

Modified: subversion/site/staging/news.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/news.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/news.html (original)
+++ subversion/site/staging/news.html Wed Jul  8 13:34:59 2020
@@ -22,6 +22,66 @@
 <!-- Maybe we could insert H2's to split up the news items by  -->
 <!-- calendar year if we felt the need to do so.               -->
 
+<div class="h3" id="news-20200527"> 
+<h3>2020-05-27 &mdash; Apache Subversion 1.14.0 Released
+ <a class="sectionlink" href="#news-20200527"
+ title="Link to this section">&para;</a> 
+</h3> 
+ 
+<p>We are pleased to announce the release of Apache Subversion 1.14.0.
+ This is the most complete Subversion release to date, and we encourage
+ users of Subversion to upgrade as soon as reasonable.
+ Please see the
+ <a href="https://svn.haxx.se/dev/archive-2020-05/0151.shtml"
+ >release announcement</a>,
+ <a href="https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces62"
+ >press release</a>, and the
+ <a href="/docs/release-notes/1.14"
+ >release notes</a> for more information about this release.</p> 
+ 
+<p>To get this release from the nearest mirror, please visit our
+ <a href="/download.cgi#recommended-release">download page</a>.</p> 
+ 
+</div> <!-- #news-20200527 --> 
+
+<div class="h3" id="news-20200422"> 
+<h3>2020-04-22 &mdash; Apache Subversion 1.14.0-rc2 Released
+ <a class="sectionlink" href="#news-20200422"
+ title="Link to this section">&para;</a> 
+</h3> 
+ 
+<p>We are pleased to announce the release of Apache Subversion 1.14.0-rc2. This
+ release is not intended for production use, but is provided as a milestone
+ to encourage wider testing and feedback from intrepid users and maintainers.
+ Please see the
+ <a href="https://svn.haxx.se/users/archive-2020-04/0040.shtml">release
+ announcement</a> for more information about this release, and the
+ <a href="/docs/release-notes/1.14.html">release notes</a> and 
+ <a href="https://svn.apache.org/repos/asf/subversion/tags/1.14.0-rc2/CHANGES"> 
+ change log</a> for information about what will eventually be
+ in the 1.14.0 release.</p> 
+ 
+<p>To get this release from the nearest mirror, please visit our
+ <a href="/download.cgi#pre-releases">download page</a>.</p> 
+ 
+</div> <!-- #news-20200422 --> 
+
+<div class="h3" id="news-20200227"> 
+<h3>2020-02-27 &mdash; Celebrating 20 Years of Subversion
+ <a class="sectionlink" href="#news-20200227"
+ title="Link to this section">&para;</a> 
+</h3> 
+
+<p>The very first CVS commit in what would become Apache Subversion
+ was recorded on a very special Leap Day, 29 February 2000.</p>
+
+<p>This year, celebrate with us as we mark Subversion's 20th Anniversary.
+ Read the <a href="https://s.apache.org/ApacheSVN20">Press Release</a> and
+ <a href="contributing.html">join our community</a> in writing the next
+ chapter of the Subversion story.</p>
+
+</div> <!-- #news-20200227 --> 
+
 <div class="h3" id="news-20191030"> 
 <h3>2019-10-30 &mdash; Apache Subversion 1.13.0 Released
  <a class="sectionlink" href="#news-20191030"

Propchange: subversion/site/staging/news.html
------------------------------------------------------------------------------
  Merged /subversion/site/publish/news.html:r1870064-1879654

Propchange: subversion/site/staging/roadmap.html
------------------------------------------------------------------------------
  Merged /subversion/site/publish/roadmap.html:r1870064-1879654

Modified: subversion/site/staging/upcoming.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/upcoming.part.html?rev=1879655&r1=1879654&r2=1879655&view=diff
==============================================================================
--- subversion/site/staging/upcoming.part.html (original)
+++ subversion/site/staging/upcoming.part.html Wed Jul  8 13:34:59 2020
@@ -1,51 +1,87 @@
 <!-- Automatically generated by ^/subversion/site/tools/generate-upcoming-changes-log.sh -->
 <pre style="border-style: none">
-Changes in ^/subversion/branches/1.13.x:
+Changes in ^/subversion/branches/1.14.x:
 ------------------------------------------------------------------------
-<a href="https://svn.apache.org/r1868880">r1868880</a> | julianfoad | 2019-10-24 15:18:40 +0000 (Thu, 24 Oct 2019) | 10 lines
+<a href="https://svn.apache.org/r1877978">r1877978</a> | svn-role | 2020-05-21 04:00:13 +0000 (Thu, 21 May 2020) | 7 lines
 
-Merge <a href="https://svn.apache.org/r1868151">r1868151</a> from trunk:
+Merge <a href="https://svn.apache.org/r1877788">r1877788</a> from trunk:
 
- * <a href="https://svn.apache.org/r1868151">r1868151</a>
-   Fix syntax error when $PYTHON is Python 3.
+ * <a href="https://svn.apache.org/r1877788">r1877788</a>
+   Fix a broken link in a docstring.
+   Votes:
+     +1: danielsh, stsp
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1878211">r1878211</a> | svn-role | 2020-05-28 04:00:12 +0000 (Thu, 28 May 2020) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1877072">r1877072</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1877072">r1877072</a>
+   svnmucc: Change an error message to state another possible cause of the
+   error.
    Justification:
-     Python 2 will reach EOL during the lifetime of this branch.
+     Error messages should be accurate.  User reported (<a href="/issue-4854">issue #4854</a>).
    Votes:
-     +1: danielsh
-     +0: julianfoad (reviewed only)
+     +1: danielsh, stsp, jcorvel
 
 ------------------------------------------------------------------------
-<a href="https://svn.apache.org/r1868883">r1868883</a> | julianfoad | 2019-10-24 15:26:12 +0000 (Thu, 24 Oct 2019) | 10 lines
+<a href="https://svn.apache.org/r1878213">r1878213</a> | svn-role | 2020-05-28 04:00:16 +0000 (Thu, 28 May 2020) | 11 lines
+
+Merge <a href="https://svn.apache.org/r1877259">r1877259</a> from trunk:
 
-Merge <a href="https://svn.apache.org/r1868575">r1868575</a> from trunk:
+* <a href="https://svn.apache.org/r1877259">r1877259</a>
+    Move variable declarations to the start of block the to fix
+    syntax errors with VC9 (Visual Studio 2008).
+  Justification:
+    Our code should be C90.
+  Votes:
+    +1: brane, stsp, jcorvel
+    +0: danielsh (from dev@)
 
- * <a href="https://svn.apache.org/r1868575">r1868575</a>
-   Fix false positive on test with Python 3 
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1878415">r1878415</a> | svn-role | 2020-06-03 04:00:20 +0000 (Wed, 03 Jun 2020) | 12 lines
+
+Merge the <a href="https://svn.apache.org/r1876707">r1876707</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1876707">r1876707</a>, <a href="https://svn.apache.org/r1876734">r1876734</a>, <a href="https://svn.apache.org/r1877318">r1877318</a>, <a href="https://svn.apache.org/r1877712">r1877712</a>, <a href="https://svn.apache.org/r1878141">r1878141</a>, <a href="https://svn.apache.org/r1878142">r1878142</a>, <a href="https://svn.apache.org/r1878143">r1878143</a>,
+   <a href="https://svn.apache.org/r1878144">r1878144</a>
+   Various fixes for making the test suite run correctly with Python 3 on
+   Windows. 
    Justification:
-     Python 2 will reach EOL during the lifetime of this branch.
+     Our test suite should test Subversion correctly also on Windows with
+     Python 3
    Votes:
-     +1: danielsh
-     +0: julianfoad (reviewed only)
+     +1: futatuki, jcorvel, stsp
 
 ------------------------------------------------------------------------
-<a href="https://svn.apache.org/r1868914">r1868914</a> | julianfoad | 2019-10-25 09:26:59 +0000 (Fri, 25 Oct 2019) | 2 lines
+<a href="https://svn.apache.org/r1879245">r1879245</a> | svn-role | 2020-06-27 04:00:12 +0000 (Sat, 27 Jun 2020) | 11 lines
+
+Merge <a href="https://svn.apache.org/r1876662">r1876662</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1876662">r1876662</a>
+   Avoid check for SWIG version for Python bindings when --without-swig is
+   passed.
+   Justification:
+     SWIG python bindings should be able to be built without SWIG when we use
+     the release tarball
+   Votes:
+     +1: futatuki, stsp, rhuijben
 
-On &#x27;1.13.x&#x27;: merge <a href="https://svn.apache.org/r1868913">r1868913</a> from trunk (update release date in CHANGES).
 ------------------------------------------------------------------------
-<a href="https://svn.apache.org/r1870786">r1870786</a> | svn-role | 2019-12-04 04:00:30 +0000 (Wed, 04 Dec 2019) | 10 lines
+<a href="https://svn.apache.org/r1879246">r1879246</a> | svn-role | 2020-06-27 04:00:17 +0000 (Sat, 27 Jun 2020) | 10 lines
 
-Merge the <a href="https://svn.apache.org/r1870393">r1870393</a> group from trunk:
+Merge <a href="https://svn.apache.org/r1876906">r1876906</a> from trunk:
 
- * <a href="https://svn.apache.org/r1870393">r1870393</a>, <a href="https://svn.apache.org/r1870395">r1870395</a>
-   Fix <a href="/issue-4837">issue #4837</a> &#x27;Cannot get info for a file that was
-   inside of file-replaced directory&#x27;.
+ * <a href="https://svn.apache.org/r1876906">r1876906</a>
+   Make gen-make.py --debug work with Python 3
    Justification:
-     Regression introduced in 1.10.0.
+     We should also be able to build in Debug configuration with Python 3
+     on Windows.
    Votes:
-     +1: julianfoad, rhuijben, jamessan
+     +1: jcorvel, stsp, rhuijben
 
 ------------------------------------------------------------------------
 </pre>
 
 <p>Further changes currently under consideration are listed in each release line's 
-<a href="https://svn.apache.org/repos/asf/subversion/branches/1.13.x/STATUS">STATUS</a> file.</p>
+<a href="https://svn.apache.org/repos/asf/subversion/branches/1.14.x/STATUS">STATUS</a> file.</p>



Mime
View raw message