Update branch information.

This commit is contained in:
Jordan K. Hubbard 1997-02-20 09:15:41 +00:00
parent 0af4c791f9
commit 23fdb8b6ca
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=1196
2 changed files with 44 additions and 36 deletions

View file

@ -1,5 +1,5 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1997-01-29 00:12:56 $">
<!ENTITY date "$Date: 1997-02-20 09:15:41 $">
<!ENTITY title "FreeBSD Announcement">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
@ -11,27 +11,27 @@
<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, soon to terminate (for real, this time)
with the impending release of <b>FreeBSD-2.1.6</b>.</p>
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 96/97:</p>
our release schedule for 97:</p>
<h3>December 1996</h3>
<h3>February 1997</h3>
<ul>
<li><b>FreeBSD 2.1.6-RELEASE</b>
<li><b>FreeBSD 2.1.7-RELEASE</b>
<p>End of <b>2.1-STABLE</b> branch.</p>
</ul>
<h3>February 1997</h3>
<h3>March 1997</h3>
<ul>
<li><b>FreeBSD 2.2-RELEASE</b>
<p>Beginning of <b>2.2-STABLE</b>.</p>
</ul>
<h3>Spring 1997</h3>
<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>
@ -44,9 +44,9 @@ 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.6-RELEASE</b>.
and <b>2.1.7-RELEASE</b>.
<p>Lest there be any confusion about the <b>2.1.6</b> and <b>2.2</b> releases
<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
@ -56,11 +56,11 @@ stratagems. :)</p>
<p>In summary:</p>
<ul>
<li><b>2.1.6-RELEASE</b> is aimed squarely at commercial users who do not need
<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.6</b> will end what we feel to have been a very
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
@ -98,12 +98,16 @@ the WEB.
<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. 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
both <b>2.1.6</b> and <b>2.2</b> releases. Those who have already received
<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> if you have not already
received <b>2.1.7</b>.
<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;