Author: julianfoad
Date: Mon Dec 10 16:18:32 2018
New Revision: 1848600
URL: http://svn.apache.org/viewvc?rev=1848600&view=rev
Log:
* publish/docs/release-notes/1.12.html: New.
* publish/docs/release-notes/index.html: Add a placeholder entry for 1.12.
Added:
subversion/site/publish/docs/release-notes/1.12.html (with props)
Modified:
subversion/site/publish/docs/release-notes/index.html
Added: subversion/site/publish/docs/release-notes/1.12.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.12.html?rev=1848600&view=auto
==============================================================================
--- subversion/site/publish/docs/release-notes/1.12.html (added)
+++ subversion/site/publish/docs/release-notes/1.12.html Mon Dec 10 16:18:32
2018
@@ -0,0 +1,400 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml";>
+<head>
+<title>Apache Subversion 1.12 Release Notes</title>
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+<style type="text/css">
+ @import url("/style/site.css");
+</style>
+</head>
+
+<body>
+<!--#include virtual="/site-banner.html" -->
+<!--#include virtual="/site-nav.html" -->
+<div id="site-content">
+<!--#include virtual="/site-notice.html" -->
+<!-- **************** BEGIN CONTENT ***************** -->
+
+<!-- ************************************************ -->
+<!-- Sections start with "###" are either templates -->
+<!-- or TODOs. Remove them before release. -->
+<!-- ************************************************ -->
+
+<h1 style="text-align: center">Apache Subversion 1.12 Release Notes</h1>
+
+<div class="notice">
+<p><span style="color: red"><b>This is work in progress.
+ Subversion 1.12 has not been released yet.</b></span></p>
+</div>
+
+<div class="notice">
+<p>Subversion 1.12 is a 6-month regular release. See
+<a href="#non-lts-release">Subversion 1.12 is a Regular Release</a>
+below.</p>
+</div>
+
+<div class="h2" id="news">
+<h2>What's New in Apache Subversion 1.12
+ <a class="sectionlink" href="#news"
+ title="Link to this section">¶</a>
+</h2>
+
+<ul>
+ <li><a href="#shelving"
+ >Improved Shelving (experimental)</a></li>
+ <li><a href="#checkpointing"
+ >Improved Commit Checkpointing (experimental)</a></li>
+ <li><a href="#conflict-resolver"
+ >Improvements to the Conflict Resolver</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.12 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.11.x is also
+in 1.12, but 1.12 contains features and bugfixes not present in any
+earlier release. The new features will eventually be documented in a
+1.12 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.12 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">¶</a>
+</h2>
+
+<p>Older clients and servers interoperate transparently with 1.12
+servers and clients. However, some of the new 1.12 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.12 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.12 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.12 libraries. However, a program written for 1.12
+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.12/";
+>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">¶</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>
+ <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—see
+ <a href="1.11#shelving-transition">the 1.11 transition
notes</a></td></tr>
+ <tr>
+ <td>
+ <a href="#checkpointing">Commit checkpointing (experimental)</a>
+ </td>
+ <td>1.12</td>
+ <td>any</td>
+ <td>any</td>
+ <td></td></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">¶</a>
+</h3>
+
+<p>Subversion 1.12 uses the same working copy format as Subversion 1.8 through
1.11.</p>
+
+<p>Before using Subversion 1.12 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.12 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.12 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 -->
+
+<!--
+<div class="h3" id="compat-misc">
+<h3>Miscellaneous Compatibility Notes
+ <a class="sectionlink" href="#compat-misc"
+ title="Link to this section">¶</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">¶</a>
+</h2>
+
+</div> <!-- new-features -->
+
+<div class="h2" id="enhancements">
+<h2>Enhancements and Bugfixes
+ <a class="sectionlink" href="#enhancements"
+ title="Link to this section">¶</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">¶</a>
+</h3>
+
+<div class="h4 experimental-feature" id="shelving">
+<h4>Improved Shelving (experimental)
+ <a class="sectionlink" href="#shelving"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>Shelving (<a
+href="https://issues.apache.org/jira/browse/SVN-3625";>issue #3625</a>),
+first introduced in Subversion 1.10, is improved in 1.12 to
+handle more kinds of changes more robustly.</p>
+
+<div class="notice">
+ <p><span style="color: red"><b>WARNING:</b></span> This feature is
+ designated "EXPERIMENTAL" in 1.12. It is being released in an early form
+ while development continues. It is expected to change significantly during
+ and after the 1.12.x series. There is no promise of backward compatibility
+ while it remains experimental.</p>
+</div>
+
+<!-- ... -->
+
+</div> <!-- shelving -->
+
+<div class="h4 experimental-feature" id="checkpointing">
+<h4>Commit checkpointing (experimental)
+ <a class="sectionlink" href="#checkpointing"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>Commit checkpointing (<a
+href="https://issues.apache.org/jira/browse/SVN-3626";>issue #3626</a>),
+first introduced in Subversion 1.11, is improved in 1.12 to
+handle more kinds of changes more robustly.</p>
+
+<div class="notice">
+ <p><span style="color: red"><b>WARNING:</b></span> This feature is
+ designated "EXPERIMENTAL" in 1.12. It is being released in an early form
+ while development continues. It is expected to change significantly during
+ and after the 1.12.x series. There is no promise of backward compatibility
+ while it remains experimental.</p>
+</div>
+
+<!-- ... -->
+
+</div> <!-- checkpointing -->
+
+<div class="h4" id="conflict-resolver">
+<h4>Improvements to the interactive conflict resolver
+ <a class="sectionlink" href="#conflict-resolver"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>The interactive conflict resolver now supports more conflict situations.
+</p>
+
+<!-- ... -->
+
+<p>Fixes for conflict resolver bugs found during the development of
+Subversion 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> <!-- cmdline -->
+
+<div class="h3" id="server-side-improvements">
+<h3>Server-side improvements
+ <a class="sectionlink" href="#server-side-improvements"
+ title="Link to this section">¶</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">¶</a>
+</h3>
+
+</div> <!-- client-server-improvements -->
+
+<div class="h3" id="apis">
+<h3>API changes, improvements and language bindings
+ (<em>client and server</em>)
+ <a class="sectionlink" href="#apis"
+ title="Link to this section">¶</a>
+</h3>
+
+</div> <!-- apis -->
+
+</div> <!-- enhancements -->
+
+<div class="h2" id="issues">
+<h2>Known issues in the release
+ <a class="sectionlink" href="#issues"
+ title="Link to this section">¶</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.12 releases. These
+may be fixed in later 1.12.x releases.</p>
+
+<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">¶</a>
+</h3>
+
+<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 class="h3" id="github-issue">
+<h3>Github's SVN Bridge server implementation incompatible with SVN 1.12
+ <a class="sectionlink" href="#github-issue"
+ title="Link to this section">¶</a>
+</h3>
+
+<p>As of November 2018, Subversion 1.12 clients are unable to
+check out repositories from Github. Stricter DAV RFC conformance checks
+were added to SVN 1.12 clients, and Github's custom SVN server implementation
+happens to not conform to the newly expected behaviour. We are waiting for
+Github to resolve the issue at their end. In the meantime, Subversion 1.10, and
+perhaps even the <a href="https://git-scm.com";>Git version control system</a>,
+can be used as a workaround.
+</p>
+
+
+</div> <!-- github-issue -->
+
+</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">¶</a>
+</h2>
+
+<p>Subversion 1.12 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.12 is a Regular Release
+ <a class="sectionlink" href="#non-lts-release"
+ title="Link to this section">¶</a>
+</h2>
+
+<p>Subversion 1.12 is one of the new 6-month regular releases with an
+emphasis on introducing new features more quickly and a shorter support
+period. It will be supported for 6 months, and then will be superseded by
+the next regular release.</p>
+
+<p>Subversion 1.11, the previous regular release, is no longer supported.</p>
+
+<p>Subversion 1.9 and 1.10 are still supported, now being regarded as
+long-term support (LTS) releases. The next LTS release is expected to be
+numbered 1.14, to be released two years after 1.10.</p>
+
+<p>For further details see
+<a href="/roadmap.html#release-planning">How We Plan Releases</a>.</p>
+
+</div> <!-- non-lts-release -->
+
+<!-- ***************** END CONTENT ****************** -->
+</div> <!-- #site-content -->
+</body>
+</html>
Propchange: subversion/site/publish/docs/release-notes/1.12.html
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: subversion/site/publish/docs/release-notes/1.12.html
------------------------------------------------------------------------------
svn:mime-type = text/html
Modified: subversion/site/publish/docs/release-notes/index.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/index.html?rev=1848600&r1=1848599&r2=1848600&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/index.html (original)
+++ subversion/site/publish/docs/release-notes/index.html Mon Dec 10 16:18:32
2018
@@ -47,6 +47,7 @@ official support status for the various
<p>Here are the release notes for the major Subversion releases:</p>
<ul>
+<li><a href="1.12.html">Subversion 1.12</a> â <i>in progress</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>
<li><a href="1.10.html">Subversion 1.10</a> â Improved path-based authz, new
interactive conflict resolver, LZ4 compression, FSFS format 8, shelving
(<i>first released â April 12, 2018</i>)</li>
<li><a href="1.9.html">Subversion 1.9</a> â FSFS format 7, FSX (<i>first
released â August 5, 2015</i>)</li>
