From owner-freebsd-doc Tue Dec 11 7:39:11 2001 Delivered-To: freebsd-doc@freebsd.org Received: from services.webwarrior.net (overlord-host99.dsl.visi.com [209.98.86.99]) by hub.freebsd.org (Postfix) with ESMTP id 3E12837B405 for ; Tue, 11 Dec 2001 07:39:08 -0800 (PST) Received: from twincat.vladsempire.net (hutch-771.hutchtel.net [206.10.71.71]) by services.webwarrior.net (Postfix) with ESMTP id 3D5D0204 for ; Tue, 11 Dec 2001 09:39:20 -0600 (CST) Received: by twincat.vladsempire.net (Postfix, from userid 1001) id 24C5C3863; Tue, 11 Dec 2001 09:39:10 +0000 (GMT) Date: Tue, 11 Dec 2001 09:39:10 +0000 From: Josh Paetzel To: Michael Lucas Cc: doc@FreeBSD.ORG Subject: Re: what to call the patched releases? Message-ID: <20011211093909.D397@twincat.vladsempire.net> References: <20011211051633.B35343@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211051633.B35343@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Dec 11, 2001 at 05:16:33AM -0500 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Dec 11, 2001 at 05:16:33AM -0500, Michael Lucas wrote: > Folks, > > We have something that isn't quite documented in the FAQ. I made a > stab at answering this, but Bruce made some comments that made me > really rethink the whole thing. (That's what a mentor is for, I > suppose. :-) > > We have our new "security patched" branches, i.e., 4.4. What are they > called? We can "track -stable", "track -current", i.e. I've heard > this as "tracking -release", "the -patched" branch, etc. Do we have > an official name, or should we knock at re@freebsd.org for appropriate > terminology? > > ==ml > -- > Michael Lucas > mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org > http://www.blackhelicopters.org/~mwlucas/ > Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons I suppose as our userbase gets larger, and our product line becomes deeper, we are going to run into more and more of these things. It's fine to say that We support the latest 4.x-RELEASE and -STABLE, but that doesn't help a guy who is forced to run a 3.3 box because he just can't take it down. How about a list (or a branch as it were) for back ported security patches. The FreeBSD security maintanance branch. List in that all versions of FreeBSD that are up to date as far as security patches go. Drop them out if something comes up that isn't going to make it back to that particular release. This is really a rough first time impression, but maybe enough for us to chew on. Josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message