From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 15:28:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 709A3106566B for ; Sun, 8 Jun 2008 15:28:41 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3737D8FC16 for ; Sun, 8 Jun 2008 15:28:41 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F413F46C15; Sun, 8 Jun 2008 11:10:28 -0400 (EDT) Date: Sun, 8 Jun 2008 16:10:28 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Chris Marlatt In-Reply-To: <4848073C.2060509@rxsec.com> Message-ID: <20080608160550.C16871@fledge.watson.org> References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <4846E14C.709@FreeBSD.org> <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <4848073C.2060509@rxsec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Adrian Chadd , FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 15:28:41 -0000 On Thu, 5 Jun 2008, Chris Marlatt wrote: > Adrian Chadd wrote: >> The project is doing what it can with what people are contributing. If > > What if it can accomplish the same or more by simply reorganizing what it's > already doing? I completely understand the apparent situation - if you look > at it from all angles it appears to be no different than that of the people > apposed to the recent scheduling changes FreeBSD has made. There's a limited > amount of people and time to do everything. It's an order-of-magnitude question. The work required to support a release for 48 months is more than double the work required to support a release for 24 months. The current regular and extended support releases reflect a practical balance with respect to how long a release can be support. We provide a much longer timeline of support for *branches*, however, and that's generally the support mechanism recommended for people looking for 4-6 years of support for a version of FreeBSD. If you look at what other OS vendors do -- Microsoft is a particularly easy example to inspect -- they require occasional large-scale updates while you live on a particular branch. For example, if you're going to keep running Win2k for six years, you must install their service packs, not just hot fixes for specific vulnerabilities. Our minor releases on a branch are a *lot* less disruptive than service packs for Windows, and are much more conservative. Robert N M Watson Computer Laboratory University of Cambridge