From owner-freebsd-current Tue Feb 19 11:32:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 5403637B400 for ; Tue, 19 Feb 2002 11:32:16 -0800 (PST) Received: from [212.238.194.207] (helo=mailhost.raggedclown.net) by post.mail.nl.demon.net with esmtp (Exim 3.33 #1) id 16dFzp-00078S-00 for current@freebsd.org; Tue, 19 Feb 2002 19:32:13 +0000 Received: from angel.raggedclown.net (angel.raggedclown.intra [192.168.1.7]) by mailhost.raggedclown.net (Ragged Clown Mail Gateway [buffy]) with ESMTP id D27D413040 for ; Tue, 19 Feb 2002 20:32:11 +0100 (CET) Received: by angel.raggedclown.net (Ragged Clown Host [angel], from userid 6002) id B8ED022596; Tue, 19 Feb 2002 20:32:11 +0100 (CET) Date: Tue, 19 Feb 2002 20:32:11 +0100 From: Cliff Sarginson To: current@freebsd.org Subject: Re: more -current testers Message-ID: <20020219193211.GA1785@raggedclown.net> References: <20020219125011.A15871@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020219125011.A15871@blackhelicopters.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 19, 2002 at 12:50:11PM -0500, Michael Lucas wrote: > I understand that we're getting to that stage where we need more > -current testers. > > We all agree that the optimal thing would be to have hordes of very > sophisticated users who can debug problems on their own and submit > patches to fix all their issues. I would guess that we all also agree > that that's not going to happen. > > It seems that the best we can hope for is to educate some of the > braver users who are ready to take the next step and are willing to > donate some time to us. > > I'm considering doing a series of articles on testing FreeBSD-current, > including: setting up for kernel dumps, what to type at the debugger > prompt after a crash, filing a decent bug report, what to expect from > -current, and so on. I would also make it clear when to not bother > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, > enable WITNESS & try again."). This would be (I suspect) three > articles, running about a month and a half. > > The last time I checked, I get 12-15 thousand readers for each > article. One half of one percent uptake would (hopefully) be quite a > few bug reports. > > My question to the community is: is it too early to do this? If I > start now, the articles would probably appear April-May. I think this is an absolutely splendid idea :) I have enough resources to run a STABLE system for my day-to-day use and also have a -CURRENT system I am more than willing to spend some time on. I think some good pointers on what is required to provide useful feedback (as opposed to bug reports that are not adequately filled in) and some practical tips would really encourage people. My first question is who or what is WITNESS :) -- Regards Cliff Sarginson -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message