subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf <...@daniel.shahaf.name>
Subject Re: 1.10.0-alpha3 queued
Date Wed, 26 Jul 2017 15:02:30 GMT
Evgeny Kotkov wrote on Wed, 26 Jul 2017 17:51 +0300:
> How about we mention this change in how 'svnadmin create' behaves,
> and also duplicate the warning about the no-upgrade-path policy for
> pre-releases?
> 
> +++ 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 <a href="#fsfs-format8">filesystem format 8</a>.
> +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

The text LGTM and it fits well in the flow.  I might've used a box for it,
but I suppose the <b/> tag does the job just as well.  (The thinking being
to make the warning stand out for users who skip the #compatibility
section, which hasn't changed in years.)

Thanks!

Mime
View raw message