Date: Thu, 19 Mar 1998 03:33:13 -0600 (CST) From: "Matthew D. Fuller" <fullermd@futuresouth.com> To: Jay Nelson <jdn@acp.qiv.com> Cc: Robert Withrow <witr@rwwa.com>, "Michael V. Harding" <mvh@netcom.com>, stable@FreeBSD.ORG Subject: Re: 'Code Freeze' Message-ID: <Pine.BSF.3.96.980319032854.20071D-100000@shell.futuresouth.com> In-Reply-To: <Pine.BSF.3.96.980318221246.1621A-100000@acp.qiv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Mar 1998, Jay Nelson wrote: > On Wed, 18 Mar 1998, Robert Withrow wrote: > > >My advice, which I'm sure everyone will ignore, is for Jordan and > >friends to 'fess up and admit that the current state of "stable" isn't > >stable enough for cutting a CD release, re-freeze now and only allow > >bug fixes for the next 30-45 days (including fixes for the slice > >stuff) and *then* cut the release. I'm pretty sure everyone *buying* > >the CD's would rather a delay than [another] less-than-completely-stable > >release. <snip> > What Micheal is suggesting is something that would satisfy everyone. > Why rush new changes into an impending release? -SABLE goes on for > those who want to have the latest, and -CURRENT goes on for those > who bleed, but a _stable_ CD is something the rest of us can install > and walk away from without midnight pages. > > I am truly grateful for the effort everyone associated with FreeBSD > has invested to make available to me an OS as good as this, and to > Walnut Creek for making the CDs available. I am subscribed and would > be happy to pay for 2.2.6 and 7 and 8 and 9, etc., but login.conf and > slice changes seems to make more for 2.3.x than 2.2.x. (ELF, by the > way seems more like 6.0.x -- I hope :-) Well, here's my $0.015 on this issue. 1) We go from 2.2.5-STABLE into 2.2.6-ALPHA, whre any features we want in 2.2.6 are stuck in. 2) After a while of this, we break off 2.2.6-BETA, in which only bug fixes/backouts are incorprated 2b) HOWEVER, at this time, 2.2-STABLE breaks back off and continues as it has been 3) 2.2.6-RELEASE comes out 4) Any finagleing necessary to go from 2.2.6-REL to 2.2.6-STABLE gets incorporated, and process repeats. This is NOT a reproach, not a flame, just a suggestion for something that seems, if not broken, at least a little askew. A stitch in time, etc. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980319032854.20071D-100000>