canmove, Confirmed users
2,237
edits
Thunderbird:Bugdays: Difference between revisions
Jump to navigation
Jump to search
m
→How: more more clarification and fixing
m (→How: get rid of small font) |
m (→How: more more clarification and fixing) |
||
| Line 117: | Line 117: | ||
# '''Get an account''' - easily created at [https://bugzilla.mozilla.org/createaccount.cgi bugzilla account]. | # '''Get an account''' - easily created at [https://bugzilla.mozilla.org/createaccount.cgi bugzilla account]. | ||
# '''Protect''' - [https://support.mozilla.org/kb/profiles-where-thunderbird-stores-user-data#w_backing-up-a-profile Backup your data]. Use a test profile | # '''Protect''' - [https://support.mozilla.org/kb/profiles-where-thunderbird-stores-user-data#w_backing-up-a-profile Backup your data]. Use a test profile especially if bugs might cause dataloss (see next two points). | ||
# '''Make a test environment''' (optional) - [https://support.mozilla.org/kb/using-multiple-profiles You can create and use a profile just for testing]. | # '''Make a test environment''' (optional) - [https://support.mozilla.org/kb/using-multiple-profiles You can create and use a profile just for testing]. | ||
<!-- <small> (For gory detail see [http://kb.mozillazine.org/Testing_pre-release_versions Testing_pre-release_versions] and [http://kb.mozillazine.org/Starting_Firefox_or_Thunderbird_with_a_specified_profile Profile manager] describe to how test and not disturb your production setup.)</small> --> | <!-- <small> (For gory detail see [http://kb.mozillazine.org/Testing_pre-release_versions Testing_pre-release_versions] and [http://kb.mozillazine.org/Starting_Firefox_or_Thunderbird_with_a_specified_profile Profile manager] describe to how test and not disturb your production setup.)</small> --> | ||
# '''Get a build''' - Testing is best done with [https://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/ "Daily" builds] | # '''Get a build''' - Testing is best done with [https://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/ "Daily" builds] because it has the newest code, also referred to "Nightly" or "Trunk". Trunk is where Thunderbird is developed. But Trunk/Daily also has the greatest risk of problems, so if you don't want to use Daily then please use [http://www.mozilla.org/en-US/thunderbird/channel/ Beta]. (Worst case, use [http://www.getthunderbird.com/ the last released version].) | ||
# '''Pick bugs''' - [[Thunderbird:Upcoming_QA_Testday|current bugday "Focus"]] suggests which bugs to work on. <!-- http://wiki.mozilla.org/Thunderbird:Upcoming_QA_Testday --> | # '''Pick bugs''' - [[Thunderbird:Upcoming_QA_Testday|current bugday "Focus"]] suggests which bugs to work on. <!-- http://wiki.mozilla.org/Thunderbird:Upcoming_QA_Testday --> | ||
# '''Work bugs''' - test the problem. For UNCONFIRMED bugs, mark as "confirmed" if you are able to reproduce '''and''' the steps to reproduce are well documented and easily followed, '''and''' the problem exists in trunk build. If you are not running trunk but can replicate with current release, please comment with your findings, but do not set to confirmed. | # '''Work the bugs''' - which means test the problem, make comments, suggest or make changes to the bug fields, and help the user. For UNCONFIRMED bugs, mark as "confirmed" if you are able to reproduce '''and''' the steps to reproduce are well documented and easily followed, '''and''' the problem exists in trunk build. If you are not running trunk but can replicate with current release, please comment with your findings, but do not set to confirmed. | ||
#* Clarify the bug report without distorting or changing the original problem. For example if you found a related or new issue not described in the bug being tested, then you should make a new bug for that issue. | #* Clarify the bug report without distorting or changing the original problem. For example if you found a related or new issue not described in the bug being tested, then you should make a new bug for that issue. | ||
#* Change the bug's one line summary at the top of the bug page to be more accurate and complete, but also remove words to make summary less chatty - a summary should not read like a book, nor a syntactically correct sentence - shortness is good. | #* Change the bug's one line summary at the top of the bug page to be more accurate and complete, but also remove words to make summary less chatty - a summary should not read like a book, nor a syntactically correct sentence - shortness is good. | ||
| Line 129: | Line 129: | ||
#* Set a more appropriate [https://bugzilla.mozilla.org/describecomponents.cgi?product=Thunderbird Thunderbird component] or [https://bugzilla.mozilla.org/describecomponents.cgi?product=MailNews%20Core MailNews component] for the problem being described. | #* Set a more appropriate [https://bugzilla.mozilla.org/describecomponents.cgi?product=Thunderbird Thunderbird component] or [https://bugzilla.mozilla.org/describecomponents.cgi?product=MailNews%20Core MailNews component] for the problem being described. | ||
#* Cite what version(s) of Thunderbird you have used in your testing. | #* Cite what version(s) of Thunderbird you have used in your testing. | ||
# '''[[Thunderbird:Bugdays#Give us feedback|Give feedback]]''' (see feedback heading below) | # '''[[Thunderbird:Bugdays#Give us feedback|Give feedback about your bugday experience]]''' (see feedback heading below) | ||
If you are new to bugzilla - some quick tips: | If you are new to bugzilla - some quick tips: | ||
* Searching in bugzilla can be tricky. [https://bugzilla.mozilla.org/page.cgi?id=quicksearch.html Quicksearch tricks] and [https://bugzilla.mozilla.org/query.cgi Advanced Search] may help you produce more accurate and smaller search results. | * Searching in bugzilla can be tricky. [https://bugzilla.mozilla.org/page.cgi?id=quicksearch.html Quicksearch tricks] and [https://bugzilla.mozilla.org/query.cgi Advanced Search] may help you produce more accurate and smaller search results. | ||
* If you cannot change a bug field, please add a bug comment detailing what should be changed and why, and then inform someone in the IRC channel. | * If you cannot change a bug field, please add a bug comment detailing what should be changed and why, and then inform someone in the IRC channel. | ||
* See [[Thunderbird:Bug_Triage#Canconfirm_and_Editbugs_Privileges|Bug triage]] about how to get upgraded privileges | * See [[Thunderbird:Bug_Triage#Canconfirm_and_Editbugs_Privileges|Bug triage]] about how to get upgraded privileges so you can change bug fields.'' | ||
More helpful information at: | |||
* [[Thunderbird:Bug_Triage|Thunderbird Bug triage]] - expert tips, extensions, reference documents | * [[Thunderbird:Bug_Triage|Thunderbird Bug triage]] - expert tips, extensions, reference documents | ||
* [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] describes how to write an effective bug report that leads to bug fixes. | * [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] describes how to write an effective bug report that leads to bug fixes. | ||