Confirmed users
137
edits
QA/qawanted proposal: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| 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. | ||
* '' | * ''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 | * ''qawanted'' will be defined as an miscellaneous request for the QA involvement not covered by any of the other existing keywords. This will be the basic catch all for | ||
* 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 '' | * 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 == | ||
| Line 70: | Line 70: | ||
* Legacy bugs with request keywords will continue to show up in queries, as is appropriate. | * Legacy bugs with request keywords will continue to show up in queries, as is appropriate. | ||
* | * Existing ''qawanted'' keyword bugs can remain as is without being impacted by the new ''qaUrgent'' keyword | ||
* | * Initially, we will likely have to re-keyword new bugs as we educate external parties on how to use the new ''qaUrgent'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme. | ||
* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qawanted'' request, while in transition. An appropriate time between releases would be chosen to fully transition. | * Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qawanted'' request, while in transition. An appropriate time between releases would be chosen to fully transition. | ||