From owner-freebsd-current@FreeBSD.ORG Thu Oct 13 16:44:57 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA9D416A41F for ; Thu, 13 Oct 2005 16:44:57 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8E6843D45 for ; Thu, 13 Oct 2005 16:44:57 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 85EE82F2B; Thu, 13 Oct 2005 11:44:56 -0500 (CDT) Date: Thu, 13 Oct 2005 11:44:56 -0500 To: Andy Hilker Message-ID: <20051013164456.GA11820@soaustin.net> References: <434BCDF6.3090303@samsco.org> <1129201350.13257.9.camel@myfreebsd.homeunix.org> <20051013155511.GA1748@mail.crypta.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051013155511.GA1748@mail.crypta.net> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Fri, 14 Oct 2005 12:12:50 +0000 Cc: current@freebsd.org Subject: Re: FreeBSD 6.0-RC1 available X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2005 16:44:58 -0000 On Thu, Oct 13, 2005 at 05:55:11PM +0200, Andy Hilker wrote: > Is it possible to include this minor patch for rc-ng scripts? It > ist present since 5.3 or earlier... I hate to pick on any particular poster, but, folks ... We're at the tail-end (I **hope**) of a release cycle that began (if you take 'src freeze' as 'began') on 10 June 2005. This means we just entered the 4th month of it (2.5 of which have been in either ports freeze or thaw). For comparision 5.3 ran from 16 Aug 2004 to 5 Nov 2004, in which ports was frozen or thawed for 2 months. (And we thought _that_ hurt at the time!) This long cycle is really putting the ports team at a disadvantage because there are certain thing we just can't do in a thaw, and all we do during freezes is bugfixes. The first rule of software engineering is that "the final product will have bugs" and the second rule of software engineering is "eventually you have to ship a product". If we held off any release until GNATS was empty we could just all stop now because they arrive faster than we have current volunteers to fix them. People really need to be realistic about what can and can not be fixed and when. Once you're already 2 months past your initial deadline, and counting, the only things that should be going in are things that would otherwise be completely deadly to us. Everything else is going to have to catch the next train because this one is pulling away from the platform. End of rant. No, I'm not on Release Engineering, so I can't speak for them. OTOH I _do_ have many (too many) years of professional experience and I _can_ speak for it. And again, this is not directed at OP, there's been several people within a couple of days asking almost the exact same question. mcl