From owner-freebsd-stable Tue Sep 1 12:05:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04579 for freebsd-stable-outgoing; Tue, 1 Sep 1998 12:05:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04571 for ; Tue, 1 Sep 1998 12:05:11 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id MAA19740; Tue, 1 Sep 1998 12:03:57 -0700 (MST) From: "Chad R. Larson" Message-Id: <199809011903.MAA19740@freebie.dcfinc.com> Subject: Re: Requisite steps for tracking -stable To: rone@B1FF.nas.nasa.gov (Ron Echeverri) Date: Tue, 1 Sep 1998 12:03:57 -0700 (MST) Cc: stable@FreeBSD.ORG In-Reply-To: <199809011640.JAA09654@B1FF.nas.nasa.gov> from Ron Echeverri at "Sep 1, 98 09:40:05 am" Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan K. Hubbard writes: > > This seems like an escalation of responsibility for the user. > > I've read (and agree) that tracking -stable without subscribing to the > > stable mailing list is asking for whatever you get. I'd never heard a > > requirement for reading the CVS logs before. > If it's not a documented requirement, I agree that it should be. > Running -current or -stable for the uninitiated is just too dangerous > and I definitely forsee a day when cvsup won't even touch your source > tree until it's verified that you performed all the requisite steps. > > So, to make things as clear as possible, what are all the requisite > steps? I, too, was under the impression subscribing to freebsd-stable > would be enough to keep track of vital information regarding the > -stable tree. If there is something else that must be done, this > should be detailed somewhere obvious, like the Handbook. I'd offer another (perhaps obvious) suggestion. The requirements to track -current might include reading the CVS logs while tracking -stable probably shouldn't. Keep in mind that the differences in -stable users and -current users. The current guys are happy to be bleeding edge, want the latest-n-greatest and/or are actively working on code (and reading -hackers, we'd hope). The -stable guys aren't necessarily able to spend a lot of time keeping up. They're running production on their boxes, not entertaining themselves with O/S development. That's =why= they're running -stable. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message