Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Dec 2001 09:39:10 +0000
From:      Josh Paetzel <friar_josh@webwarrior.net>
To:        Michael Lucas <mwlucas@blackhelicopters.org>
Cc:        doc@FreeBSD.ORG
Subject:   Re: what to call the patched releases?
Message-ID:  <20011211093909.D397@twincat.vladsempire.net>
In-Reply-To: <20011211051633.B35343@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Dec 11, 2001 at 05:16:33AM -0500
References:  <20011211051633.B35343@blackhelicopters.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011211093909.D397>