Re: RFC: A little 'howto' about bug system status's.
| From: | Zak Greant | Date: | Mon, 02 Oct 2000 20:32:47 +0000 |
| Subject: | Re: RFC: A little 'howto' about bug system status's. | ||
| References: | 1 | Groups: | php.dev php.qa |
| Request: | Send a blank email to php-dev+get-34093@lists.php.net to get a copy of this message | ||
At 11:26 PM 10/2/00 +0300, Jani Taskinen wrote:
Okay, I asked this a while ago so I should propably go on writing it also. 'Duplicate' The report is either bogus (e.g. empty) or send accidently twice or more. !!! Reports marked as duplicates are deleted from database from time to time. !!!Ah... I have always assumed that this meant the bug was a post about a bug that has already been reported. If this is the common usage (which it may be by now, due to the sheer number of bug reports that you handle :) then perhaps it should be renamed to "Invalid"... If a bug is bogus or a duplicate, then I would close it with a note stating that it was bogus.
'Open' Bug report is new / nobody is working on it. 'Closed' Bug is either fixed or there is no bug or user doesn't respond to feedback requests. 'Assigned' Someone is working on it (either fixing code or trying to reproduce, etc.) 'Analyzed' Real Bug (tm) (someone has confirmed that bug actually exists) 'Suspended' The bug is analyzed and the fix is something that isn't in our hands but might get fixed eventually (third party software?), or the fix is going to be in the next _major_ version of PHP or the fix needs something else to be fixed first. 'Feedback' Waiting for user feedback (e.g. more info) 'OldFeedback' After 60 days of 'feedback' status the status is automaticly changed to this. And the one status that is missing IMO: 'Similar to' The report describes the same assumed bug.That makes sense - anyone have any issues about me adding this (along with the content of this this message after everyone has had a kick at it :) to the bugs page? - zak