You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by da...@apache.org on 2012/03/29 15:20:30 UTC
svn commit: r578 - /dev/subversion/README.html
Author: danielsh
Date: Thu Mar 29 13:20:28 2012
New Revision: 578
Log:
Add a README.html, based on the old RC Warning click-through page
at tools/dist/templates@1303762.
Added:
dev/subversion/README.html (with props)
Added: dev/subversion/README.html
==============================================================================
--- dev/subversion/README.html (added)
+++ dev/subversion/README.html Thu Mar 29 13:20:28 2012
@@ -0,0 +1,99 @@
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+-->
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>Apache Subversion Pre-releases</title>
+</head>
+<body style="font-size: 14pt; text-align: justify;
+ background-color: #f0f0f0; padding: 0 5%">
+<h1 style="font-size: 30pt; text-align: center;
+ text-decoration: underline">WARNING</h1>
+
+<p>The code you are about to download is a <i>Release Candidate</i>
+for Apache Subversion.</p>
+
+<p>A <i>Release Candidate</i> is exactly what it sounds like: a
+distribution of Subversion that may become an official release later,
+<i>if and only if</i> it passes preliminary testing by those members
+of the community who are interested in testing it.</p>
+
+<p>If you are looking for a copy of Subversion for production use, this
+is <i>not it</i>; you should instead grab the latest stable release
+from the <a
+href="http://subversion.apache.org/download/">Download area</a>.</p>
+
+<p>If you are interested in helping us test this Release
+Candidate, you're very welcome to download and test these packages, and
+<a href="http://subversion.apache.org/docs/community-guide/issues.html">report
+bugs</a> back to the developers; but please keep in mind that this is
+not a final release of Apache Subversion, so only use it on data
+you aren't afraid to lose.</p>
+
+<h2 style="font-size: 18pt">Note to operating system distro package
+maintainers</h2>
+
+<p>As stated above, this is <i>not</i> an official, end-user release
+of Subversion. It is a distribution intended for testing only, and is not
+suitable for production use. It has not been publicly announced.</p>
+
+<p>Packages with <tt>alpha</tt>, <tt>beta</tt>, or <tt>rc</tt> in their names
+will remain unsuitable for production use even they have been publicly
+announced; if you chose to package such a pre-release for your operating system
+distro's management system, you must do so in a way which clearly denotes that
+it is not a final release, and is only for testing purposes.</p>
+
+<p>And please don't package anything you see here before it has been <a
+href="http://mail-archives.apache.org/mod_mbox/subversion-announce/">publicly
+announced</a>.</p>
+
+<h2 style="font-size: 14pt">Why shouldn't I set up/make available a
+Release Candidate for production use?</h2>
+
+<p style="font-size: 11pt">(Taken from a <a
+ href="http://svn.haxx.se/dev/archive-2005-11/1295.shtml"
+>mail by Karl Fogel</a> on the subject)</p>
+
+<p style="font-size: 11pt">Subversion release candidates are for
+testing only. We might have to withdraw one to fix bugs, and fixing
+those bugs might involve changing APIs, or changing a soft-upgrade
+strategy in the repository or working copy formats. If some production
+users had begun depending on the new API, or had unknowingly
+soft-upgraded their repository or working copy, then they'd be in for
+a very unpleasant suprise when the real release comes out and doesn't
+have the same API anymore, or doesn't use the same formats. Not only
+would Subversion suddenly "stop working" for them, but there wouldn't
+be any convenient path to get it working again, since no blessed
+Subversion release would have the code needed to interpret their
+legacy data.</p>
+
+<p style="font-size: 11pt">We encourage RC testing by users who know
+how to install from a tarball independently of their OS's packaging
+system. Users who install only packaged releases, however, should wait
+for and use only officially released Subversions. Anything else is
+playing with fire. When the inevitable blowup happens, both your
+reputation as a packager and Subversion's reputation will suffer --
+but only one will deserve it.</p>
+
+<p>If you want to help us test this distribution of Subversion, you
+can find the files <a href=".">here</a>.</p>
Propchange: dev/subversion/README.html
------------------------------------------------------------------------------
svn:mime-type = text/html