Date: Sun, 10 Sep 2006 19:11:17 -0500 From: Karl Denninger <karl@denninger.net> To: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! Message-ID: <20060911001117.GA44739@FS.denninger.net> In-Reply-To: <00c301c6d50d$751ffe80$0a0aa8c0@rivendell> References: <20060910183958.GA35701@FS.denninger.net> <00c301c6d50d$751ffe80$0a0aa8c0@rivendell>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 10, 2006 at 10:15:20PM +0300, Reko Turja wrote: > From: "Karl Denninger" <karl@denninger.net> > To: <freebsd-stable@freebsd.org> > Sent: Sunday, September 10, 2006 9:39 PM > >Yes it is, in the general case; in any event if you track RELENG_6_1 > >you will > >get no bug fixes in general - security related items to filter back > >down but > >in general bug reports posted against a -RELEASE are, if addressed, > >put into > >-STABLE. > > You would like untested fixes to hit the release version first? By the > way, possible breakage of STABLE due MFC process was announced a good > while ago... No, I would like -STABLE to be treated as what it is claimed to be - BETA code, not ALPHA code. There's a huge difference between the two, and MFCing something back to -STABLE without testing the <BASIC> functionality of the module you're working with first does not fit the BETA model (it DOES fit the Alpha model.) This is coming from someone who has run FreeBSD in a production environment for basically 10 years, and has even sometimes used -CURRENT during that time (with full knowledge that running THAT is, indeed, ALPHA code!) -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060911001117.GA44739>