From owner-freebsd-security@FreeBSD.ORG Tue Jan 11 20:33:40 2005 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5B7816A4CE for ; Tue, 11 Jan 2005 20:33:40 +0000 (GMT) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 780BE43D45 for ; Tue, 11 Jan 2005 20:33:40 +0000 (GMT) (envelope-from nectar@celabo.org) Received: from lum.celabo.org (lum.celabo.org [10.0.1.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "lum.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id 4F4973E2C23; Tue, 11 Jan 2005 14:33:46 -0600 (CST) Received: by lum.celabo.org (Postfix, from userid 1001) id F266355C89E; Tue, 11 Jan 2005 14:33:38 -0600 (CST) Date: Tue, 11 Jan 2005 14:33:38 -0600 From: "Jacques A. Vidrine" To: Julian Elischer Message-ID: <20050111203338.GD7869@lum.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Julian Elischer , Christopher McCrory , freebsd-security@freebsd.org References: <1105317580.22779.12.camel@wednesday.pricegrabber.com> <20050110132233.GA5374@lum.celabo.org> <41E2D492.9020302@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E2D492.9020302@elischer.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.6i cc: Christopher McCrory cc: freebsd-security@freebsd.org Subject: Re: update for 4.11 Security Officer-supported branches X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 20:33:41 -0000 On Mon, Jan 10, 2005 at 11:16:34AM -0800, Julian Elischer wrote: > there will however be a RELENG_4 branch still active for those of us who > need to > continue generating 4.x based releases for ourselves.. > I'm assuming security patches goin gto 4.11 will also go there. Yep! And also errata fixes. > While a 4.12 will PROBABLY not happen, I do plan on continued MFCs of > important changes to RELENG_4 as I do not envision my custommers > moving to 5.x until some time in 2006 at the earliest. (Including > fixes from dragonfly, and possibly some new drivers and thing like USB > fixes. And I don't see any reason that such fixes cannot eventually be merged to the 4.11 errata branch, assuming they are well-tested. That'd be great for everyone! Cheers, -- Jacques A Vidrine / NTT/Verio nectar@celabo.org / jvidrine@verio.net / nectar@FreeBSD.org