bug resolution definitions

[jed jed]

Hey all,

A few people may get this twice because I'm sending to both the development and testing lists, but it's pretty useful information to keep us all communication in the same way.  Also, as new people join in on the project it will help prevent and bugs getting lost in the process.

Basically - I just wanted to share our PCF-specific definitions of what the bug resolutions fields mean.  For any bug, you can click the status link and it will take you to the definitions: http://bugzilla.pculture.org/page.cgi?id=fields.html#status

Here's a quick view:

FIXED

A fix for this bug is checked into the tree and has been tested or unit tested. FIXED bugs should always include a link to the relevant commit. Bug is now in the queue to be verified by a card-carrying member of the special forces QA team.

INVALID

The problem described is not a bug.

WONTFIX

The problem described is a bug which will never be fixed.

DUPLICATE

The problem is a duplicate of an existing bug. Marking a bug duplicate requires the bug# of the duplicating bug and will at least put that bug number in the description field.

WORKSFORME

All attempts at reproducing this bug were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the bug can be reopened. Alternatively, this can also be used for a bug that cannot be reproduced but we're pretty sure it was a bug and has been fixed.

MOVED

The problem was specific to a related product whose bugs are tracked in another bug database. The bug has been moved to that database.

INCOMPLETE

Additional information has been requested from the original reporter or recent commenter. No new information has been added to the bug for more than 2 weeks.

Few things to point out: 

1. If there is some back and forth between test and development and a bug has been REOPENED after being FIXED.  If the reason for the Reopen was invalid, the bug should still be marked as FIXED by dev or tester since there was a code change involved in the original fix and that needs verification.
2. For bugs that get marked as WORKSFORME, or INVALID it's the responsibility of the original reporter to dispute it, (ie reopen) if they believe there is still a reproducible issue.
3. DUPLICATE should always have the real ticket number of the bug it's duplicating
   
4. Only bugs that are marked as FIXED get retested by QA and subsequently marked as VERIFIED, meaning it passed testing.

Janet