From owner-freebsd-stable Mon Jun 11 16: 4:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hex.databits.net (hex.databits.net [207.29.192.16]) by hub.freebsd.org (Postfix) with SMTP id 229D937B407 for ; Mon, 11 Jun 2001 16:04:45 -0700 (PDT) (envelope-from petef@hex.databits.net) Received: (qmail 71235 invoked by uid 1001); 11 Jun 2001 23:04:43 -0000 Date: Mon, 11 Jun 2001 19:04:43 -0400 From: Pete Fritchman To: Juha Saarinen Cc: stable@FreeBSD.ORG Subject: Re: Why is the STABLE branch not so stable anymore? Message-ID: <20010611190443.B70538@databits.net> References: <20010611153217J.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from juha@saarinen.org on Tue, Jun 12, 2001 at 10:51:31AM +1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ++ 12/06/01 10:51 +1200 - Juha Saarinen: | I'm confused about this. The Handbook says to track -STABLE, if errr... | you want stability. Are you saying that in order to have a stable system, | we should stick with -RELEASE? | Perhaps the handbook should be updated then. If you want maximum "stability", you should track -STABLE. But not blindly.. don't cvsup to the latest code and {build,install}world on all your production machines without catching up on the mailing list. If you find a problem, report it for the benefit of others so they won't run into the same problem (because they should be tracking the mailing list). When you report a problem, remember this isn't a commercial entity, but a volunteer project and that a 6-hour turnaround time is pretty decent. It's not a life-or-death issue.. it's not like -stable was broken and nobody knew about it (I mean, when it broke, nobody knew about it.. but someone found it and reported it to stable@). On my production systems, I'll cvsup src/, and then wait a couple days to see if anybody reports big bugs/etc on stable@. Or, I'll just make world on one of my workstations and see if I notice anything broken. If, after a few days, everything looks good, I'll go ahead and make world on the production servers. If you want to keep your production systems in production, be smart about upgrading. -pete [who was thinking about making some analogy to IOS, but I'm too lazy to type up one of the many nightmares that resulted from IOS upgrades when we didn't look for bug reports/etc] -- Pete Fritchman Databits Network Services, Inc. finger petef@databits.net for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message