213
edits
m (remove call for nightly testers to wign up) |
m (→Additional QA Tasks: update to blocking-seamonkey1.1 flag) |
||
| Line 39: | Line 39: | ||
* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search). | * Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search). | ||
* If you find a bug that you believe must be fixed before the next milestone (1. | * If you find a bug that you believe must be fixed before the next milestone (1.1), nominate the bug to block release by setting the "blocking-seamonkey1.1" nomination flag to "?" and add a comment to state why you think the bug is important. Also, please help with any QA needed for the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.1%2B bugs] the Council has already decided should block the next milestone. | ||
== More QA Resources == | == More QA Resources == | ||
edits