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

[da...@apache.org]

Author: danielsh
Date: Wed Aug 24 13:48:29 2011
New Revision: 1161100

URL: http://svn.apache.org/viewvc?rev=1161100&view=rev
Log:
* docs/release-notes/1.7.html
  (wc-upgrade): Document the limitations of upgrading working copies of prior releases;
    namely, 1.7 cannot run loggy.

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

Modified: 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=1161100&r1=1161099&r2=1161100&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Wed Aug 24 13:48:29 2011
@@ -479,6 +479,15 @@ to run a new command, <tt>svn upgrade</t
 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><strong>Note:</strong> Subversion 1.7 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.7, a 1.6
+client must be used to run <tt>svn cleanup</tt> on all working copies that
+require cleanup.  We regret for this limitation, but we had to introduce it in
+order for 1.7 to ship timely and without overcomplicating the internals.</p>
+
+<!-- 'sed -ne 5p < .svn/entries' to print `svn info | grep URL` of a 1.4-1.6 working copy. -->
+
 </div>  <!-- wc-upgrade -->
 
 </div>  <!-- wc-ng -->