tools/dist/sample-rc-warning-index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html>
   4 <head>
   5 <title>Subversion @VERSION@ tarballs</title>
   6 </head>
   7 <body style="font-size: 14pt; text-align: justify;
   8   background-color: #f0f0f0; padding: 0 5%">
   9 <h1 style="font-size: 30pt; text-align: center;
  10   text-decoration: underline">WARNING</h1>
  11
  12 <p>The code you are about to download is a <i>Release Candidate</i>
  13 for Subversion @VERSION@.</p>
  14
  15
  16 <p>A <i>Release Candidate</i> is exactly what it sounds like: a
  17 distribution of Subversion that may become an official release later,
  18 <i>if and only if</i> it passes preliminary testing by those members
  19 of the community who are interested in testing it.</p>
  20
  21 <!-- , which means it is considered <strong
  22  style="text-decoration: underline">UNRELEASED</strong> code.  The
  23  term 'release candidate' means the code works to the best knowledge
  24  of the Subversion developers, but that it still requires testing by a
  25  larger number of people to root out bugs.</p> -->
  26
  27 <p>As such, if you are interested in helping us test this Release
  28 Candidate, you're very welcome to download and test these packages.
  29 If you are looking for a copy of Subversion for production use, this
  30 is <i>not it</i>; you should instead grab the latest stable release
  31 from the <a
  32 href="http://subversion.tigris.org/project_packages.html">Download
  33 area</a>.</p>
  34
  35 <h2 style="font-size: 18pt">Note to operating system distro package
  36 maintainers</h2>
  37
  38 <p>As stated above, this is <i>not</i> an official, end-user release
  39 of Subversion.  It is a distribution intended for testing only. Please
  40 do <i>not</i> package this distribution in any way. It should not be
  41 made available to users who rely on their operating system distro's
  42 packages.</p>
  43
  44 <h2 style="font-size: 14pt">Why shouldn't I set up/make available a
  45 Release Candidate for production use?</h2>
  46
  47 <p style="font-size: 11pt">(Taken from a <a
  48   href="http://svn.haxx.se/dev/archive-2005-11/1295.shtml"
  49 >mail by Karl Fogel</a> on the subject)</p>
  50
  51 <p style="font-size: 11pt">Subversion release candidates are for
  52 testing only. We might have to withdraw one to fix bugs, and fixing
  53 those bugs might involve changing APIs, or changing a soft-upgrade
  54 strategy in the repository or working copy formats. If some production
  55 users had begun depending on the new API, or had unknowingly
  56 soft-upgraded their repository or working copy, then they'd be in for
  57 a very unpleasant suprise when the real release comes out and doesn't
  58 have the same API anymore, or doesn't use the same formats. Not only
  59 would Subversion suddenly "stop working" for them, but there wouldn't
  60 be any convenient path to get it working again, since no blessed
  61 Subversion release would have the code needed to interpret their
  62 legacy data.</p>
  63
  64 <p style="font-size: 11pt">We encourage RC testing by users who know
  65 how to install from a tarball independently of their OS's packaging
  66 system. Users who install only packaged releases, however, should wait
  67 for and use only officially released Subversions. Anything else is
  68 playing with fire. When the inevitable blowup happens, both your
  69 reputation as a packager and Subversion's reputation will suffer --
  70 but only one will deserve it.</p>
  71
  72 <p>If you want to help us test this distribution of Subversion, you
  73 can find the files <a href="@DIRNAME@/">here</a>.</p>
  74
  75 </body>
  76 </html>