Three of my nine bug reports have now been incorrectly closed as INVALID.  I'm 
not precious about resolution status, as long as problems are reported and 
then resolved but this seems to have got out of hand.  Just in case anyone is 
using the statuses in any sort of reports it would be useful if we were all 
provided some guidance in the use of the correct resolution reasons!  The 
Bugmaster (do we have one for MeeGo?) might also like to occasionally review 
some of the RESOLVED bugs to make sure their status is correct and fix ones 
which are not (with a comment, so that both submitter and developer 
understand what status should have been used and why).

Bug 2705 is the most ridiculous -- it was closed as INVALID because the fix 
was already in git but will not be available until the 1.1 release!  It 
should have been closed as FIXED.  Bug 3058 should have been closed as 
WONTFIX.  Bug 446 should not have been closed at all until the documentation 
in the Wiki had been updated, then it should have been closed as FIXED (in 
the end, I fixed the documentation myself after the developer closed the bug 
as invalid).

Either don't use statuses at all or use them correctly.  If we need more 
statuses, then add them.  The INVALID status should be reserved for bugs 
which are incorrectly formatted, spam, insufficient information, etc.  It is 
not reasonable to use it for genuine and meaningful bug reports even if you 
disagree that they are a bug (that is what WONTFIX is for).  It is even less 
correct to use it for bugs you have actually fixed!!

Graham
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to