Add new wording explaining more about how branches work

with FreeBSD.  Change "instability" to "volatility" when
talking about -current.

PR:             docs/11028
Submitted by:   Lowell Gilbert <lowell@world.std.com>
This commit is contained in:
Nik Clayton 1999-05-29 13:02:47 +00:00
parent 0f56ee2f81
commit 9e34892b04
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=4969

View file

@ -1,4 +1,4 @@
<!-- $Id: preface.sgml,v 1.36 1999-05-19 12:47:54 jesusr Exp $ -->
<!-- $Id: preface.sgml,v 1.37 1999-05-29 13:02:47 nik Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect>
@ -96,6 +96,16 @@
<p>Briefly explained, <em/-stable/ is aimed at the ISP or other
corporate user who wants stability and a low change count over
the wizzy new features of the latest <em/-current/ snapshot.
Releases can come from either "branch," but you should only use
<em/-current/ if you're sure that you're prepared for its
increased volatility (relative to <em/-stable/, that is).
<p>Releases are only made <ref id="release_freq" name="every few
months">. While many people stay more up-to-date with the
FreeBSD sources (see the questions on <ref id="current"
name="FreeBSD-current"> and <ref id="stable"
name="FreeBSD-stable">) than that, doing so is more of a
commitment, as the sources are a moving target.
<sect1>
<heading>What is FreeBSD-current?<label id="current"></heading>
@ -148,7 +158,7 @@
branches.
<sect1>
<heading>What is the FreeBSD-stable concept?</heading>
<heading>What is the FreeBSD-stable concept?<label id="stable"></heading>
<p>Back when FreeBSD 2.0.5 was released, we decided to branch FreeBSD
development into two parts. One branch was named <url
@ -197,7 +207,7 @@
with the first 4.0 releases appearing in Q1 2000.
<sect1>
<heading>When are FreeBSD releases made?</heading>
<heading>When are FreeBSD releases made?<label id="release_freq"></heading>
<p>As a general principle, the FreeBSD core team only release a new
version of FreeBSD when they believe that there are sufficient new