Thunderbird:Bug Triage

<< Back to Thunderbird Testing

This document changes frequently. To be notified of changes either [Login] and set a Watch, or use [Wiki RSS]

The purpose of this document to assist anyone interested in helping improve Thunderbird through the process of triaging of Thunderbird bugs. Triage of and resolution of bugs helps drive both the quality of the product and the development process, and thus has a great impact on user satisfaction. The goal of triage is to either close the bug as no longer useful or invalid, or move it to a high state of quality where a developer can take action to fix and resolve it.

What's great is anyone can help, no matter how little or how extensive your experience with the product, with QA, with code, or with triaging. And there are plenty of people to help you in this process. No prior experience is needed.

The current state of Thunderbird bugs is mixed, so we can use your help. Many are actively being worked on by developers or are of high enough quality for any coder to pick up the bug and work on it. But, there are many unconfirmed (UNCO) bugs and bugs of poor quality - in a confirmed state but very old and in need of reevaluation.

Contributing, aka How you can help with Thunderbird bugs

In general:

• Don't have elevated Bugzilla privileges canconfirm or editbugs? (if you don't know what these are then you don't have them) Then we suggest as you comment in bugs and file new ones, that you work toward getting your privileges. See simple instructions on how to get these privileges. (Note: privileges not needed to just comment in bugs.)

• Triage and comment in existing bug reports to either improve the quality or to prove or disprove that the bug exists. x

• cc: yourself (without comment) on bugs you care about or can help in the future but can't help just now.

• File a new bug if you have a problem that hasn't been reported, or an existing bug report mentions more than one problem that do not have a bug filed.

• Help with Testing and QA of future versions and updates

• Help with Thunderbird Bug Days

Triage Process

From canned the Thunderbird bugzilla queries, or your own query, pick the type of bugs you are interested in or presently have trouble with. If you don't have a specific interest, we provide bugs that are deserving of interest and care.

Then, use the well established triage process, working by yourself or in tandem with the reporter and others in the bug, to evaluate and/or improve the bug, and help drive it to a successful resolution.

Especially:

• Add or improve steps to to reproduce
• Determine if a bug exists on a newer release, or trunk build
• Confirm or resolve the bug if you have privileges

Triage Resources, Tools and Hints

• Builds
  • [Hourly builds] - to test a patch that a developer just landed
  • [Nightly builds aka nightlies] - the bleeding edge
  • [Archives of Branch Releases]
  • [An explanation about versions and builds for testing...]
  • see also builds forum below
• bugzilla
  • [What and what not to do in Bugzilla]
  • bookmark shortcuts
• Crash reports for [branch builds @talkback], trunk builds @crash-stats] (note: NTT extension provides direct links to your crashes)
• extensions useful in debugging and/or triage
  • thunderbird: [Nightly Tester Tools aka NTT], [Profile Switcher]
  • firefox: [Nightly Tester Tools aka NTT], [TinyURL Creator], [greasemonkey]
    • greasemonkey scripts
• Discussion and Help (for Testing and QA)
  • mozilla.dev.apps.thunderbird newsgroup
  • [IRC chat] -- general QA help: #qa channel -- mail developers: #maildev channel
  • [Weekly developments in Mozilla Thunderbird builds]
  • [Daily Build Thread], and in [RSS]
  • [Builds Forum] - The testing community at Mozillazine
• News and Archival Information
  • [Releases Tracking] - schedule, plan and bugs fixed
  • Thunderbird Release Changelogs]
• Miscellaneous
  • Excellent [Glossary]
  • http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html#unconfirmed

Canconfirm and Editbugs Privileges

To get elevated privileges to triage Thunderbird bugs ...

If you don't have canconfirm privilege (which allows you to create bugs in a New state and confirm other's bugs by changing them from Unco to New) do one of the following:

• If you haven't filed many bugs, go through all the steps under "Confirm the Unconfirmed" for three bugs.
• Mail the full URLs of the bugs.
• If everything looks okay, you'll then get the "can confirm a bug" privilege.

To get "editbugs", allows you to edit most aspects of a bug, mail either:

• The URLs of two bugs to which you have attached patches or testcases; or
• The URLs of the relevant comment on three bugs which you wanted to change, but couldn't, and so added a comment instead.

Bugs you probably do not want to not use towards getting your privileges :

• CLOSEME in whiteboard - many are trivial and/or lack much useful information
• Bugs about moving and copying messages - often not easily verified (Exception: if you personally experienced the problem in the time frame described by the reporter(s), and therefore in a good position to say whether the problem does or does not exist today on a newer release.)

See / add useful information