os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Nuke branch.sgml - it's not up-to-date anymore and seems largely forgotten.

Browse source
This commit is contained in:
Jordan K. Hubbard 1998-08-17 09:47:47 +00:00
parent d9183abb0d
commit 3e684476e3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=3359
2 changed files with 1 additions and 119 deletions

3
en/Makefile
View file

@ -1,4 +1,4 @@
# $Id: Makefile,v 1.43 1998-08-16 13:12:03 wosch Exp $
# $Id: Makefile,v 1.44 1998-08-17 09:47:47 jkh Exp $
.if exists(Makefile.conf)
.include "Makefile.conf"
@ -10,7 +10,6 @@
DOCS= applications.sgml
DOCS+= auditors.sgml
DOCS+= availability.sgml
DOCS+= branch.sgml
DOCS+= docs.sgml
DOCS+= features.sgml
DOCS+= register.sgml

117
en/branch.sgml
View file

@ -1,117 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1997-07-01 03:52:00 $">
<!ENTITY title "FreeBSD Announcement">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: branch.sgml,v 1.10 1997-07-01 03:52:00 max Exp $ -->
<html>
&header;
<em>From <a href="mailto:jkh@FreeBSD.org">jkh</a>, November 4th:</em>
<p>FreeBSD's development stream has, as of today, branched into the
<b>2.2-RELEASE</b> and <b>3.0-<a href="handbook/current.html">CURRENT</a></b>
development streams. The <b>2.1-<a href="handbook/stable.html">STABLE</a></b>
branch is also still alive, though now in maintenance mode after the
release of <b>FreeBSD-2.1.7</b>.</p>
<p>This branch has occurred so that <b>2.2</b> may be readied for release
without impacting significant new developments, like SMP support, in the
mainstream <a href="handbook/current.html">-current</a> branch.
<p>Modulo any of our usual two-week slips here and there, here is
our release schedule for 97:</p>
<h3>February 1997</h3>
<ul>
<li><b>FreeBSD 2.1.7-RELEASE</b>
<p>End of <b>2.1-STABLE</b> branch.</p>
</ul>
<h3>March 1997</h3>
<ul>
<li><b>FreeBSD 2.2-RELEASE</b>
<p>Beginning of <b>2.2-STABLE</b>.</p>
</ul>
<h3>Late Spring 1997</h3>
<ul>
<li><b>FreeBSD 2.2.x-RELEASE</b>
<p>Bugfix release for <b>2.2R</b> along <b>2.2-STABLE</b> branch.</p>
</ul>
<p>This is also probably as good a time as any to announce that new
XFree86 <a href="ftp://ftp.freebsd.org/pub/XFree86/3.2/binaries">
3.2 binaries</a>, with early <a href="http://www.matrox.com">Matrox</a>
support, are available.</p>
<p>Thanks to <a href="http://www.xfree86.org">The XFree86 project</a>
for the timely release, which will be distributed with <b>2.2-RELEASE</b>
and <b>2.1.7-RELEASE</b>.
<p>Lest there be any confusion about the <b>2.1.7</b> and <b>2.2</b> releases
coming so close together, let me also just explain that the two branches of
development had really very little to do with one another, and the fact
that both branches came to release status around the same time was
simply how the scheduling worked out. When engineering is allowed
to do the scheduling, it rarely employs traditional marketing
stratagems. :)</p>
<p>In summary:</p>
<ul>
<li><b>2.1.7-RELEASE</b> is aimed squarely at commercial users who do not need
to be on the leading edge of development but favor things like stability
and a long test-cycle instead. 2.1-<a href="handbook/stable.html">STABLE</a>
has had only incremental refinements made to it since <b>2.1.5</b> was
released, and <b>2.1.7</b> will end what we feel to have been a very
successful branch.<p></p>
<li><b>2.2-RELEASE</b> will begin introducing the more leading edge
technologies we have been developing over the year that
<a href="handbook/stable.html">-stable</a> has run in parallel,
and will also be entering bug-fix mode after its release. Existing
-stable customers will be encouraged to make the jump to 2.2-STABLE
some time after <b>2.2</b>'s release, once the first round of customer
PRs have come back and been acted on.<p></p>
<li><b>3.0-CURRENT</b> is now the bleeding edge of development, and where
all new development takes place. Until code freeze on the 10th
of November, changes may also be marked "For 2.2-RELEASE" and
they will be brought into that branch as necessary. After code
freeze, it will have to be a clearly important bug fix to make
it in before the release date.<p></p>
Many significant changes are planned for <b>3.0</b>, and those interested
in its development should subscribe to the freebsd-current
<a href="handbook/eresources.html">mailing list</a> (send mail to
<a href="mailto:majordomo@FreeBSD.ORG">majordomo@FreeBSD.ORG</a>).
</ul>
<p>As always, <em>all</em> branches of FreeBSD development are available
from a single CVS repository which may be freely replicated
to your own machine (see <a href="handbook/handbook.html">the handbook</a>) or
<a href="http://www.freebsd.org/cgi/cvsweb.cgi">browsed</a> via
the WEB.
<p>Please do not hesitate to use this valuable resource!</p>
<p></p>
<em>Note for CDROM customers</em>:
<p>If you are a regular FreeBSD
<a href="http://www.cdrom.com/titles/os/freebsd.htm">subscription customer</a>
of <a href="http://www.cdrom.com/">Walnut Creek CDROM</a>, you will receive
both <b>2.1.6</b> and <b>2.2</b> releases. Those who have already received a
<b>2.1.6</b> CD are also entitled to a free upgrade to <b>2.1.7</b> and should
<a href="mailto:orders@cdrom.com">contact them</a> about shipping a replacement
<b>2.1.7</b> CD.
<p>Making each release a full CD distribution was the only way of ensuring
that each would meet the quality expectations of each customer base, and
any customer who feels they would have preferred to receive only one release
may contact the <a href="mailto:orders@cdrom.com">the orders department</a>
at Walnut Creek CDROM at any time for a full refund or credit towards the next
subscription issue.</p>
&footer;
</body>
</html>