Date: Tue, 3 Oct 2000 17:34:14 -0700 From: Kris Kennaway <kris@FreeBSD.org> To: Jordan Hubbard <jkh@winston.osd.bsdi.com> Cc: Paul Richards <paul@originative.co.uk>, Christopher Masto <chris@netmonger.net>, Warner Losh <imp@village.org>, Kris Kennaway <kris@FreeBSD.org>, Joseph Scott <joseph.scott@owp.csus.edu>, Brian Somers <brian@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, freebsd-security@FreeBSD.org Subject: Re: How long for -stable [ Re: cvs commit: src/usr.bin/finger finger.c ] Message-ID: <20001003173414.A58372@freefall.freebsd.org> In-Reply-To: <84222.970618959@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Tue, Oct 03, 2000 at 05:22:39PM -0700 References: <paul@originative.co.uk> <84222.970618959@winston.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 03, 2000 at 05:22:39PM -0700, Jordan Hubbard wrote:
> I would therefore like to propose the following: We change the wording
> of our policy to state that upgrading to something within two releases
> of the "current -stable" product is the *recommended* action but that
> we will continue to provide, WHERE POSSIBLE, support for older
> branches of FreeBSD. We also stop telling people running 3.x (or
I suggest that in practise it will be all but impossible for people to
get active bugfix support for 3.x, and we'd probably be giving a false
impression if we say otherwise.
If some of the developers really plan to devote significant efforts
towards supporting 3.x (or whatever "dead branch of the month" we
have), let them do so for 3 or 4 months to prove their ability to do
so, and if it's actually worked by the end of the trial period then we
can officially change the published policy.
Speaking for myself as part of the security team, I don't want to
support 3.x for security fixes any more, since it's been just too damn
hard to do that over the past few months (i.e. in fact we havent been
providing good security support because developers aren't backporting
security fixes), and as warner pointed out we've now passed our "3
releases along a branch" cutoff policy.
Again, if someone else is going to step up and commit to fixing
problems in 3.x I'll work with them (i.e. give them an advisory
prerelease and release deadline to get the fix merged by, and if they
miss it, too bad), but I would prefer not to do this myself for time
constraints. I think I'd like to formally announce this unless
someone steps up to the plate with the above.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001003173414.A58372>