Author: stefan2
Date: Sat Nov 23 18:07:02 2013
New Revision: 1544850
URL: http://svn.apache.org/r1544850
Log:
Add 1.9 release notes as a rip-off of the current 1.8
release notes and put many templates in with "###"
blind text markers.
* site/publish/docs/release-notes/1.9.html
(): new file
Added:
subversion/site/publish/docs/release-notes/1.9.html
Added: subversion/site/publish/docs/release-notes/1.9.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.9.html?rev=1544850&view=auto
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (added)
+++ subversion/site/publish/docs/release-notes/1.9.html Sat Nov 23 18:07:02 2013
@@ -0,0 +1,301 @@
+<!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.9 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.9 Release Notes</h1>
+
+<div class="h2" id="news">
+<h2>What's New in Apache Subversion 1.9
+ <a class="sectionlink" href="#news"
+ title="Link to this section">¶</a>
+</h2>
+
+<ul>
+ <li><a href="#dwim-feature"
+ >### Some new feature</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>Apache Subversion 1.9 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.7.x is also
+in 1.8, but 1.8 contains features and bugfixes not present in any
+earlier release. The new features will eventually be documented in a
+1.8 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.9 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.9
+servers and clients. However, some of the new 1.9 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.9/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin";
+>dump and reload</a> your repositories.
+Subversion 1.9 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.9 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.9 libraries. However, a program written for 1.9
+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.9/";
+>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="#dwim-feature">### some cool feature</a></td>
+ <td>1.9</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 -->
+
+<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><span style="color: red"><i>### <b>TODO</b> Keeping the original 1.8
+section as a template. Update to 1.9 where applicable.</i></span></p>
+
+<p>Subversion 1.8 introduces changes to the working copy format.
+In previous releases of Subversion (1.6 and earlier), Subversion would
+automatically upgrade the working copy to the new format when a write
+operation was performed. Subversion 1.8, however, requires an upgrade for
+both read and write operations on the working copy, and makes the upgrade
+a manual step.</p>
+
+<p>Before using Subversion 1.8 with existing working copies, 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, and for some users,
+it may be more practical to simply checkout a new working copy.</p>
+
+<p>Subversion 1.8 can only upgrade working copies created with Subversion 1.6
+and Subversion 1.7.</p>
+
+<p><strong>Note:</strong> Subversion 1.8 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, a 1.6
+client must be used to run <tt>svn cleanup</tt> on all 1.6 working copies that
+require cleanup. Likewise, Subversion 1.8 cannot upgrade corrupt 1.6 working
+copies. Unfixable problems can arise from missing or corrupt meta-data inside
+<tt>.svn</tt> directories. Such damage to the 1.6 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="output-changes">
+<h3>Command Line Output Changes
+ <a class="sectionlink" href="#output-changes"
+ title="Link to this section">¶</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 <tt>--xml</tt> 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 <tt>svn foo</tt>
+ <a class="sectionlink" href="#foo"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>The output of <tt>svn foo</tt> has been improved. The following
+example illustrates these changes.</p>
+
+<pre>
+ $ svn foo
+ BAR
+ BAZ
+ BLAH
+ BIN
+ $
+</pre>
+
+</div>
+-->
+
+<div class="h4" id="annoying-formatting">
+<h4>### Annoying formatting
+ <a class="sectionlink" href="#annoying-formatting"
+ title="Link to this section">¶</a>
+</h4>
+
+<p><span style="color: red"><i>### All output is now centred.</i></span></p>
+
+</div> <!-- annoying-formatting -->
+
+</div> <!-- output-changes -->
+
+<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="auto-ignore-mishaps">
+<h4>### Auto-ignore configuration mishaps
+ <a class="sectionlink" href="#auto-ignore-mishaps"
+ title="Link to this section">¶</a>
+</h4>
+
+<p><span style="color: red"><i>### Check your server configuration
+for erroneous settings lest they will be ignored.</i></span></p>
+
+</div> <!-- auto-ignore-mistakes -->
+
+</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="dwim-feature">
+<h3>### DWIM option
+ <a class="sectionlink" href="#dwim-option"
+ title="Link to this section">¶</a>
+</h3>
+
+<p><span style="color: red"><i>### Command line now supports the
+Do What I Mean (TM) flag.</i></span></p>
+
+</div> <!-- dwim-option -->
+
+</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="new-lorem-ispum">
+<h3>### Introducing blind text
+ <a class="sectionlink" href="#new-lorem-ispum"
+ title="Link to this section">¶</a>
+</h3>
+
+<p><span style="color: red"><i>### Change this to non-random
text.</i></span></p>
+
+</div> <!-- new-lorem-ispum -->
+
+</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.9 releases. These
+may be fixed in later 1.9.x releases.</p>
+
+<div class="h3" id="1234-bad-stuff">
+<h3>### Stuff is broken
+ <a class="sectionlink" href="#1234-bad-stuff"
+ title="Link to this section">¶</a>
+</h3>
+
+<p><span style="color: red"><i>### SVN 1.9.0 has broken code in
it.</i></span></p>
+
+</div> <!-- 1234-bad-stuff -->
+
+</div> <!-- issues -->
+
+<div class="h2" id="svn-1.7-deprecation">
+<h2>Subversion 1.7.x series no longer supported
+ <a class="sectionlink" href="#svn-1.7-deprecation"
+ title="Link to this section">¶</a>
+</h2>
+
+<p>The Subversion 1.7.x line is no longer supported. This doesn't
+mean that your 1.7 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.7.x versions, and will not make any
+more 1.7.x bugfix releases.</p>
+
+</div> <!-- svn-1.7-deprecation -->
+
+<!-- ***************** END CONTENT ****************** -->
+</div> <!-- #site-content -->
+</body>
+</html>
