Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26654 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62383 invoked by uid 1010); 17 Nov 2006 08:08:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 62368 invoked from network); 17 Nov 2006 08:08:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Nov 2006 08:08:38 -0000 X-Host-Fingerprint: 195.225.34.5 fw01.axit.nl Received: from [195.225.34.5] ([195.225.34.5:2768] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1B/00-60908-40E6D554 for ; Fri, 17 Nov 2006 03:08:37 -0500 Message-ID: <1B.00.60908.40E6D554@pb1.pair.com> To: internals@lists.php.net References: <4554AE0D.4080600@caedmon.net> <4554B9B5.5090305@caedmon.net> <4554C2C7.9070502@caedmon.net> <4554C945.3000509@velum.net> <20061111135517.zqn0qes34sk4444c@neo.wg.de> <4555D20F.8060903@lerdorf.com> <1821.208.195.234.246.1163626505.squirrel@www.l-i-e.com> <455CB6BD.2080806@lerdorf.com> Date: Fri, 17 Nov 2006 08:38:18 +0100 Lines: 40 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-RFC2646: Format=Flowed; Original X-Posted-By: 195.225.34.5 Subject: Re: [PHP-DEV] Namespaces in PHP 6 - ++$take From: r.korving@xit.nl ("Ron Korving") Why not add another bug-status called "incomplete" or something, and append a standard message saying "Please study the bug-reporting guidelines in order to write complete and accurate bug reports."? I think this tiny addition to tagging something "bogus" would make a lot of bug reporters happier and it might make them fix their bug report. -- Ron "Rasmus Lerdorf" schreef in bericht news:455CB6BD.2080806@lerdorf.com... > Richard Lynch wrote: >> On Sat, November 11, 2006 7:37 am, Rasmus Lerdorf wrote: >>> helping to get rid of bogus reports or translating the really bad >>> reports into a simple reproducable test case is often the part that >> >> This is a plea for not being quite so bogus-trigger-happy as we have >> in the past. >> >> Many correct, if incomplete, bug reports get quickly labeled "bogus" >> with no real research, and that only makes it even harder for anybody >> to do anything useful... >> >> I know it's [hard] work to wade through those things, to some degree, >> but you make your life more miserable with incorrect assessment. :-) >> >> Please do not take this request amiss! It is an attempt, however >> small, to make your life better, not to complain about your efforts! > > I think lagging 6-12 months behind on bug reports would be much worse. > If the bug report is incomplete and isn't likely to lead to a resolution > I think it is better to let the reporter know sooner rather than later. > The fact that we only have 2 or 3 people regularly looking at these and > the flow of them is ever increasing doesn't leave us with much choice > here. If more people helped out we could spend more time on each one, > but until that happens, the quick-bogus is going to continue. > > -Rasmus