Confirmed users
609
edits
B2G/Triage: Difference between revisions
Jump to navigation
Jump to search
→FxOS Device Group
| Line 20: | Line 20: | ||
*** If the bugs only affect platform specific launches, we will tag keywords(ex, "[2.0M_Only]") in the whiteboard and fixes only go to 2.0M branch. | *** If the bugs only affect platform specific launches, we will tag keywords(ex, "[2.0M_Only]") in the whiteboard and fixes only go to 2.0M branch. | ||
*** Otherwise(to 2.1), fixes will go to platform branches "and" master / mozilla-central as well. | *** Otherwise(to 2.1), fixes will go to platform branches "and" master / mozilla-central as well. | ||
* After device group identified a bug as a device blocker, device group | * After device group identified a bug as a device blocker, device group will configure the blockers to block a device launch meta bug(for example, Woodduck 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. | ||
* Once a bug is tagged as a blocker(blocking-b2g:release#+) | * 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" | ||
| Line 28: | Line 28: | ||
! Tagging rule !! Description !! Landing to master/m-c !! Landing to 2.0 !! Landing to 2.0M | ! Tagging rule !! Description !! Landing to master/m-c !! Landing to 2.0 !! Landing to 2.0M | ||
|- | |- | ||
| | | linked to Woodduck meta bug; blocking-b2g:2.0+; status-b2g-v2.0M:affected || Device launch blocker; general issue to overall 2.0 release || Yes || Yes || Yes | ||
|- | |- | ||
| blocking-b2g:2.0+; status-b2g-v2.0M:affected || Bug affected 2.0M and it's general to overall 2.0 release || Yes || Yes || Yes | | blocking-b2g:2.0+; status-b2g-v2.0M:affected || Bug affected 2.0M and it's general to overall 2.0 release || Yes || Yes || Yes | ||
|- | |- | ||
| | | linked to Woodduck meta bug; blocking-b2g:2.0M+ || Device launch blocker || Yes || --- || Yes | ||
|- | |- | ||
| blocking-b2g:2.0M+ || Bug found or nice to have feature request to 2.0M device launch || Yes || --- || Yes | | blocking-b2g:2.0M+ || Bug found or nice to have feature request to 2.0M device launch || Yes || --- || Yes | ||
|- | |- | ||
| | | linked to Woodduck meta bug; "[2.0M_Only]" in the whiteboard; blocking-b2g:2.0M+ || Device launch blocker, but specific to this platform || --- || --- || Yes | ||
|- | |- | ||
| "[2.0M_Only]" in the whiteboard; blocking-b2g:2.0M+ || Bug found or nice to have feature request to 2.0M device launch only || --- || --- || Yes | | "[2.0M_Only]" in the whiteboard; blocking-b2g:2.0M+ || Bug found or nice to have feature request to 2.0M device launch only || --- || --- || Yes | ||