Hi Graham Cobb, Thanks for reporting bugs for MeeGo at first.
In my understanding, the INVALID means this is not a bug. This situation may be caused by some behaviors (you look them as bug) are: #1 mis-operation by users #2 by design in purpose #3 features request but we will not to support #4 misunderstood between user and app behavior (or you can say this is usability bug, and this can be reported to UI design team for review) Based on above definition, I reviewed the 3 bugs: 1. Bug 2705: I don't think it is INVALID. If developer think it is fixed in 1.1, he should not change *version*. And for 1.0, the issue is still there. Suggestion: please feel reopen the bug and comment your concerns on the bug. 2. Bug 3058: This is relevant to the rules #4 above. Your expectations and app behavior are not same. Of course you can look this one as bug and change the category to "UI Design", and involve designer to get more thinking about it. But for developers, who implement software, they can see it as INVALID. Suggestion: you can reopen it and change the bug to *UI Design* catalog if you want more information from UI Designer. 3. Bug 446: I agree with you this bug should be keep open until the documentation updated correctly in correct place. Suggestion: you can reopen this bug if you found the documents are still not correct. And furthermore, you can add comments on the bug to describe your concerns about bug resolution. Thanks, Lei Y MeeGo QA team -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Graham Cobb Sent: Monday, July 12, 2010 5:06 PM To: [email protected] Subject: [MeeGo-dev] Bugs being incorrectly closed as INVALID 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 _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
