canmove, Confirmed users
2,237
edits
Thunderbird:Bugdays: Difference between revisions
Jump to navigation
Jump to search
m
→How: nit
m (→How: more more clarification and fixing) |
m (→How: nit) |
||
| Line 122: | Line 122: | ||
# '''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].) | # '''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 the bugs''' - which means test the problem, make comments | # '''Work the bugs''' - which means test the problem, in the bug report make comments and 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. | ||