You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by da...@apache.org on 2016/05/01 18:44:35 UTC
svn commit: r1741872 - /subversion/site/publish/docs/release-notes/1.10.html
Author: danielsh
Date: Sun May 1 16:44:34 2016
New Revision: 1741872
URL: http://svn.apache.org/viewvc?rev=1741872&view=rev
Log:
docs/release-notes/1.10.html: New, skeleton filled with placeholders.
Added:
subversion/site/publish/docs/release-notes/1.10.html
Added: subversion/site/publish/docs/release-notes/1.10.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.10.html?rev=1741872&view=auto
==============================================================================
--- subversion/site/publish/docs/release-notes/1.10.html (added)
+++ subversion/site/publish/docs/release-notes/1.10.html Sun May 1 16:44:34 2016
@@ -0,0 +1,344 @@
+<!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.10 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.10 Release Notes</h1>
+
+<div class="h2" id="news">
+<h2>What's New in Apache Subversion 1.10
+ <a class="sectionlink" href="#news"
+ title="Link to this section">¶</a>
+</h2>
+
+<ul>
+ <li><a href="#fsfs-improvements"
+ >FSFS improvements</a></li>
+ <li><a href="#fsx"
+ >FSX – A new experimental repository backend</a></li>
+ <li><a href="#enhancements"
+ >Many enhancements and bug fixes</a></li>
+ <li><a href="#issues"
+ >Known issues in the release</a></li>
+</ul>
+
+<p class="todo">TODO: remove 1.9 entries, left throughout this file as placeholders</p>
+
+<p>Apache Subversion 1.10 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.9.x is also
+in 1.10, but 1.10 contains features and bugfixes not present in any
+earlier release. The new features will eventually be documented in a
+1.10 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.10 section of the <a
+href="http://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.10
+servers and clients. However, some of the new 1.10 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.10 servers can read and write to repositories created by
+earlier versions. To upgrade an existing server installation, just install the
+newest libraries and binaries on top of the older ones.</p>
+
+<p>Subversion 1.10 maintains API/ABI compatibility with earlier
+releases, by only adding new functions, never removing old ones. A
+program written to any previous 1.x API can both compile
+and run using 1.10 libraries. However, a program written for 1.10
+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="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.10/"
+>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="#self-writing-release-notes">Self-writing release notes</a></td>
+ <td>1.10</td>
+ <td>1.9</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.10 uses the same working copy format as Subversion 1.8 and 1.9.</p>
+
+<p>Before using Subversion 1.10 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.10 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.10 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 class="h4" id="next-release-is-1.10">
+<h4>Next release will be numbered 1.10
+ <a class="sectionlink" href="#next-release-is-1.10"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>The next minor release after 1.9.0 will be numbered 1.10.0.</p>
+
+</div> <!-- next-release-is-1.10 -->
+
+</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 class="h3" id="fsfs-improvements">
+<h3>FSFS improvements
+ <a class="sectionlink" href="#fsfs-improvements"
+ title="Link to this section">¶</a>
+</h3>
+
+<div class="h4" id="fsfs-format7">
+<h4>Format bump
+ <a class="sectionlink" href="#fsfs-format7"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>The default filesystem format is now a new format, numbered 7.
+(The new command <a href="#svnadmin-info" title="svnadmin info">
+<tt>svnadmin info</tt></a> displays the filesystem format number
+of a repository.)
+In contrast to previous
+releases, format 7 is a major overhaul with the general goal of I/O reduction.
+Major changes include:
+</p>
+
+</div> <!-- fsfs-format7 -->
+
+</div> <!-- fsfs-improvements -->
+
+</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" id="svn-auth">
+<h4>New sub-command <tt>svn auth</tt>
+ <a class="sectionlink" href="#svn-auth"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>The new <tt>svn auth</tt> sub-command can be used to view or remove
+authentication credentials saved in any of the supported password caches.
+Authentication credentials include usernames, passwords,
+SSL certificates, and SSL client-certificate passphrases.</p>
+
+</div> <!-- svn-auth -->
+
+</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 class="h4" id="fewer-ood-conditions">
+<h4>Committing the result of large merges
+ <a class="sectionlink" href="#fewer-ood-conditions"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>Our best practices suggest that projects should branch and merge
+at the project root level. Each merge will then usually change the
+<tt>svn:mergeinfo</tt> property at the project base folder. To commit
+that change, pre-1.9 servers require the client to have the latest
+version of that base folder. Whenever there is a commit in that tree,
+its base folder will get a new revision as well, though. Thus, in
+large, busy projects, it is likely that by the time a large merge commit
+would actually have reached its finalization phase, some other commit
+got through and the merge commit is rejected for being out of date.
+</p>
+
+</div> <!-- fewer-ood-conditions -->
+
+</div> <!-- server-side-improvements -->
+
+<div class="h3" id="svnadmin-improvements">
+<h3><tt>svnadmin</tt> changes and improvements
+ <a class="sectionlink" href="#svnadmin-improvements"
+ title="Link to this section">¶</a>
+</h3>
+
+<div class="h4" id="svnadmin-info">
+<h4>New sub-command <tt>svnadmin info</tt>
+ <a class="sectionlink" href="#svnadmin-info"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>This prints detailed format information for the given repository.
+</p>
+
+<pre>
+ $ svnadmin info /repos/apache/
+ Path: /repos/apache
+ UUID: ac336b0e-000b-11e0-b354-23d019ddd9ed
+ Repository Format: 5
+ Compatible With Version: 1.8.0
+ Repository Capability: mergeinfo
+ Filesystem Type: fsfs
+ Filesystem Format: 6
+ FSFS Sharded: yes
+ FSFS Shard Size: 1000
+ FSFS Shards Packed: 1631/1631
+ FSFS Logical Addressing: no
+ Configuration File: /repos/apache/db/fsfs.conf
+</pre>
+
+</div> <!-- svnadmin-info -->
+
+</div> <!-- svnadmin-improvements -->
+
+</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 some known issues in the Subversion 1.10 releases. These
+may be fixed in later 1.10.x releases.</p>
+
+<div class="h3" id="no-op-changes">
+<h3>No-op changes no longer dumped by '<tt>svnadmin dump</tt>'
+ <a class="sectionlink" href="#no-op-changes"
+ title="Link to this section">¶</a>
+</h3>
+
+<p>See <a href="https://issues.apache.org/jira/browse/SVN-4598">issue #4598 "No-op changes no longer dumped by 'svnadmin dump' in 1.9"</a>.
+</p>
+
+<p>It has always been possible, in atypical cases, for a commit to mark a
+file as 'changed' without actually changing the file's text and/or
+properties to a different value. Starting from 1.9.0, <tt>svnadmin dump</tt>
+still outputs a record for such a file, including a header saying that the
+action is 'change', but no longer appends a block describing the new text
+for the file. (And similarly for properties, perhaps? TBD.) When
+<tt>svnadmin load</tt> (1.8 or 1.9) reads this dumpfile, it does not record
+any change in the repository for such a file.
+</p>
+
+</div> <!-- no-op-changes -->
+
+</div> <!-- issues -->
+
+<div class="h2" id="svn-1.8-deprecation">
+<h2>Subversion 1.8.x series no longer supported
+ <a class="sectionlink" href="#svn-1.8-deprecation"
+ title="Link to this section">¶</a>
+</h2>
+
+<p>The Subversion 1.8.x line is no longer supported. This doesn't
+mean that your 1.8 installation is doomed; if it works well and is all
+you need, that's fine. "No longer supported" just means we've stopped
+accepting bug reports against 1.8.x versions, and will not make any
+more 1.8.x bugfix releases.</p>
+
+</div> <!-- svn-1.8-deprecation -->
+
+<!-- ***************** END CONTENT ****************** -->
+</div> <!-- #site-content -->
+</body>
+</html>