QA/qawanted proposal: Difference between revisions

QA/qawanted proposal (view source)

3 bytes removed , 25 June 2013

Confirmed users

137

edits

@@ Line 70: / Line 70: @@
 * 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 ''qa-urgent'' keyword
+* 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 ''qa-urgent'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.
+* 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 ''qa-urgent'' 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 ''qaurgent'' request, while in transition. An appropriate time between releases would be chosen to fully transition.