From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 22:04:40 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 96BC81065675 for ; Mon, 22 Sep 2008 22:04:40 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 1F79F8FC17 for ; Mon, 22 Sep 2008 22:04:40 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 26415 invoked by uid 399); 22 Sep 2008 21:37:59 -0000 Received: from localhost (HELO ?192.168.0.12?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 22 Sep 2008 21:37:59 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <48D81034.6080607@FreeBSD.org> Date: Mon, 22 Sep 2008 14:37:56 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Dylan Cochran References: <1219409496.10487.22.camel@bauer.cse.buffalo.edu> <20080904133604.GB1188@atarininja.org> <47d0403c0809051319r3c82f87bhdb15ce5b0167987a@mail.gmail.com> <2742CAB1-8FF2-425D-A3B6-0658D7DB8F4D@netconsonance.com> <0C2C7E9B-61E3-4720-B76F-4745A3C963DA@netconsonance.com> <658B8861-1E78-4767-8D3D-8B79CC0BD45F@netconsonance.com> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Benefits of multiple release branches (Was: Re: Upcoming Releases Schedule...) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@freebsd.org 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 22:04:40 -0000 Dylan Cochran wrote: > One of the biggest (and most prominent, though not obviously so) > issues is the lack of concurrency with regards to releases. With the > default system, having multiple freebsd releases side by side (both > different versions, and different architectures) is infeasible. This > makes the choice more critical, while hindering flexibility. The > necessity of long support schedules is one of the symptoms. While on the one hand I can understand the users' frustration on this point, IMO having at least 2 release branches is necessary. We are trying to walk the fine line between pleasing those who want new features (including new drivers), better performance, etc. that a newer release branch offers (in this case 7.x) and those that want long-term API stability, and other forms of stability that an "established" release offers. The only practical way to accomplish both of those goals is with 2 release branches. Speaking only for myself, Doug -- This .signature sanitized for your protection