Date: Sun, 10 Sep 2006 11:59:10 +1000 From: Mark Andrews <Mark_Andrews@isc.org> To: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! Message-ID: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> In-Reply-To: Your message of "Sat, 09 Sep 2006 13:28:31 EST." <20060909182831.GA32004@FS.denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yeah, -STABLE is what you should run if you want stable code, right? No. STABLE means STABLE API. If you want stable code you run releases. Between releases stable can become unstable. Think of stable as permanent BETA code. Changes have passed the first level of testing in current which is permanent ALPHA code. Most of the time beta code is perfectly fine to run but occasionally things will go wrong. The point of BETA code is to catch those errors that escape detection in the ALPHA stage before they make it into a release. That is done by having a wider diversity of clients run the BETA code. Occasionally you have bugs that make it through both the ALPHA and BETA stages. Mark -- ISC Training! October 16-20, 2006, in the San Francisco Bay Area, covering topics from DNS to DHCP. Email training@isc.org. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609100159.k8A1xAIn089481>