QA/qawanted proposal: Difference between revisions

Jump to navigation Jump to search
m
Line 46: Line 46:
* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.
* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.


* ''qa-urgent'' will be introduced as a new keyword to request direct involvement by the Mozilla QA staff and will be used in conjunction with one of the other existing keywords.
* ''qaurgent'' will be introduced as a new keyword to request direct involvement by the Mozilla QA staff and will be used in conjunction with one of the other existing keywords.


* ''qawanted'' will be defined as an miscellaneous request for the  QA involvement not covered by any of the other existing keywords.
* ''qawanted'' will be defined as an miscellaneous request for the  QA involvement not covered by any of the other existing keywords.
Line 52: Line 52:
* Bugzilla's keyword definitions will be updated to reflect this proposal.
* Bugzilla's keyword definitions will be updated to reflect this proposal.


* All Product QA teams will adopt these semantics, though the specific commitment to ''qa-urgent'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders. ''qawanted'' will no longer be used to indicate an urgent response is required and should not be used in conjunction with other QA related keywords.
* All Product QA teams will adopt these semantics, though the specific commitment to ''qaurgent'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders. ''qawanted'' will no longer be used to indicate an urgent response is required and should not be used in conjunction with other QA related keywords.


== How Proposed Changes Address Issues ==
== How Proposed Changes Address Issues ==
Confirmed users
137

edits

Navigation menu