Re: Namespaces in PHP 6 - ++$take

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