Date: Sun, 10 Sep 2006 11:48:52 -0500 From: "Christopher Schulte" <christopher@schulte.org> To: "Patrick J Okui" <pokui@psg.com>, "Karl Denninger" <karl@denninger.net> Cc: freebsd-stable@freebsd.org Subject: RE: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! Message-ID: <AE12D302E6E62544BEDBD6D1AAAEE9AE0B7C1A@2k3.windows2003.schulte.org>
next in thread | raw e-mail | index | archive | help
> -----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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE12D302E6E62544BEDBD6D1AAAEE9AE0B7C1A>