svn commit: r1145454 - in /subversion/site/publish: .htaccess docs/community-guide/releasing.part.html

[da...@apache.org]

Author: danielsh
Date: Tue Jul 12 04:47:01 2011
New Revision: 1145454

URL: http://svn.apache.org/viewvc?rev=1145454&view=rev
Log:
Give #prerelease-caveats a more-permanent home.  (Follow-up
to r1145214 on /trunk.)

* docs/community-guide/releasing.html
  (#prerelease-caveats): New.

* .htaccess
  (/prerelease-caveats): Update pointer.

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

Modified: subversion/site/publish/.htaccess
URL: http://svn.apache.org/viewvc/subversion/site/publish/.htaccess?rev=1145454&r1=1145453&r2=1145454&view=diff
==============================================================================
--- subversion/site/publish/.htaccess (original)
+++ subversion/site/publish/.htaccess Tue Jul 12 04:47:01 2011
@@ -14,4 +14,4 @@ RedirectMatch ^/buildbot(.*) http://ci.a
 \&
 RedirectMatch ^/patches$ /docs/community-guide/general.html#patches
 RedirectMatch ^/HACKING$ /docs/community-guide/
-RedirectMatch ^/prerelease-caveats$ http://mail-archives.apache.org/mod_mbox/subversion-announce/201106.mbox/%3cBANLkTi=wNbZJ=A6Mev+m=4JQF+cHS2N3Xw@mail.gmail.com%3e
+RedirectMatch ^/prerelease-caveats$ /docs/community-guide/releasing.html#prerelease-caveats

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=1145454&r1=1145453&r2=1145454&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Jul 12 04:47:01 2011
@@ -157,6 +157,35 @@ href="http://subversion.tigris.org/servl
 
 </div> <!-- alphas-betas -->
 
+<div class="h4" id="prerelease-caveats">
+<h4>Breaking compatibility
+  <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#prerelease-caveats"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>Our compatibility rules (as detailed <a href="#release-compat">below</a>)
+only start to apply once a <em>final</em> x.y.0 version has been blessed and
+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>
+
+<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
+designated scripts for the legacy format&mdash;with the final release.  (Of
+course, we might provide such scripts for the benefit of developers and users
+who test our pre-releases; but we do not obligate ourselves to do so.)
+Consequently, pre-releases should <strong>never</strong> be trusted with any
+data meant for long-term safe-keeping.</p>
+
+<p>At the same time, we wish to remind the reader that the best time to point
+out API design bugs is before they are released and set in stone&mdash;in
+other words, during the initial design and pre-release stages.</p>
+
+</div> <!-- prerelease-caveats -->
+
 <div class="h4" id="name-reuse">
 <h4>Reuse of release names
   <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#name-reuse"