svn commit: r1434737 - /subversion/site/publish/docs/release-notes/1.8.html

[st...@apache.org]

Author: stsp
Date: Thu Jan 17 15:44:31 2013
New Revision: 1434737

URL: http://svn.apache.org/viewvc?rev=1434737&view=rev
Log:
* site/docs/release-notes/1.8.html: Add a section about working copy upgrades.

Modified:
    subversion/site/publish/docs/release-notes/1.8.html

Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1434737&r1=1434736&r2=1434737&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Thu Jan 17 15:44:31 2013
@@ -161,6 +161,40 @@ and what impact these changes may have.<
 
 </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">&para;</a>
+</h3>
+
+<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"