Confirmed users
2,816
edits
Bugmasters/Guide: Difference between revisions
m
→Triage docs for specific teams or modules
| Line 75: | Line 75: | ||
* [https://developer.mozilla.org/en-US/docs/Triaging_crash_bugs Triaging crash bugs]. Tackle bugs that may have caused a crash. Learn how to find crash bugs, add complete steps to reproduce, a stack trace, and a [https://developer.mozilla.org/en-US/docs/Reducing_testcases reduced testcase] for a crash bug, then tag it for a developer to review. The [https://wiki.mozilla.org/CrashKill/DesktopTriage CraskKill team] triage notes may be helpful. | * [https://developer.mozilla.org/en-US/docs/Triaging_crash_bugs Triaging crash bugs]. Tackle bugs that may have caused a crash. Learn how to find crash bugs, add complete steps to reproduce, a stack trace, and a [https://developer.mozilla.org/en-US/docs/Reducing_testcases reduced testcase] for a crash bug, then tag it for a developer to review. The [https://wiki.mozilla.org/CrashKill/DesktopTriage CraskKill team] triage notes may be helpful. | ||
* B2G Triage: https://wiki.mozilla.org/B2G/QA/Triage with a list of keywords agreed on by the B2G team and QA. B2G developers use keywords to tag bugs with steps-wanted, testcase-wanted, regressionwindow-wanted, verifyme, and qawanted. | * B2G Triage: QA's page, https://wiki.mozilla.org/B2G/QA/Triage, with a list of keywords agreed on by the B2G team and QA. B2G developers use keywords to tag bugs with steps-wanted, testcase-wanted, regressionwindow-wanted, verifyme, and qawanted. Also, [https://wiki.mozilla.org/B2G/Triage B2G Triage meeting notes] from the B2G team. | ||
* Firefox Triage days (tuesday) https://etherpad.mozilla.org/firefox-triage Backchannel: #fx-team | * Firefox Triage days (tuesday) https://etherpad.mozilla.org/firefox-triage Backchannel: #fx-team | ||