Date: Sun, 21 Sep 2008 09:57:52 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: netgeek <netgeek@bgp4.net> Cc: Jo Rhett <jrhett@netconsonance.com>, freebsd-stable <freebsd-stable@freebsd.org>, Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> Subject: Re: Upcoming Releases Schedule... Message-ID: <alpine.BSF.1.10.0809210952560.58772@fledge.watson.org> In-Reply-To: <48D596AD.1070209@bgp4.net> References: <1219409496.10487.22.camel@bauer.cse.buffalo.edu> <20080904133604.GB1188@atarininja.org> <CB36FE28-D125-4C22-B5DE-1001515DD8A6@netconsonance.com> <47d0403c0809051319r3c82f87bhdb15ce5b0167987a@mail.gmail.com> <alpine.BSF.1.10.0809061159410.28840@fledge.watson.org> <2742CAB1-8FF2-425D-A3B6-0658D7DB8F4D@netconsonance.com> <alpine.BSF.1.10.0809162043380.64176@fledge.watson.org> <0C2C7E9B-61E3-4720-B76F-4745A3C963DA@netconsonance.com> <alpine.BSF.1.10.0809180022580.13100@fledge.watson.org> <658B8861-1E78-4767-8D3D-8B79CC0BD45F@netconsonance.com> <alpine.BSF.1.10.0809181935540.16464@fledge.watson.org> <15F15FD1-3C53-4018-8792-BC63289DC4C2@netconsonance.com> <448wtpcikb.fsf@be-well.ilk.org> <C096D142-4572-48DF-8CCA-053B41003A07@netconsonance.com> <alpine.BSF.1.10.0809191158330.40909@fledge.watson.org> <34C3D54B-C88C-4C36-B1FE-C07FC27F8CB5@netconsonance.com> <alpine.BSF.1.10.0809201102270.22368@fledge.watson.! org> <48D596AD.1070209@bgp4.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Sep 2008, netgeek wrote: >> Don't get me wrong: I would love to see us support all releases for 24 >> months (or even more) after they ship. I think our users would appreciate >> that also. > > Perhaps there is a middle ground here? What about a statement that each > major branch (6.x, 7.x) will be supported for at least 24+ months from its > last production release? Smaller periods of support could be given to minor > releases along the way (7.2, for example), but at least companies would know > that if they installed a 6.x version, they'd have support for a couple of > years, even if that might mean upgrading to a newer minor version if there > was a problem. This is precisely what we already do -- we guarantee we will support the last release on a branch for 24 months after the release. The point of concern being discussed is that we can't tell you for sure which minor release will be the last release at the time that release goes out the door, because the extent to which we keep releasing on old branches depends in large part on how the new branch looks. Right now, it sounds like 6.4 will be the last minor release on the 6.x branch, but I think it would be a mistake to commit to that decision until 7.1 has settled in for a few months and we believe firmly there is a good migration path forwards to the 7.x branch. 7.0 was arguably one of the most stable .0 releases we've ever done (perhaps the most stable -- 4.0 was pretty good though), so it seem almost certain 7.1 will be really stable, but stable is what happens when people install it and it works well in practice, so there's always a wait-and-see element. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0809210952560.58772>