B2G/QA/Triage: Difference between revisions

Jump to navigation Jump to search
340 bytes removed ,  20 October 2013
Line 45: Line 45:
== QA Contact ==
== QA Contact ==


The use of QA contact field should be set optimally when the person is actively investigating something in relation to the bug, usually in connection to one of the keywords above. The QA contact field should aim to only be set by the person who is planning on working on the bug for some piece of QA.  
The use of QA contact field should be set optimally when the person is actively investigating something in relation to the bug, usually in connection to one of the keywords above. The QA contact field should aim to only be set by the person who is planning on working on the bug for some piece of QA.


There are some exception cases to this rule however stated below.  
However, there is one exception to this rule. If a high need is raised in triage to find an owner for a bug, then triagers should set the QA contact to the QA representative in triage to find a QA owner to address the QA needs for the bug. If no QA representative is present, then Jason Smith should be set as the QA contact as a fallback.
 
The first case is if an explicit owner is known up front for a component who actively manages the bugs. In this case, the default QA contact will be used to address QA needs for the bugs.
 
The second case is if a high need is raised in triage to find an owner for a bug. In this case, triagers should set the QA contact to the QA representative in triage to find a QA owner to address QA needs for the bug. If no QA representative is present, then one of the two sheriffs should be set as the QA owner by area:
 
* Gaia General: Naoki Hirata
* Platform General: Geo Mealer
* Apps Gaia and Platform: Jason Smith


== QA Requests ==
== QA Requests ==
Confirmed users
2,959

edits

Navigation menu