Author: stsp Date: Thu Oct 13 12:55:49 2011 New Revision: 1182819 URL: http://svn.apache.org/viewvc?rev=1182819&view=rev Log: * publish/docs/release-notes/1.7.html: Tweak wording to distinguish clearly between client- and server-side matters. Should prevent misunderstandings in case the reader believes that a "repository" and a "working copy" are the same thing (yes, this is quite common, I regularly witness this in the #svn IRC channel).
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=1182819&r1=1182818&r2=1182819&view=diff ============================================================================== --- subversion/site/publish/docs/release-notes/1.7.html (original) +++ subversion/site/publish/docs/release-notes/1.7.html Thu Oct 13 12:55:49 2011 @@ -69,17 +69,24 @@ also cases where a new feature will work 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 and write to repositories created by -earlier versions. To upgrade an existing installation, just install the +repositories. Subversion 1.7 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.7 uses the same repository formats as 1.6 does. Therefore, -it is possible to seamlessly upgrade and downgrade between 1.6.x and 1.7.x -without touching the on-disk repositories. (This is not correct in general -for any pair of 1.x and 1.y releases, but happens to hold for 1.6 and 1.7.) -If new-in-1.7 features were enabled (in the hooks or server configuration -files), they will, of course, have to be disabled prior to reverting to a -1.6 server.</p> +<p>Subversion 1.7 servers use the same repository format as Subversion 1.6. +Therefore, it is possible to seamlessly upgrade and downgrade between 1.6.x and 1.7.x +servers without changing the format of the on-disk repositories. +(This is not correct in general for any pair of 1.x and 1.y servers, +but happens to hold for 1.6 and 1.7.) +If new 1.7 features were enabled on the server (in the hooks or server +configuration files), they will, of course, have to be disabled prior +to reverting back to a 1.6 server.</p> + +<p>Subversion 1.7 clients use a new working copy format. +Subversion 1.7 clients cannot use Subversion 1.6 (and earlier) working copies. +Existing working copies created with Subversion 1.6 and earlier need to be +upgraded before they can be used with a Subversion 1.7 +client (see <a href="#wc-ng">below</a> for details).</p> <p>Subversion 1.7 maintains API/ABI compatibility with earlier releases, by only adding new functions, never removing old ones. A