Thunderbird:Bug Triage: Difference between revisions

Jump to navigation Jump to search
update - first cut
(Replaced ftp and http with https where it didn't make things worse.)
(update - first cut)
Line 3: Line 3:
''To be notified of changes to this page either [[https://wiki.mozilla.org/index.php?title=Special:Userlogin Login]] and set a '''Watch''', or use [[https://wiki.mozilla.org/index.php?title=Special:Recentchanges&feed=rss Wiki RSS]]''
''To be notified of changes to this page either [[https://wiki.mozilla.org/index.php?title=Special:Userlogin Login]] and set a '''Watch''', or use [[https://wiki.mozilla.org/index.php?title=Special:Recentchanges&feed=rss Wiki RSS]]''


The purpose of this document to assist anyone interested in helping improve Thunderbird through the process of triaging of Thunderbird bugs. The goal of triage is to either close a bug as no longer useful or invalid, or move it to a high state of quality - to a point where a developer can take action to fix it.
The document is a reference for anyone interested in helping improve Thunderbird through the process of triaging Thunderbird bug reports.  
Therefore triage, and your work, helps drive both the quality of the product and the development process, and ultimately impacts user satisfaction.  


What's great about triage is anyone can help - technical skills are not required, nor is extensive experience required. And there are many people to help you with the product, with QA, and triaging.
<u>The goal of triage is to close a bug as no longer useful or not a valid bug, or move it to a high state of quality - to a point where the bug has enough information for a developer to take action to fix it.</u>


In short, we need your help.  
What's great about triage is anyone can help - coding skills are not required, nor is extensive experience required. Being a user of Thunderbird is good enough.  And we have people who can help you. Your triage work can impact both the quality of the product and the speed of development process, and ultimately improve user satisfaction.
 
<u>But this doesn't happen without volunteers.  In short, we need your help.</u>


== Contributing, aka How you can help with Thunderbird bugs ==
== Contributing, aka How you can help with Thunderbird bugs ==


You can help, and we need you. You can:
Easy ways to get started:


* cc: yourself on bugs you care about, or perhaps can help with in the future but can't help right now.
* cc: yourself on bugs you care about, or perhaps can help with in the future but can't help right now.


* [[Thunderbird:Bug_Triage#Triage Process|Triage and comment in]] existing bug reports to improve the quality or to prove or disprove that the bug exists.  (Many bugs are unconfirmed (UNCO). And many "confirmed" bugs are of poor quality - for example very old and need to be evaluated again.)
* [[Thunderbird:Bug_Triage#Triage Process|Triage and comment in]] existing bug reports to improve the quality, or to prove or disprove that the bug exists.  (Primarily bug reports whose state is "unconfirmed/UNCO". Also, some old bug "confirmed" bugs are of poor quality and need retesting.)


* If you don't have Bugzilla privileges (canconfirm/editbugs) we suggest you [[#Canconfirm and Editbugs Privileges|work towards getting privileges]]. You can do this as you comment in bugs and file new ones. Note: anyone can comment in bugs - privileges are optional and not needed to ''just'' comment.
* If you don't have Bugzilla privileges (canconfirm/editbugs) we suggest you [[#Canconfirm and Editbugs Privileges|take steps to get privileges]]. A starting point is just adding good information to existing bug reports, or helping the bug reporter better define their bug. (anyone can comment in bugs - privileges not needed)


* File a new bug if you see a problem that hasn't been reported.
* File a new bug if you see a problem that hasn't been reported.


* Help with [[Thunderbird:Testing|Testing and QA of future versions and updates]]
* Help with [[Thunderbird:Testing|Testing and QA of future versions and updates]].


* Help with and have fun in [[Thunderbird:Bugdays|Thunderbird Bug Days]]
* Help with and have fun in [[Thunderbird:Bugdays|Thunderbird Bug Days]].


* More info and opportunities at [https://www.thunderbird.net/en-US/get-involved/ Mozilla Messaging - Get Involved]
* More info and opportunities at [https://www.thunderbird.net/en-US/get-involved/ Get Involved].


== Where to get help and places for discussion (for Testing and QA) ==
== Where to get help and places for discussion (for Testing and QA) ==
Line 42: Line 43:


Use the triage processes described in [https://developer.mozilla.org/en/Confirming_unconfirmed_bugs Confirm the unconfirmed] and [https://developer.mozilla.org/en/What_to_do_and_what_not_to_do_in_Bugzilla What to Do and Not]. Especially:
Use the triage processes described in [https://developer.mozilla.org/en/Confirming_unconfirmed_bugs Confirm the unconfirmed] and [https://developer.mozilla.org/en/What_to_do_and_what_not_to_do_in_Bugzilla What to Do and Not]. Especially:
* Add or improve steps to to reproduce
* Add or improve details steps to to reproduce.
* Determine if a bug exists on a newer release, or trunk build
* Determine if a bug exists on a newer release, or daily build.
* Confirm or resolve the bug if you have [[#Canconfirm and Editbugs Privileges|privileges]]
* Confirm or resolve the bug if you have [[#Canconfirm and Editbugs Privileges|privileges]].


Things you can add to Status Whiteboard:
Things you can add to Status Whiteboard:
* [closeme YYYY-MM-DD] - if you directed a question or gave instructions to a bug reporter, pick a date 2-4 weeks in the future to allow time for a response (see [[#Closemes|Closemes]])
* [workaround comment ##] - to indicate useful instructions
* [dupeme] - if you believe this is a duplicate of another bug, but don't know which one
* [[Thunderbird:PatchLove|[patchlove]]] - if a patch needs attention
* [good first bug] - you think coding the solution will be simple, good for a first-timer [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=good+first+bug&keywords_type=allwords&keywords=&product=MailNews+Core&product=Thunderbird&emailreporter1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= bug query]
* [good first bug] - you think coding the solution will be simple, good for a first-timer [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=good+first+bug&keywords_type=allwords&keywords=&product=MailNews+Core&product=Thunderbird&emailreporter1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= bug query]
* dupeme - if you believe this is a duplicate of another bug, but don't know which one
* closeme YYYY-MM-DD - with a date 2-4 weeks in the future to allow time for a response to your questions or instructions (see [[#Closemes|Closemes]])
* workaround comment ## - to indicate useful instructions
* [[Thunderbird:PatchLove|[patchlove]]] - if a patch needs attention


== Triage Resources, Tools and Hints ==
== Triage Resources, Tools and Hints ==
canmove, Confirmed users
2,081

edits

Navigation menu