Comment 1 for bug 628678

First we need to identify when is something a bug or a blueprint...
Once it is classified as a bug i think we should follow this pattern:

STATUS:
------------
* NEW: No one had a look and no discussion took place yet.
* INCOMPLETE: The bug has insufficient info for us to be able to reproduce it, or verify its existence.
* OPINION: ???
* WON'T FIX: ???
* CONFIRMED: The bug can be reproduced.
* TRIAGED: Source of bug has been found.
* IN PROGRESS: A developer is developing a fix for it in a new branch.
* COMMITTED: The bug fix landed in trunk.
* RELEASED: The bug has been rolled out with the latest tarball.

IMPORTANCE:
-------------------
* UNDECIDED: No decision has been taken on the necessity of fixing the bug.
* WISHLIST: ???
* LOW: ???
* MEDIUM: The expected results are not delivering as supposed to .
* HIGH: The bug represents a resources, a performance problem for the users.
* CRITICAL: The bug represents a crash or a build error that makes Zeitgeist unusable.