Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26657
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.82.226 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:in-reply-to:references:mime-version:x-priority:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=Jav8P/CMgMxboAY3dChpWdOMQNm+bw+Sh0BP+3tOfrxai4pSrpbju33uz6bKU1OODZGtE2exN9ibIvbe8rR4QD37UTMJPd8fKgm30koVOPJrRiRO/1DxNBrHynRkDi7w+HZM4vOGP4Mf1PQsR5HMbFDZ+NvtB4B9AJTFQ/VUBSg=
In-Reply-To: <1B.00.60908.40E6D554@pb1.pair.com>
References: <4554AE0D.4080600@caedmon.net>    <D268FFAD-6916-4EDE-9511-31F5BC774318@prohost.org>    <4554B9B5.5090305@caedmon.net>    <DA611470-FC2C-48DE-AE6B-29EC4554A298@prohost.org>    <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> <1B.00.60908.40E6D554@pb1.pair.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <1BDB7D8E-0408-48BF-BA9C-DD74D1A60E9C@prohost.org>
Cc: internals@lists.php.net
Content-Transfer-Encoding: 7bit
Date: Fri, 17 Nov 2006 10:24:18 -0500
To: "Ron Korving" <r.korving@xit.nl>
Sender: Ilia Alshanetsky <iliaal@gmail.com>
Subject: Re: [PHP-DEV] Namespaces in PHP 6 - ++$take
From: ilia@prohost.org (Ilia Alshanetsky)

Majority of the "bogus" bugs are truly bogus, I see no reason to  
change a perfectly valid term used to describe bugs.


On 17-Nov-06, at 2:38 AM, Ron Korving wrote:

> 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" <rasmus@lerdorf.com> 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
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

Ilia Alshanetsky