From owner-freebsd-stable@FreeBSD.ORG Mon Oct 25 12:38:06 2004 Return-Path: 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 DA94616A4CE for ; Mon, 25 Oct 2004 12:38:06 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8975043D41 for ; Mon, 25 Oct 2004 12:38:06 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i9PCbaKR005129; Mon, 25 Oct 2004 08:37:36 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9PCbZTd005126; Mon, 25 Oct 2004 13:37:36 +0100 (BST) (envelope-from robert@fledge.watson.org) Date: Mon, 25 Oct 2004 13:37:35 +0100 (BST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-stable@auscert.org.au In-Reply-To: <200410250516.i9P5GqiP019297@app.auscert.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Where to get 5.3 Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 12:38:07 -0000 On Mon, 25 Oct 2004 freebsd-stable@auscert.org.au wrote: > > Shogan2k1@aol.com writes: > > > Everyone keep on saying they have problem running 5.3 stable. But is > > > 5.3 stable really out? I can't find it anywhere. > > > > 5.3-RELEASE isn't out yet, but you can get 5.3-STABLE by cvsup'ing > > the RELENG_5 tag. > > As RELENG_5_3 has been branched, I have been tracking this release - I > presume this is the same as RELENG_5 until 5.3 RELEASE is frozen > (already?), but will then only change for security patches. (Someone > please correct me if this is an incorrect assumption) With the advent of 5.3, the intent is to expand the coverage of changes in the RELENG_MAJOR_MINOR branch to include critical other fixes in addition to the normal security fixes going into the branch. For example, if there is a critical stability fix for a driver or other system component. We also intend to adopt this approach for future 4.x releases. The bar will be high for changes to go into the branch, and will result in errata announcements (exact format to be determined) in much the same way we currently produce security advisories. The branch will remain "owned" by the security officer team, and any stability fixes will be merged by the release engineering team in close coordination with the security officer team. It is not the intent that the branches become "-STABLE" substitutes, since they won't be getting feature enhancements. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research