B2G/PartnerTriage: Difference between revisions
< B2G
Jump to navigation
Jump to search
(Created page with "Once a b2g release is ready to be handed off to OEM for final rounds of testing, blocker triage is also handed off and the following general criteria should help determine who...") |
|||
| Line 2: | Line 2: | ||
=Partner Triage= | =Partner Triage= | ||
* review all | * review all {codename}? bugs and set + or - according to partner priorities, quality bar & certification requirements | ||
** when +ing a blocker, a target milestone is also set | ** when +ing a blocker, a target milestone is also set | ||
* for any nominated bugs the partner doesn't have an opinion on, set [ | * for any nominated bugs the partner doesn't have an opinion on, set [{codename}-triage] | ||
=Mozilla Triage (after hand off)= | =Mozilla Triage (after hand off)= | ||
Revision as of 02:34, 31 May 2013
Once a b2g release is ready to be handed off to OEM for final rounds of testing, blocker triage is also handed off and the following general criteria should help determine who is responsible for which areas of triage:
Partner Triage
- review all {codename}? bugs and set + or - according to partner priorities, quality bar & certification requirements
- when +ing a blocker, a target milestone is also set
- for any nominated bugs the partner doesn't have an opinion on, set [{codename}-triage]
Mozilla Triage (after hand off)
- review only those not reported by partner(s) and only +/- obvious bugs
- review bugs that have [$codename-triage] in the whiteboard
- review bugs for upcoming deadlines and remove barriers where possible
- email all partner triage members when we disagree about the call on the blocking flag