Updated the B2G QA triage wiki based on your feedback. I've now broken
it into four categories and now have the highest urgency listed as "very
high" that would have the SLA of three days optimally for initial response.
Sincerely,
Jason Smith
Desktop QA Engineer
Mozilla Corporation
https://quality.mozilla.com
On 3/8/2013 4:54 PM, Jason Smith wrote:
Hi Alex,
Our team is aims to provide an initial response to requests on the
high list within three days optimally.
I'll add another priority also about the tracking? and tracking+ as
well per your feedback.
Sincerely,
Jason Smith
Desktop QA Engineer
Mozilla Corporation
https://quality.mozilla.com
On 3/8/2013 10:46 AM, Alex Keybl wrote:
This is great - the queries you provided at
https://wiki.mozilla.org/B2G/QA/Triage#Request_Urgency will
definitely help joint triage and engineering understand priorities
for testing. How regularly would you all expect to address requests
from the High list? It's obviously case by case, but understanding
how regularly that list is being looked at will help for context.
One final suggestion would be to add a priority between low and
medium, where tracking-b2g18 contains + or ?. Those would be a higher
engineering priority so I'm thinking they should be a higher QA
priority as well.
-Alex
On Mar 8, 2013, at 9:36 AM, Jason Smith <[email protected]> wrote:
Hi Everyone,
Our B2G QA team has put together a short wiki that summarizes how we
will triage incoming requests for QA support here -
https://wiki.mozilla.org/B2G/QA/Triage. This document aims to
clarify what keywords to use in what situation, how the QA contact
field is used, and our different triage queries we use by urgency
for addressing QA requests. Some areas from this documentation
that's worth noting includes the following:
* For QA requests, aim to use one of the keywords specified in the
wiki that best represents the request being made. Need STR on a bug?
Use steps-wanted. Need a regression window? Use
regressionwindow-wanted. Need specialized QA support that doesn't
fit any QA keyword? Use qawanted.
* The QA contact field should optimally aim to be set by the QA
intending to be working on the bug. Two exceptions on this rule
include:
o When there is a known default owner on the bugs (e.g. I test
calendar bugs), a default QA contact is defined and used by
default for QA requests
o When there is a high need to find an owner on a bug during
blocking triage, the QA representative in triage should be set
as the QA contact to find an owner to look at the bug. If there
is no representative in triage, then the QA contact field should
be set to either Naoki (Gaia), Geo (Platform), or myself (Apps)
based on the specific area the bug falls into.
* We address QA requests by order of three buckets - bugs that are
blocking? or blocking+, bugs that are blocking-, and any other bug.
If you have any questions, comments, feedback on this process,
please feel free to let our team know.
--
Sincerely,
Jason Smith
Desktop QA Engineer
Mozilla Corporation
https://quality.mozilla.com
_______________________________________________
dev-gaia mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-gaia
_______________________________________________
dev-gaia mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-gaia
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
