On 15 Jan 2003 [EMAIL PROTECTED] wrote:

> Why has this bug been marked as Bogus when it's a Duplicate?  It seems
> to be increasingly common for this to happen -- when did it become
> standard policy to set duplicate report to Bogus?

Two exactly the same bugs were posted one minute after eachother from 
persons on the same domain. 

> This is very
> confusing, when there is still a Duplicate status in the system. 
> Surely, if a bug is a duplicate of another, it's far better to set its
> status to Duplicate, so that it's obvious from a brief look that it
> *is* a duplicate (and it shows up in search results as such).  Setting
> it to Bogus is bogus, because it's patently not Bogus if it's the same
> issue as an Open bug.

It was in this case.

> And even if it is policy to set duplicate report to Bogus, that policy
> should be prominently documented, so that people don't get in a huff
> about bugs being dismissed as not a bug when their duplicate report is
> set to Bogus (which has happened more than once already!).

People who dont understand the implicit meaning of the statii shouldn't 
touch the reports in the bug system. I'll write them down again:

bogus: submitted twice after each other, or by the same person on the 
       same topic; it's not a bug, but a support question. The reason 
       should always be noted in the comments
dupli: almost the same bug, both bugs are found 'duplicate' later on and 
       have both useful information
verif: a member of the QA has verified the bug to be a real one
analy: the cause of the bug is known, or a solution is known for it but
       not yet implemented
assig: don't touch this one, somebody is working on this. 
open:  just submitted, or nobody knows what to do with it (after 
       feedback)
feedb: Waiting for more feedback from the user
suspe: at some point in the future we'll look at it again, currently we 
       are waiting on an external thing to be fixed first
close: the bug has been solved (fixed in cvs)
wontf: we are not going to fix this issue because ....
criti: critical bug, should be fixed ASAP
no fe: No feedback from the user was added since we asked it two weeks 
       ago

if you;re not sure what status to set a report to, ask on the php-qa@ 
list!

regards,
Derick

-- 

-------------------------------------------------------------------------
 Derick Rethans                                 http://derickrethans.nl/ 
 JDI Media Solutions                             http://www.jdimedia.nl/
 PHP Magazine - PHP Magazine for Professionals       http://php-mag.net/
-------------------------------------------------------------------------



-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to