Comment 3 for bug 997637

Hi Dan.

I think your suggestions are good. I think they might be written a little differently:

Bug importance is about organising work. We often image the work we do as a queue. The are some complications because the names we used are so generic that they do not work with any project's model of organisation. Projects with a lot of bugs (more bugs than can be fixed by the contributors in a year) only commit to work on bugs that are critical or high. small projects, which can empty the queue of bugs, will schedule medium bugs. We can image the top three importances as inserting bugs at the top, middle and bottom of the queue.

    * Critical: Fix now or as soon as possible.
    * High: Schedule to be fixed soon.
    * Medium: Fix when convenient, or schedule to fix later.
    * Low: Fix when convenient.
    * Wishlist: Not a bug. It's an enhancement/new feature.
    * Undecided: Not decided yet. Maybe needs more discussion.

I am concerned about the definition on incomplete. It is not just a request for information, The issue is that the bug cannot be demonstrated to exist so more information is needed. There was a historic problem where project did use incomplete to mean someone wants more information from the reporter, then Lp would expire the bug because it is not a bug. Opinion is the same as wont fix, but is deemed politer and Lp was asked to remove it.

    * New: Not looked at yet.
    * Incomplete: Cannot be verified, the reporter needs to give more info.
    * Opinion: Doesn't fit with the project, but can be discussed.
    * Invalid: Not a bug. May be a support request or spam.
    * Won't fix: Doesn't fit with the project plans, sorry.
    * Confirmed: Verified by someone other than the reporter.
    * Triaged: Verified by the bug supervisor.
    * In Progress: The assigned person working on it.
    * Fix Committed: Fixed, but not available until next release.
    * Fix Released: The fix was released.