From owner-freebsd-stable@FreeBSD.ORG Tue Sep 16 19:47:21 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 B36B91065670; Tue, 16 Sep 2008 19:47:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (unknown [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 85FB28FC35; Tue, 16 Sep 2008 19:47:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id 1A6F546B35; Tue, 16 Sep 2008 15:47:21 -0400 (EDT) Date: Tue, 16 Sep 2008 20:47:21 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jo Rhett In-Reply-To: <2742CAB1-8FF2-425D-A3B6-0658D7DB8F4D@netconsonance.com> Message-ID: References: <1219409496.10487.22.camel@bauer.cse.buffalo.edu> <593618A3-56DA-4891-A4A0-690E9A9C5B32@netconsonance.com> <20080904133604.GB1188@atarininja.org> <47d0403c0809051319r3c82f87bhdb15ce5b0167987a@mail.gmail.com> <2742CAB1-8FF2-425D-A3B6-0658D7DB8F4D@netconsonance.com> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable , Wesley Shields , Nathan Way , Ben Kaduk Subject: Re: Upcoming Releases Schedule... 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: Tue, 16 Sep 2008 19:47:21 -0000 On Mon, 15 Sep 2008, Jo Rhett wrote: > On Sep 6, 2008, at 4:06 AM, Robert Watson wrote: >> Unfortunately, it's a little hard to tell at time-of-release whether a >> particular release will become extended life or not. This is because >> extended support status is dependent on the success of the release ... >> from earlier branch adopters. How long we keep release 6.x releases will >> depend entirely on how successful 7.x is; I think there's a reasonable >> expectation that 6.4 or 6.5 will be the last 6.x release, in which case we >> would want to grant it extended support status. But what happens depends a >> lot on how successful 7.1 is. My hopes are high, but there's nothing like >> real-world deployment to shed light on things :-). > > Robert, I'd like to point out to you that when I complained about 6.2's > accelerated EoL, I was soundly boxed around the ears and told that I should > have been paying attention to the projected EoL date when we decided to roll > out 6.2 across the business. > > I was also told that I should have been more active in the release cycle > process for 6.3, etc. > > Now you are saying that expected EoL will be determined at some random point > in the future based on gut feelings about how well a completely different > branch is doing. > > How can I reconcile these disparate points of view? How does one focus on > testing and upgrade cycle for an "appropriately supported release" when the > decision for the support cycle is completely up in the air? The FreeBSD Project, as with any other company or organization, responds to events as they occur. We try to plan ahead, and when things go better or worse than expected, we sometimes change the plans. As far as I know we've never *shortened* the expected support timeline for any branch or release, but we have on occasion lenthened them when we feel it's important to do so. I'm not sure what other answer is possible. Robert N M Watson Computer Laboratory University of Cambridge