B2G/Triage: Difference between revisions

Jump to navigation Jump to search
Line 41: Line 41:
*** If the bugs only affect platform specific launches, we will tag keywords(ex, "[2.0M_Only], [2.1S_Only]") in the whiteboard and fixes only go to 2.0M / 2.1S branch.  
*** If the bugs only affect platform specific launches, we will tag keywords(ex, "[2.0M_Only], [2.1S_Only]") in the whiteboard and fixes only go to 2.0M / 2.1S branch.  
*** Otherwise(to 2.1 or 2.2), fixes will go to platform branches "and" master / mozilla-central as well.
*** Otherwise(to 2.1 or 2.2), fixes will go to platform branches "and" master / mozilla-central as well.
* After partner and device group identified a bug as a device P1 bug, device group will configure the P1 bug to block a device launch meta bug(for example, Woodduck_P1 meta bug).  
* After partner and device group identified a bug as a device Blocker bug, device group will configure the Blocker bug to block a device launch meta bug(for example, [https://bugzilla.mozilla.org/show_bug.cgi?id=1080337 Woodduck_Blocker meta bug)].  
* Tracking flag(for example, status-b2g-v2.0M) is marked as "affected" once we identify that platform launches are affected by this bug.  
* Tracking flag(for example, status-b2g-v2.0M) is marked as "affected" once we identify that platform launches are affected by this bug.  
* Device branch sheriff will mark status-b2g-v2.0M to "fixed" and also put “verifyme” at Keywords field if bug assignee initial pull request and review+.  
* Device branch sheriff will mark status-b2g-v2.0M to "fixed" and also put “verifyme” at Keywords field if bug assignee initial pull request and review+.  
* Device QA will mark status-b2g-v2.0M to "verified" if bug is verified fixed.  
* Device QA will mark status-b2g-v2.0M to "verified" if bug is verified fixed.  
* Once a bug is tagged as a P1(blocking-b2g:release#+), FxOS core group shouldn't minus it, due to its urgency and importance on device launches.  
* Once a bug is tagged as a Blocker(blocking-b2g:release#+), FxOS core group shouldn't minus it, due to its urgency and importance on device launches.  
* So, overall, the tagging rule after triage driven by device group is(take 2.0M as an example):
* So, overall, the tagging rule after triage driven by device group is(take 2.0M as an example):
{| class="wikitable"
{| class="wikitable"
Confirmed users
811

edits

Navigation menu