From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 19:14:18 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 7FD561065673 for ; Mon, 22 Sep 2008 19:14:18 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id 5E8838FC19 for ; Mon, 22 Sep 2008 19:14:18 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id m8MJEFNb011267; Mon, 22 Sep 2008 12:14:15 -0700 (PDT) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -1.021 X-Spam-Level: X-Spam-Status: No, score=-1.021 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=0.419] Message-Id: <34CE6F7C-DFB9-4B82-88F1-0B847283FC73@netconsonance.com> From: Jo Rhett To: "Simon L. Nielsen" In-Reply-To: <20080920205645.GI1151@arthur.nitro.dk> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 22 Sep 2008 12:14:10 -0700 References: <15F15FD1-3C53-4018-8792-BC63289DC4C2@netconsonance.com> <448wtpcikb.fsf@be-well.ilk.org> <34C3D54B-C88C-4C36-B1FE-C07FC27F8CB5@netconsonance.com> <20080920020703.GA82392@phat.za.net> <851F09A2-788D-4343-9E00-A0AB5C3AC063@netconsonance.com> <4d7dd86f0809192057s33dfd92fv598488a4c05ada14@mail.gmail.com> <4B2A556D-B13D-4B71-819A-F9B23C5685AF@netconsonance.com> <20080920205645.GI1151@arthur.nitro.dk> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable 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: Mon, 22 Sep 2008 19:14:18 -0000 On Sep 20, 2008, at 1:56 PM, Simon L. Nielsen wrote: >> 2 years for each supported branch would be excellent, although I'm >> open to alternatives. Right now 6.4 will EoL before 6.3 will :-( > > Eh, where did you get that information? AFAIK the EoL date of 6.4 has > not yet been decided (and I should know though of course I could have I asked specifically on this list. First I was told it hadn't been decided. My response was to point out that this makes it very hard for a company to decide to commit resources to test it, if there may never be a reasonable chance for deployment. Then I was told it was 1 year, or perhaps just 6 months if it was ruled to be an unstable version. Either answer is less than 6.3's support period. > If, when we get closer to the actual release, still is the plan for > 6.4 to be the last RELENG_6 release I'm almost certain 6.4 will be a > Extended Support release. That would be excellent. As soon as you know if this will be true, I'll be able to convince $EMPLOYER to allow me to spend time testing this release. If its not an extended support release, then it will expire before 6.3 (which is already tested) and thus $EMPLOYER gains no value in the effort. FWIW, this is why I'm in favor of consistent support periods. When you align the business benefit with the community benefit, you can get the business to help improve the community product. (remainder snipped to a different subject line) -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness