From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 22:32:09 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 D140D10656AC for ; Thu, 5 Jun 2008 22:32:09 +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 795178FC26 for ; Thu, 5 Jun 2008 22:32:07 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local (pooker.samsco.org [168.103.85.57]) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m55MW3i9022749; Thu, 5 Jun 2008 16:32:03 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48486962.7030001@samsco.org> Date: Thu, 05 Jun 2008 16:32:02 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Jo Rhett References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846E637.9080101@samsco.org> <48472DB6.5030909@samsco.org> <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> <484736E0.6090004@samsco.org> <74EB4162-74CB-4591-B7E5-8156BB56C29E@netconsonance.com> In-Reply-To: <74EB4162-74CB-4591-B7E5-8156BB56C29E@netconsonance.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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: Thu, 05 Jun 2008 22:32:10 -0000 Jo Rhett wrote: > On Jun 4, 2008, at 5:44 PM, Scott Long wrote: >> Really, if it's such a big issue that you have time to bitch an moan >> on the mailing lists, I don't understand why you don't have time to also >> help a goddamned developer identify the problem. Are you actually >> experiencing problems with 6.3, or not? > > > None of the bugs were in a state with the developer trying to identify > the system. We have several systems dedicated for FreeBSD developers to > use for test cases already, and we'd be happy to provide another if one > was necessary. > What is needed prior to talking about loaner systems and test cases is for you to say, "Hardware XYZ isn't working for me anymore. It used to do FOO, and now it does BAR." That's the first step. It's a simple step, but it's an essential step. Seriously. And if you aren't actually experiencing any problems, then all I can say is that your input on the release and support process has been noted, and we all look forward to bug reports from you in the future. And before you circle back on the "but but but the PR database shows unresolved bugs" argument, understand that few of us on this mailing lists are idiots; we know how to read, and we are aware that there are PR entries. What pushes a stalled PR along, though, is having an interested party bring it up and offer insight into the specifics of it. Just pointing from afar adds nothing to the process. You're welcome to disagree on that point, but it seems pretty clear that continuing to argue it in this forum isn't really solving anything. So I'll try one last time.... you seem to be concerned about possible bugs in the the 3ware and broadcom drivers. Can you please provide specifics on what you are concerned about? Any personal insight or experience you have would be highly helpful and appreciated. Scott