Further strengthen the wording of Nik's revisions for -stable, making it

very clear that this is _not_ a branch for end-users, it is for developers.
This commit is contained in:
Jordan K. Hubbard 2001-07-23 08:27:37 +00:00
parent 0546620270
commit 125ae35cfc
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10007

View file

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.76 2001/07/17 23:33:26 chern Exp $ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.77 2001/07/19 23:18:06 chern Exp $
--> -->
<chapter id="cutting-edge"> <chapter id="cutting-edge">
@ -264,26 +264,31 @@ subscribe cvs-all</programlisting>
<title>What is &os.stable;?</title> <title>What is &os.stable;?</title>
<indexterm><primary>-STABLE</primary></indexterm> <indexterm><primary>-STABLE</primary></indexterm>
<para>&os.stable; is our development branch for a more low-key <para>&os.stable; is our development branch from which major releases
and conservative set of changes intended for our next mainstream are made. Changes go into this branch at a different pace, and
release. Any changes to this branch will have debuted in with the general assumption that they've first gone into
&os.current; first, helping to reduce (but not eliminate) the chance &os.current; first for testing. This is <emphasis>still</emphasis>
that the changes will cause problems.</para> a development branch, however, and this means that at any given time,
the sources for &os.stable; may or may not be suitable for any
particular purpose. It is simply another engineering development
track, not a resource for end-users.</para>
</sect3> </sect3>
<sect3> <sect3>
<title>Who needs &os.stable;?</title> <title>Who needs &os.stable;?</title>
<para>If you are interested in tracking the FreeBSD development <para>If you are interested in tracking or contributing to the
process, and you want early access to the features that will appear FreeBSD development process, especially as it relates to the
in the next <quote>point</quote> release of FreeBSD then you should next <quote>point</quote> release of FreeBSD, then you should
consider following &os.stable;.</para> consider following &os.stable;.</para>
<para>Tracking &os.stable; also gives you easy access to security <para>While it is true that security fixes also go into the
fixes for FreeBSD as they are released. However, you do not &os.stable; branch, you do not <emphasis>need</emphasis> to
<emphasis>need</emphasis> to track &os.stable; to do this, as every track &os.stable; to do this. Every security advisory for
security advisory for FreeBSD explains how to fix the problem for FreeBSD explains how to fix the problem for the releases it
the releases it affects.</para> affects, and tracking an entire development branch just
for security reasons is likely to bring in a lot of unwanted
changes as well.</para>
<para>Although we endeavor to ensure that the &os.stable; branch <para>Although we endeavor to ensure that the &os.stable; branch
compiles and runs at all times, this cannot be guaranteed. In compiles and runs at all times, this cannot be guaranteed. In