Date: Wed, 24 Sep 2008 12:36:35 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: Jo Rhett <jrhett@netconsonance.com>, Robert Watson <rwatson@freebsd.org>, Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> Subject: Re: Upcoming Releases Schedule... Message-ID: <200809241236.36319.jhb@freebsd.org> In-Reply-To: <5307532F-194E-482D-8617-2FB6E13E3F83@netconsonance.com> References: <1219409496.10487.22.camel@bauer.cse.buffalo.edu> <200809231610.17625.jhb@freebsd.org> <5307532F-194E-482D-8617-2FB6E13E3F83@netconsonance.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 23 September 2008 04:42:13 pm Jo Rhett wrote: > John, we're already committed to upgrade to 6.3 (since it will > currently be supported longer than 6.4). 6.2 support isn't part of > this conversation, it has entirely revolved around support periods for > upcoming releases. Then replace 6.2 with 6.3 in my comments. Granted, there's nothing to do with 6.3 until it is EOL'd, but you should still get the general idea. I picked 6.2 just to have a specific example to work with. > On Sep 23, 2008, at 1:10 PM, John Baldwin wrote: > > Jo, so it seems to me that you could just start by maintaining your > > own set of > > extended support patches for the FreeBSD releases you care about. I > > don't > > think you have to be a committer or secteam@ member to do this. It > > does mean > > that you might not be able to fix a bug in, say, 6.2 at the same > > exact time > > the advisory goes out at first, but you could take the patch from the > > advisory and apply it to your local 6.2 tree and then update your > > "cumulative > > patch" (would probably want to use some sort of source code control > > for this > > where you basically branch from FreeBSD X.Y where X.Y is a vendor > > branch of > > sorts). That would let you build the "street cred", as it were, to > > be able > > to get the patches directly into FreeBSD more easily. > > > > To start with it is probably going to be a bit slow as far as > > getting things > > committed directly to FreeBSD proper as it means finding a committer > > who has > > the time to test and review your patch and then commit it. However, > > the "Unofficial FreeBSD 6.2 Patchset" can be updated more quickly > > since it is > > something that would be under your control. Also, doing this will > > give you > > insight into exactly what is required to support a release after it > > is EOL'd > > in a much more direct fashion than an e-mail thread. > > > > -- > > John Baldwin > > -- > Jo Rhett > Net Consonance : consonant endings by net philanthropy, open source > and other randomness > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809241236.36319.jhb>