From owner-freebsd-rc@FreeBSD.ORG Fri May 12 00:24:35 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4819416A50A for ; Fri, 12 May 2006 00:24:35 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [80.237.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60CC243F02 for ; Thu, 11 May 2006 23:59:11 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: (qmail 13179 invoked by uid 0); 11 May 2006 23:57:55 -0000 Received: from erdgeist.org (erdgeist@erdgeist.org@80.237.196.15) by elektropost.org with AES256-SHA encrypted SMTP; 11 May 2006 23:57:55 -0000 Date: Fri, 12 May 2006 01:57:54 +0200 (CEST) From: Dirk Engling To: Brooks Davis In-Reply-To: <20060511205124.GA17701@odin.ac.hmc.edu> Message-ID: <20060511231504.K84453@erdgeist.org> References: <20060508185155.H84453@erdgeist.org> <1147106428.2570.9.camel@localhost> <20060509124442.E84453@erdgeist.org> <1147171780.4810.19.camel@mayday.esat.net> <4463760F.7010304@erdgeist.org> <1147367711.80625.24.camel@localhost> <20060511203018.R84453@erdgeist.org> <20060511205124.GA17701@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-rc@freebsd.org Subject: Re: New jail_interface broken in 6.1-RELEASE X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2006 00:24:54 -0000 On Thu, 11 May 2006, Brooks Davis wrote: > The Q/A process is that users download the BETA and RC releases and test > the feature they care about. Unless someone out of the blue gives us > tens of millions of dollars to hire a massive testing staff there is > no other option. If you depend on a critical feature that isn't used > by the average user you need to either test it or risk this happening. > This is not idea, but that's the world we live in. I _did_ in fact test 6.1. I tested it since 6.1-BETA, every test release there was. So I _know_, new features, apparently untested and buggy, were introduced to RELENG after RC2 went out. So this "millions of dollar"-story is a rather lame excuse. When I declare release candidate I declare feature freeze. So I can simply forbid any commits or merges to my release branches as long they are not bug fixes. You do neither need a huge staff to do that, nor millions of dollars. Just a policy you even can enforce automatically. That would improve Q/A, in my eyes. I can see your point. If every arbitrary user starts complaining over any tiny bug breaking some esoteric features, you'd never achieve anything. However, if no one ever complains for fear of offending volunteers, Open Source Software dies of mediocracy. Regards erdgeist