subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From danie...@apache.org
Subject svn commit: r1803073 - /subversion/site/publish/docs/community-guide/releasing.part.html
Date Wed, 26 Jul 2017 16:43:16 GMT
Author: danielsh
Date: Wed Jul 26 16:43:16 2017
New Revision: 1803073

URL: http://svn.apache.org/viewvc?rev=1803073&view=rev
Log:
* docs/community-guide/releasing.part.html
  (#prerelease-caveats): Explain the FSFS f5 example better.

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1803073&r1=1803072&r2=1803073&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Wed Jul 26 16:43:16 2017
@@ -172,9 +172,8 @@ only start to apply once a <em>final</em
 released.  Any API's, wire protocols, and on-disk formats that appeared on
 trunk or in an alpha/beta/rc pre-release are not subject to <em>any</em>
 compatibility promises; we may change them arbitrarily until the final
-release, if we find a good reason to do so.  (Often, a last-minute design wart
-is discovered shortly before the compatibility barrier is crossed, and we
-hurry to fix it before it's set in stone.)</p>
+release, if we find a good reason to do so.  We might even remove entirely
+an interface or serialization format that we are not comfortable with.</p>
 
 <p>This is particularly a problem for persistent data (working copies and
 repositories), since we might not provide an upgrade path&mdash;code paths or



Mime
View raw message