You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by hw...@apache.org on 2010/12/07 18:02:42 UTC

svn commit: r1043128 - /subversion/site/publish/docs/release-notes/1.7.html

Author: hwright
Date: Tue Dec  7 17:02:41 2010
New Revision: 1043128

URL: http://svn.apache.org/viewvc?rev=1043128&view=rev
Log:
Prime the pump by adding some skeleton 1.7 release notes.  These are going to
take a while to write--no use in putting it off to the last minute!
 
 * publish/docs/release-notes/1.7.html:
   New.

Added:
    subversion/site/publish/docs/release-notes/1.7.html   (with props)

Added: subversion/site/publish/docs/release-notes/1.7.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.7.html?rev=1043128&view=auto
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (added)
+++ subversion/site/publish/docs/release-notes/1.7.html Tue Dec  7 17:02:41 2010
@@ -0,0 +1,263 @@
+<!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.7 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 ***************** -->
+
+<div class="warningmessage">
+<p><strong>Note:</strong> Subversion 1.7 is <em>not released yet</em>.
+When it is released, this warning message will disappear, and the rest
+of this page will become the release notes.  Until then, this page
+describes what is planned for the release.</p>
+</div>
+
+<h1 style="text-align: center">Apache Subversion 1.7 Release Notes</h1>
+
+<div class="h2" id="news">
+<h2>What's New in Apache Subversion 1.7
+  <a class="sectionlink" href="#news"
+    title="Link to this section">&para;</a>
+</h2>
+
+<ul>
+  <li><a href="#wc-ng"
+      >Working Copy Metadata Storage Improvements</a></li>
+  <li><a href="#cmdline"
+      >Command-line client improvements</a></li>
+  <li><a href="#apis"
+      >API changes, improvements, and much language bindings work</a></li>
+  <li><a href="#bug-fixes"
+      >More than XX new bug fixes, enhancements</a></li>
+</ul>
+
+<p>Apache Subversion 1.7 is a superset of all previous Subversion releases,
+and is considered the current "best" release.  Any feature or bugfix
+in 1.0.x through 1.6.x is also in 1.7, but 1.7 contains features and
+bugfixes not present in any earlier release.  The new features will
+eventually be documented in a 1.7 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.7 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">&para;</a>
+</h2>
+
+<p>Older clients and servers interoperate transparently with 1.7
+servers and clients.  However, some of the new 1.7 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 dump and reload your
+repositories.  Subversion 1.7 can read repositories created by earlier
+versions.  To upgrade an existing installation, just install the
+newest libraries and binaries on top of the older ones.</p>
+
+<p>Subversion 1.7 maintains API/ABI compatibility with earlier
+releases, by only adding new functions, never removing old ones.  A
+program written to the 1.0, 1.1, 1.2, 1.3, 1.4, 1.5 or 1.6 API can both compile
+and run using 1.7 libraries.  However, a program written for 1.7
+cannot necessarily compile or run against older libraries.</p>
+
+<p>There may be limited cases where the behavior of old APIs may have 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.7/">
+API errata</a> for more detailed information on what these APIs are and what
+impact these changes may have.  For Subversion 1.7, these errata are limited to
+<code>libsvn_wc</code>.</p>
+
+<div class="h3" id="new-feature-compatibility-table">
+<h3>New Feature Compatibility Table
+  <a class="sectionlink" href="#new-feature-compatibility-table"
+    title="Link to this section">&para;</a>
+</h3>
+<table border="1">
+  <tr>
+    <th>New Feature</th>
+    <th>Minimum Client<sup>1</sup></th>
+    <th>Minimum Server</th>
+    <th>Minimum Repository</th>
+    <th>Notes</th></tr>
+  <tr>
+    <td><a href="#httpv2">HTTPv2</a></td>
+    <td>1.7</td>
+    <td>1.7</td>
+    <td>any</td>
+    <td>Permutations of older client/server combinations will continue to
+      function at the pre-1.7 feature level.</td></tr>
+  <tr>
+    <td><a href="#wc-ng">WC-NG</a></td>
+    <td>1.7</td>
+    <td>any</td>
+    <td>any</td>
+    <td></td></tr>
+   <tr>
+     <td colspan="5"><sup>1</sup>Reminder: when using the <code>file://</code>
+       repository access method, the Subversion program is both the client
+       <em>and</em> the server.</td></tr>
+</table>
+
+</div>  <!-- new-feature-compatibility-table -->
+
+<div class="h3" id="output-changes">
+<h3>Command Line Output Changes
+  <a class="sectionlink" href="#output-changes"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>Although we try hard to keep output from the command line programs
+compatible between releases, new information sometimes has to be
+added.  This can break scripts that rely on the exact format of the
+output.  For this reason, we encourage programs which consume the output
+of the commandline client to consider using the <code>--xml</code> option,
+or accessing Subversion through the various bindings interfaces.</p>
+
+<!-- Insert items here, of the following form:
+<div class="h4" id="foo">
+<h4>Improved output of <code>svn foo</code>
+  <a class="sectionlink" href="#foo"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>The output of <code>svn foo</code> has been improved.  The following
+example illustrates these changes.</p>
+
+<pre>
+   $ svn foo
+   BAR
+   BAZ
+   BLAH
+   BIN
+   $ 
+</pre>
+
+</div>
+-->
+
+</div>  <!-- output-changes -->
+
+</div>  <!-- compatibility -->
+
+<div class="h2" id="new-features">
+<h2>New Features
+  <a class="sectionlink" href="#new-features"
+    title="Link to this section">&para;</a>
+</h2>
+
+<div class="h3" id="wc-ng">
+<h3>Working Copy Metadata Storage Improvements (<em>client</em>)
+  <a class="sectionlink" href="#auth-related-improvements"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>Wherein we describe all the magic behind wc-ng.</p>
+
+</div>  <!-- wc-ng -->
+
+</div>  <!-- new-features -->
+
+<div class="h2" id="enhancements">
+<h2>Enhancements and Bugfixes
+  <a class="sectionlink" href="#enhancements"
+    title="Link to this section">&para;</a>
+</h2>
+
+<!-- Don't need to highlight every bugfix, just major ones which aren't in
+     any patch release. -->
+
+<div class="h3" id="cmdline">
+<h3>Command-line client improvements (<em>client</em>)
+  <a class="sectionlink" href="#cmdline"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>There are far too many enhancements and new options to the
+command-line client to list them all here.  Aside from all the ones
+mentioned already in these release notes, below are a few more that we
+consider important, but please see the 1.7.0 section in the <a
+href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES">CHANGES</a> file
+for a complete list.</p>
+
+<!-- Insert selected items here -->
+
+</div>  <!-- cmdline -->
+
+<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">&para;</a>
+</h3>
+
+<p>There are too many new and revised APIs in Subversion 1.7.0 to list
+them all here.  See the <a
+href="http://subversion.apache.org/docs/api/1.7/" >Subversion API
+Documentation</a> page for general API information.  If you develop a
+3rd-party client application that uses Subversion APIs, you should
+probably look at the header files for the interfaces you use and see
+what's changed.</p>
+
+<p>One general change is that most APIs that formerly took a
+<tt>recurse</tt> parameter have been upgraded to accept a
+<tt>depth</tt> parameter instead, to enable the new <a
+href="#sparse-checkouts">sparse checkouts</a> feature.</p>
+
+<p>Language bindings have mostly been updated for the new APIs, though
+some may lag more than others.</p>
+
+</div>  <!-- apis -->
+
+<div class="h3" id="bug-fixes">
+<h3>Bug fixes (<em>client and server</em>)
+  <a class="sectionlink" href="#bug-fixes"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>A great many bugs have been fixed.  See the 1.7.0 section in the <a
+href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES">CHANGES</a> file
+for details.</p>
+
+</div>  <!-- bug-fixes -->
+
+</div>  <!-- enhancements -->
+
+<div class="h2" id="svn-1.5-deprecation">
+<h2>Subversion 1.5.x series no longer supported
+  <a class="sectionlink" href="#svn-1.5-deprecation"
+    title="Link to this section">&para;</a>
+</h2>
+
+<p>The Subversion 1.5.x line is no longer supported.  This doesn't
+mean that your 1.5 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.5.x versions, and will not make any
+more 1.5.x bugfix releases.</p>
+
+</div>  <!-- svn-1.5-deprecation -->
+
+<!-- ***************** END CONTENT ****************** -->
+</div> <!-- #site-content -->
+</body>
+</html>

Propchange: subversion/site/publish/docs/release-notes/1.7.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: subversion/site/publish/docs/release-notes/1.7.html
------------------------------------------------------------------------------
    svn:executable = *