From owner-freebsd-stable@FreeBSD.ORG Tue Jun 5 22:14:12 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 17E9116A41F; Tue, 5 Jun 2007 22:14:12 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 06AF013C46A; Tue, 5 Jun 2007 22:14:12 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C24E11A3C19; Tue, 5 Jun 2007 15:15:29 -0700 (PDT) Received: from rot13.obsecurity.org (rot13.obsecurity.org [192.168.1.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 49E6D513AE; Tue, 5 Jun 2007 18:14:11 -0400 (EDT) Received: by rot13.obsecurity.org (Postfix, from userid 1001) id 347F4C207; Tue, 5 Jun 2007 18:14:11 -0400 (EDT) Date: Tue, 5 Jun 2007 18:14:11 -0400 From: Kris Kennaway To: Chris Message-ID: <20070605221411.GA48199@rot13.obsecurity.org> References: <465BF62B.6090904@vwsoft.com> <20070529102929.GA49322@owl.midgard.homeip.net> <20070529111757.GE70055@turion.vk2pj.dyndns.org> <20070529182224.GD8255@soaustin.net> <3aaaa3a0706020045v1ce69a7bsec4a8dced2a99fe1@mail.gmail.com> <3aaaa3a0706041315q9e527b7n886dd73997cc5ac5@mail.gmail.com> <46647C25.80307@FreeBSD.org> <3aaaa3a0706051510y3c897c26p16e6d1d6fa0bf660@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0706051510y3c897c26p16e6d1d6fa0bf660@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: stable@freebsd.org, Doug Barton Subject: Re: release cycle 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, 05 Jun 2007 22:14:12 -0000 On Tue, Jun 05, 2007 at 11:10:03PM +0100, Chris wrote: > On 04/06/07, Doug Barton wrote: > >Chris wrote: > > > >> So my question remains when we have 7.0 and 6.3 both STABLE releases > >> will the ports tree not be supported in 6.3 a just released version of > >> FreeBSD? > > > >I can't help but get the impression that you're spoiling for a fight > >here, so let me ask you to take step 1, which is relax a little. > > > >You are focusing on released version numbers when you ask about ports > >support, and we generally focus on release branches. See > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html > >for more information about that. We will be supporting ports for > >RELENG_5 and _6, and RELENG_7 after it's created from what is now HEAD. > > > >Where I think the confusion is coming in is in regards to support for > >a specific version number that is older than the latest version in > >that branch. For example, support for 6.1 which is an older release on > >the RELENG_6 branch. We do our best to provide ports support for older > >versions on currently supported branches, but it's not always possible > >to do so. You can search the archives of the ports list for > >information on why just supporting 3 active branches (which will be 4 > >after RELENG_7 is branched) for over 16,000 ports is a pretty massive > >undertaking. > > > >I hope this makes the situation more clear. > > > >Doug > > > >-- > > > > This .signature sanitized for your protection > > > > > > This is what I had always thought until I was told otherwise recently > thanks. Not spoiling for a fight just trying to understand the > situation because it was dissapointing to be told last week that the > reason for a ommision in UPDATING was because 6.1 was not the latest > release. For this reason I wont dig up the quote I am just happy that > 6.3 will be supported. This is an orthogonal issue. Again, if you read the URL I gave (http://www.freebsd.org/ports/) it explains that older releases on a stable branch (whether 5.x, 6.x or soon to be 7.x) are not supported, although they may continue to work and we will accept patches from the user community to keep them working when they are accidentally broken by a change. Kris