From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 01:59:16 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 13AD116A407 for ; Sun, 10 Sep 2006 01:59:16 +0000 (UTC) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8EB143D46 for ; Sun, 10 Sep 2006 01:59:15 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 38188E601F for ; Sun, 10 Sep 2006 01:59:14 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.8/8.13.6) with ESMTP id k8A1xAIn089481 for ; Sun, 10 Sep 2006 11:59:11 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> To: freebsd-stable@freebsd.org From: Mark Andrews Mail-Followup-To: freebsd-stable@freebsd.org In-reply-to: Your message of "Sat, 09 Sep 2006 13:28:31 EST." <20060909182831.GA32004@FS.denninger.net> Date: Sun, 10 Sep 2006 11:59:10 +1000 Sender: Mark_Andrews@isc.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 01:59:16 -0000 > 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