Canmove, confirm
1,343
edits
Changes
→Following a component
== Following a component ==
We've noticed that when a bug is taken into account very shortly after it's creation, bug openers where were following the bug more closely.
We would like to be more responsive - as in answer initial bug reports faster.
Following a component is juts following a subset of bugs in bugzilla. And interacting with the bug reporters.
=== setup ===
You'll need a bugzilla account of course. In the email settings just select to follow on one of these [https://bugzilla.mozilla.org/describecomponents.cgi?product=Thunderbird QA contacts] or [https://bugzilla.mozilla.org/describecomponents.cgi?product=MailNews%20Core these] fake email addresses.You can also do it just using [https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch bugzilla's Preferences]
=== Which component to follow ===
We think it's important that helping us should be fun. The first component that you should follow, should be something you care a lot about Thunderbird. This will make you more confident on how to use bugzilla and how to deal with following a component. Once you feel comfortable with that, ask us and we'll tell you which one need more attentions then others.
=== How do easily deal with new bugs ===
# Are these local or imap folders
With that you are gathering important information. The first two question let you rule out or not if the bug is related to an add-on.If it works in -safe-mode then an extension or theme is responsible for the bug. If it is the bug can be closed as INVALID - as extensions should be fixed by the extension authors. The second question might help diagnose what the issue is - but rarely helps :( The last question is a good starting point to try to reproduce - as once you've reproduce you can confirm the existence of the bug. If you can't reproduce say , so in a bug comment. You might also want to ask for precisions (ie on windows is there an anti-virus program running etc ...)
== Docs ==
