From owner-freebsd-stable@FreeBSD.ORG Tue Jun 5 22:10:05 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 E91CD16A421 for ; Tue, 5 Jun 2007 22:10:05 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 53D3713C45E for ; Tue, 5 Jun 2007 22:10:05 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so340831uge for ; Tue, 05 Jun 2007 15:10:04 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=aW1+QNb/20QxLNY4f4Il81apv+QfqghLpsSxDCv7ObuhPZ4c/XftMFm08QNpUq1iq9GUDrFtsmutCDE1eGxwP/zx/sPMktf0XC5wI1PJMBN3s1Ra2Y27AYbmtCzoZDozT5cRrqkvxwmIbeu/HEbySgjMJ3gEmoO3mSbGF1QawTY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OyBuZ1DWiLNCjBqaYD5ILgl3mQWaBWmdO5b2cIl3jNMfaw8M1llP0fmPCRAOqZb73/qo181vglyoqHn6YmqIZW2Yk61wIBmVQ1eLAK1l36sWuyNHi5KnMqscrVD0xi4soVK9+r4iVdoqbTKc06LhuUSDWJ7sqHx6/FO/Nx4GJac= Received: by 10.67.115.11 with SMTP id s11mr754856ugm.1181081403928; Tue, 05 Jun 2007 15:10:03 -0700 (PDT) Received: by 10.66.241.12 with HTTP; Tue, 5 Jun 2007 15:10:03 -0700 (PDT) Message-ID: <3aaaa3a0706051510y3c897c26p16e6d1d6fa0bf660@mail.gmail.com> Date: Tue, 5 Jun 2007 23:10:03 +0100 From: Chris To: "Doug Barton" In-Reply-To: <46647C25.80307@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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> Cc: stable@freebsd.org 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:10:06 -0000 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. Chris