The latest -stable release is 3.1, not 2.2.8.

This commit is contained in:
Dag-Erling Smørgrav 1999-03-18 21:12:14 +00:00
parent 4f76f94131
commit 76158cc799
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=4544

View file

@ -1,4 +1,4 @@
<!-- $Id: preface.sgml,v 1.28 1999-01-29 18:37:16 wosch Exp $ -->
<!-- $Id: preface.sgml,v 1.29 1999-03-18 21:12:14 des Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect>
@ -88,22 +88,13 @@
<sect1>
<heading>What is the latest version of FreeBSD?</heading>
<p>Version <url url="ftp://ftp.freebsd.org/pub/FreeBSD/releases/2.2.8-RELEASE"
name="2.2.8"> is the latest <em>stable</em> version; it was released
in December, 1998. This is also the latest <em>release</em> version.
<p>Version <url url="ftp://ftp.freebsd.org/pub/FreeBSD/releases/3.1-RELEASE"
name="3.1"> is the latest <em/stable/ version; it was released
in February, 1999. This is also the latest <em/release/ version.
<p>Briefly explained, <bf>-stable</bf> is aimed at the ISP or other
<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 release. At the moment, these
versions are one and the same, but it shouldn't be long before the
<bf>-current</bf> branch is polished enough for general release.
<p>This is not to say that a 3.0-STABLE release is unusable for
business services, and many people who need some 3.0 specific feature
(newer compiler technology, faster networking code, etc) have decided
to take a chance with it with very good results. We simply do not
wish to "certify" 3.0 as mission-worthy until it's been released
as 3.1-RELEASE in February, 1999.
the wizzy new features of the latest <em/-current/ snapshot.
<sect1>
<heading>What is FreeBSD-current?<label id="current"></heading>