From owner-cvs-all Tue Oct 3 15:56:42 2000 Delivered-To: cvs-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 706) id 1D31437B502; Tue, 3 Oct 2000 15:56:38 -0700 (PDT) Date: Tue, 3 Oct 2000 15:56:38 -0700 From: Jonathan Lemon To: Paul Richards Cc: Jordan Hubbard , Christopher Masto , Warner Losh , Kris Kennaway , Joseph Scott , Brian Somers , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, freebsd-security@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/finger finger.c Message-ID: <20001003155638.B73409@hub.freebsd.org> References: <83262.970607906@winston.osd.bsdi.com> <39DA6055.594B13E4@originative.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <39DA6055.594B13E4@originative.co.uk>; from Paul Richards on Tue, Oct 03, 2000 at 11:40:21PM +0100 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 03, 2000 at 11:40:21PM +0100, Paul Richards wrote: > > > > If it's now part of your full-time hattism to worry about this then I > > hope you'll start spending some number of hours each day in reviewing > > each and every change which goes into -stable. However many other > > I think you're looking at it the wrong way around. The stable team > wouldn't be putting in a lot of hours reviewing stable commits. Stable > commits would only occur if the stable team did them i.e. no-one else > would be allowed to commit to stable. The stable team would then monitor > -current, noting commits that are bug fixes, and slating them for a MFC > at a later date when it's felt they've had enough of a shakeout. > > Stable would stagnate to some extent, certainly more so than it > presently does, but I think that's exactly what should happen to a > stable branch. That's not to say that new features would never make it > back to the stable branch but they would certainly do so a lot more > slowly and only if there was real value to them and not just because > they exist. Uh. If only the "-stable" team were allowed to commit to -stable, then it would quickly become the -stale branch. I think that we had this at one point with 3.X, and there were lots of complaints. -stable is not (IMHO) supposed to be just bugfixes. Doing it that way would just put more pressure on the developers to shove the next release line out the door because they want new features. If you just want "bugfixes" and no new features, then may I suggest that you stick with the 3.X branch? No new development or changes go in there, but you can still pull in critical bug fixes as needed. Then when 5.0 becomes the -stable branch, you can move on to 4.x. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message