A brand new "in-litmus" flag has been added to (most) bugs in Bugzilla. For those of you who are familiar with the "in-testsuite" flag, "in-litmus" will work almost the same way, but for those of you aren't, here's a brief overview.

Yesterday I updated the bug watcher list on wiki.mozilla.org and also added myself to general@thunderbird.bugs to get notified of new bugs for this component.
Meanwhile I got some new messages. I had to search on Bugzilla to find
related bugs so I could dupe the new ones.
While searching the Bugzilla database I noticed that thousands of bug
reports have an old and unused default QA contact. People are gone over time or
there is even no entry made. These reports haven't got attention for a

Just a friendly reminder to our Mozilla developers to use the "qawanted" keyword for bugs.   If you would like some help with verifying bugs and regression, please be sure to fill in this keyword in your bugs.  We are particularly interested ones that flagged blocking-firefox 3 or blocking1.9 bugs.  Be sure to include steps to reproduce as always.

These are the current bug queries that QA is tracking:

Our project to lower the number of unconfirmed bugs has been very successful. A great thanks to all of our community members like stevee, aaronr, and aleksej for their help on lowering the number of unconfirmed bugs.

We have triaged a lot of bugs so far (over 1000 bugs in nearly a month!), but there is still a huge list of bugs to work on. So we still need your help!

For those community members that are new and want to help or want more information about this, please see the inital post.

Thank you for your report.

If you need general assistance, please see http://support.mozilla.com for
various documentation and community resources you can turn to for help with
your problem. Bugzilla is not such a resource - the purpose of Bugzilla is to
track bugs in the software so that they can be fixed by the developers.

It's important that Bugzilla is reserved for reporting actual problems with the
software, in enough detail that the bug report helps us fix the problem.

In working with Bugzilla, there are some issues that come up frequently enough that form replies are warrented. This section is an attempt to collect those topics and their replies.

http://developer.mozilla.org/en/docs/What_to_do_and_what_not_to_do_in_Bu...

http://wiki.mozilla.org/MozillaQualityAssurance:Triage
Triage is the process by which the flood of bugs in Bugzilla are classified, validated, and hopefully sent onward to developers for further action.  When triaging a bug report evaluate it with these points in mind:

• Ensure the bug is classified under the proper Product and Component in bugzilla for the issue it refers to
  

Bugzilla is the bug tracking system used by Mozilla projects, and as such many of the activities of Mozilla Quality Assurance revolve around Bugzilla.