subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@apache.org
Subject svn commit: r1693116 - /subversion/site/publish/docs/release-notes/1.9.html
Date Tue, 28 Jul 2015 15:31:37 GMT
Author: stefan2
Date: Tue Jul 28 15:31:36 2015
New Revision: 1693116

URL: http://svn.apache.org/r1693116
Log:
Address a TODO in the 1.9 release notes.

* publish/docs/release-notes/1.9.html
  (wc-upgrade): No w/c upgrade required from 1.8 to 1.9.
                Uogrades from older formats are the same as in 1.8.

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

Modified: 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=1693116&r1=1693115&r2=1693116&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Tue Jul 28 15:31:36 2015
@@ -131,29 +131,22 @@ and what impact these changes may have.<
     title="Link to this section">&para;</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.9 uses the same working copy format as Subversion 1.8.</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.9 with existing an 1.6 or 1.7 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, and
+for some users, it may be more practical to simply checkout a new working
+copy.</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
+<p>Subversion 1.9 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
+<p><strong>Note:</strong> Subversion 1.9 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
+was run (with a 1.6 client).  In other words, before upgrading to 1.9, 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
+require cleanup.  Likewise, Subversion 1.9 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>



Mime
View raw message