From owner-freebsd-stable@FreeBSD.ORG Tue May 29 19:53:32 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 71B8716A473; Tue, 29 May 2007 19:53:32 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 2242613C4B0; Tue, 29 May 2007 19:53:31 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l4TJrSu2056728; Tue, 29 May 2007 13:53:29 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <465C84B5.10500@samsco.org> Date: Tue, 29 May 2007 13:53:25 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: Colin Percival References: <465BF62B.6090904@vwsoft.com> <20070529102929.GA49322@owl.midgard.homeip.net> <465C06CE.6000703@delphij.net> <465C4624.5020004@freebsd.org> <465C49B5.8080003@freebsd.org> In-Reply-To: <465C49B5.8080003@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Tue, 29 May 2007 13:53:29 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: "Bruce A. Mah" , 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, 29 May 2007 19:53:32 -0000 Colin Percival wrote: > Bruce A. Mah wrote: >> We've done point releases in the past but only in cases where there were >> severe problems and/or regressions with released versions. Look at the >> announcements and release notes for 4.6.2-RELEASE and >> 5.2.1-RELEASE...these were the two most recent instances where we did >> this. There's a reason for this...it's a lot of effort. >> >> Folks should realize that making a new release (even a new point >> release) is not just a matter of tagging the tree and typing "make >> release". We (re@) need to figure out exactly what bugs are to be >> fixed, get the changes merged and tested, build at least one release >> candidate, get that tested, and finally build a set of RELEASE bits and >> push them out. > > I point releases have been obsoleted by errata notices. In the past when > X.Y.Z-RELEASE has happened, it has been because of critical bugs in the > X.Y-RELEASE which there wasn't any other mechanism to fix. Now that we > have errata noticed and FreeBSD Update is in the base system, it's vastly > easier for users to run "freebsd-update fetch install" than it is for them > to upgrade to a new release. > Not really. 5.2.1 existed because people were having problems getting 5.2 installed on their ATA disks. If you have big problems with storage or network, freebsd-update isn't going to be of much use to you. Scott