From owner-freebsd-current Sat Feb 21 10:45:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27649 for freebsd-current-outgoing; Sat, 21 Feb 1998 10:45:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27639 for ; Sat, 21 Feb 1998 10:45:54 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id MAA15049; Sat, 21 Feb 1998 12:45:39 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <34f0277d.678104@mail.cetlink.net> References: <19980221143803.31160@freebie.lemis.com> <199802210245.NAA06439@cimlogic.com.au> <23061.888029515@time.cdrom.com> <19980221143803.31160@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 21 Feb 1998 12:44:48 -0600 To: jak@cetlink.net (John Kelly) From: Richard Wackerbarth Subject: Re: More breakage in -current as a result of header frobbing. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:22 PM -0600 2/21/98, John Kelly wrote: >On Sat, 21 Feb 1998 14:38:03 +1030, Greg Lehey wrote: > >>Maybe now's an appropriate time to come out with a thing that I've >>been meaning to propose for some time: >> >>Sure, living with -CURRENT means never knowing where your next install >>comes from > >I propose that after 2.2.6 or 2.2.7, whichever comes last, that you >just do away with -stable altogether and start making three or four CD >SNAPs of -current per year and call it "semi-stable." Just catch the >-current tree at a really good time when making those CDs. This would definitely be the WRONG way to go. We need to be making EXTREMELY HIGH QUALITY releases. >>From my point of view, the gap between -stable and -current has grown >too wide to keep much interest in -stable. PPPD is a good example. >The version in -stable is more than two years old. I do not disagree that the gap is wider than might be desirable. However, there are two ways to close that gap. 1) Move features that have been well tested back into the 2.2 branch (pppd might well be an appropriate candidate for this approach) 2) Freeze a 3.0 release and start improving its stability. This second approach will eventually become necessary even if (1) is used as an interim measure. However, when this is appropriate is a decision for the development team. In either case, the "stable" concept will not go away. There will always be those who are working on "not ready for prime time" enhancements. If those features are to get more than local testing, they will have to go into an "experimental/development" tree rather than the "reliable" one. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message