[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.10.0-alpha3 queued

From: Evgeny Kotkov <evgeny.kotkov_at_visualsvn.com>
Date: Wed, 26 Jul 2017 17:51:45 +0300

Daniel Shahaf <d.s_at_daniel.shahaf.name> writes:

> With my RM hat off, the text LGTM except that I think #fsfs-format8
> should be mentioned under the #compatibility heading or linked from it,
> since the behaviour of 'svnadmin create' (without --compatible-version)
> has changed even for people who are agnostic to the lz4/zlib choice.

Makes sense.

How about we mention this change in how 'svnadmin create' behaves,
and also duplicate the warning about the no-upgrade-path policy for

Index: publish/docs/release-notes/1.10.html
--- publish/docs/release-notes/1.10.html (revision 1803054)
+++ publish/docs/release-notes/1.10.html (working copy)
@@ -82,6 +82,14 @@ Subversion 1.10 servers can read and write to repo
 earlier versions. To upgrade an existing server installation, just install
 newest libraries and binaries on top of the older ones.</p>

+<p>Please note that <tt>svnadmin create</tt> will by default create
+repositories using the new filesystem format 8.
+Until Subversion 1.10 is generally available, <b>no upgrade path is
+promised</b> for repositories with this new filesystem format. Please do
+not use newly created repositories for any data meant for long-term
+safe-keeping. See our <a href="/prerelease-caveats">policy for
+pre-releases</a> for additional information.</p>
 <p>Subversion 1.10 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

Evgeny Kotkov
Received on 2017-07-26 16:52:16 CEST

This is an archived mail posted to the Subversion Dev mailing list.