From owner-freebsd-doc Sat Apr 7 12:10:21 2001 Delivered-To: freebsd-doc@freebsd.org Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by hub.freebsd.org (Postfix) with ESMTP id 3C7DA37B43E for ; Sat, 7 Apr 2001 12:10:15 -0700 (PDT) (envelope-from manek@ecst.csuchico.edu) Received: from rover (vpn-24-16-30-209.corp.home.net [24.16.30.209]) by zipcode.corp.home.net (8.9.3/8.9.3) with SMTP id MAA14620 for ; Sat, 7 Apr 2001 12:10:13 -0700 (PDT) From: "Sameer R. Manek" To: Subject: Faq Addition suggestion Date: Sat, 7 Apr 2001 12:10:11 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This might be worth while adding to the faq, to append to this section. http://www.freebsd.org/FAQ/preface.html#STABLE Sameer -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Ken Bolingbroke Sent: Thursday, April 05, 2001 10:59 AM To: Steve Tremblett Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC On Thu, 5 Apr 2001, Steve Tremblett wrote: > I was under the impression that 4-STABLE was primarily for bugfixes > applied to the 4.2-RELEASE codebase, and 4-CURRENT is for development > of new features. Given that rationale, 4.3-RC should be a preliminary > merge of CURRENT code into STABLE. The intruduction of (relatively) > unproven code into an established as-stable-as-possible codebase > introduces instability until after it has been tested, therefore just > because 4.3-RC == 4-STABLE, that does not imply that 4.3-RC == stable. No, that's not how it works. It goes like this: 4.0-CURRENT -> 4.0-STABLE -> 4.1-RC -> 4.1-STABLE , etc There is no 4-CURRENT now. -CURRENT is currently 5.0-CURRENT. At some further point in time, 5.0-CURRENT will become 5.0-STABLE. But you'll never have another -CURRENT merged into 4-STABLE. And in the -STABLE branch, whatever the current name, the general idea is to introduce only small changes, bugfixes, security updates, and the like. So if you're following -STABLE at 4.2, you should be thinking of 4.2-STABLE as (4.2-RELEASE + bugfixes). And 4.3-RC would be (4.2-STABLE + more bugfixes). And 4.3-RELEASE will be (4.3-RC + yet more bugfixes). One difference is that commits are locked down in the -RC stage, so there's less change, less chance of things breaking when the branch is in the -RC stage. People tend to think it's a "beta" in the way Microsoft or other vendors might do a beta of their OS, but that's not how it works here. Given this, I feel that -RC is a safer bet than any arbitrary -STABLE, given that -STABLE is constantly changing, with less review than it gets in -RC. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message