From owner-freebsd-stable@FreeBSD.ORG Fri Sep 5 20:19:24 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 45E2E106566C for ; Fri, 5 Sep 2008 20:19:24 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by mx1.freebsd.org (Postfix) with ESMTP id 11D748FC1B for ; Fri, 5 Sep 2008 20:19:23 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so574432wfg.7 for ; Fri, 05 Sep 2008 13:19:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=rcOAxWG8hMpBZsKmsiTiFmdGl6oMXxCGju1gN520djE=; b=QFz82LO9NZBY37sEzWb4rHcC9vpYDd2f7q/U2OJES4t87OZfNJRnmen7uuObV40ZjR hJDmRs87GF0zZ4mGKsZDSP/R0KD5Kx7LQPVCgEr8V3dvvpf4deYKZr+a6zZf/gTOsTTC 7TU5LLkYaW/3CFBfoDYTGw1DfQ18GgI9R2fVo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=e/oFsxsNi3NPUPLfFb547yEfjyHeeFdYj2MlSJ0c8hWPMuoe4ttzhWxKc5NbT0HBiR ovFwycLd/4/z0g4c95wHPN9ZXbHB+cVoZlJ4VzZvsPjzOIVzsSc3lH88jOz/IG0JGZC9 2EQ/tkPVaKFTsSox0D/QnaAqwtiVfSTMCpXSM= Received: by 10.142.201.3 with SMTP id y3mr4225148wff.5.1220645963576; Fri, 05 Sep 2008 13:19:23 -0700 (PDT) Received: by 10.142.222.16 with HTTP; Fri, 5 Sep 2008 13:19:23 -0700 (PDT) Message-ID: <47d0403c0809051319r3c82f87bhdb15ce5b0167987a@mail.gmail.com> Date: Fri, 5 Sep 2008 16:19:23 -0400 From: "Ben Kaduk" To: "Jo Rhett" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1219409496.10487.22.camel@bauer.cse.buffalo.edu> <593618A3-56DA-4891-A4A0-690E9A9C5B32@netconsonance.com> <20080904133604.GB1188@atarininja.org> Cc: Nathan Way , Wesley Shields , 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: Fri, 05 Sep 2008 20:19:24 -0000 On Thu, Sep 4, 2008 at 2:40 PM, Jo Rhett wrote: >>>> Where can one find the expected EoL for these releases? > >> On Wed, Sep 03, 2008 at 09:24:04PM -0700, Nathan Way wrote: >>> >>> http://www.freebsd.org/security/security.html#supported-branches >>> To quote from the above web site: (snip) > > On Sep 4, 2008, at 6:36 AM, Wesley Shields wrote: >> >> These are the existing releases. I believe Jo was looking for EoL for >> 7.1 and 6.4 once they are released. > > Yes, thank you. > To quote from the same website: Early adopter Releases which are published from the -CURRENT branch will be supported by the Security Officer for a minimum of 6 months after the release. Normal Releases which are published from a -STABLE branch will be supported by the Security Officer for a minimum of 12 months after the release. Extended Selected releases will be supported by the Security Officer for a minimum of 24 months after the release. I don't remember seeing any speculation about 6.4 being an extended release, so, EoL is 12 months after release, whenever that actually happens. I thought this was mentioned in the previous thread you started about EoL, but I didn't see it in a quick search. >> The answer to that is not clear - >> nor do I know if it should be clear yet. I don't know when the type of >> support decision is made, but I suspect it's not this early in the >> process. > > > The release date for 6.4 is ~30 days away, isn't it? > > Also given that we've previously seen overlaps such that a newer version is > only supported to the same EoL as the older version, that would pretty much > dictate that spending resources on testing 6.4-REL and/or upgrading would be > futile. > That's the difference between a long-term-support branch and a regular branch; many OSes do that. If you want to run the same machines for a long time and not have to do a huge battery of tests (at the expense of getting new features and better performance in the interim), you use long-term branches. The regular branches that get released later, will then become unsupported at the same time as the (older) long-term branch. Yes, it's poor when a long-term branch goes EoL before there's another one ready to take its place, but if the new one isn't ready, then you just use whichever regular release is current and then snag a long-term release when it becomes available. Yes, it's more work, but that's life. -Ben Kaduk