From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 16:49:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DFF716A416 for ; Sun, 10 Sep 2006 16:49:00 +0000 (UTC) (envelope-from christopher@schulte.org) Received: from monster.schulte.org (monster.schulte.org [209.134.156.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC69543D49 for ; Sun, 10 Sep 2006 16:48:59 +0000 (GMT) (envelope-from christopher@schulte.org) Received: from localhost (localhost.schulte.org [127.0.0.1]) by monster.schulte.org (Postfix) with ESMTP id B30C51CC0F; Sun, 10 Sep 2006 11:48:58 -0500 (CDT) X-Virus-Scanned: amavisd-new at schulte.org Received: from monster.schulte.org ([127.0.0.1]) by localhost (monster.schulte.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id so4invfbb5G1; Sun, 10 Sep 2006 11:48:54 -0500 (CDT) Received: from 2k3.windows2003.schulte.org (exchange.windows2003.schulte.org [209.134.156.205]) by monster.schulte.org (Postfix) with ESMTP; Sun, 10 Sep 2006 11:48:54 -0500 (CDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable x-mimeole: Produced By Microsoft Exchange V6.5 Date: Sun, 10 Sep 2006 11:48:52 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! Thread-Index: AcbU7YT7J80Lj0s/SqW2bbZ/HpuI1gABiqNA From: "Christopher Schulte" To: "Patrick J Okui" , "Karl Denninger" Cc: freebsd-stable@freebsd.org Subject: RE: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Sep 2006 16:49:00 -0000 > -----Original Message----- > From: owner-freebsd-stable@freebsd.org=20 > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Patrick J Okui > Sent: Sunday, September 10, 2006 10:22 AM > To: Karl Denninger > Cc: freebsd-stable@freebsd.org > Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! >=20 > You can track changes to a particular release - say by using > RELENG_6_1 rather than RELENG_6. In which case, would you=20 > still say you are tracking STABLE? Well, that depends. For security and "critical fixes" (as the handbook phrases it) you can track RELENG_6_1 (in the case of 6.1-RELEASE) and be happy. But what happens if the needed fix isn't security or "critical" in the minds of the FreeBSD developers? At that point you either need to wait for the next RELEASE, manually merge fixes into your production source (which depending on the fix(s) could be non-trivial) or cross your fingers and follow -STABLE. This problem isn't specific to FreeBSD (or unix in general) by Any means, of course. Sure, we could broaden the scope of RELENG_X_Y. Or introduce a new branch that's closer to -STABLE yet tuned for something like, "security, critical and major fixes" for production systems. I'm not sure either of those options are preferable, would be effective in alleviating the problem, or even workable in the first place. Personally, I've been served quite well for many years with the current configuration. Since I don't track -STABLE on anything important (or more accurately have yet NEEDED to do so), I've never been hit by any of these transient issues that crop up from time to time and can elicit loud complaints. --Chris