Dear all,
Just like to share with you the triage rule for those bugs/features request
against post CC release (For now they are 2.0, 2.1):
Link: https://wiki.mozilla.org/B2G/Triage#FxOS_Device_Group
<https://wiki.mozilla.org/B2G/Triage#FxOS_Device_Group>
Blocking-b2g flag indicates where the fixes should be landed to depends on:
If the issue is regression and can be reproduced on main release(for example,
2.0+, 2.1+, ...).
If yes, blocking-b2g flag should be set to the values for FxOS core group(for
example, 2.0+, 2.1+, ...). Fixes should go to specific version branches and
master / mozilla-central.
Otherwise, it should be set with values for FxOS device group(for example,
2.0M+, 2.1S+, …). It means, 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 fixes are urgent to be landed for some reasons, these blocking-b2g flags
should be device group specific values(for example, 2.0M+, 2.1S+, …).
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.
In short:
Only regression issue can be nominated as release blocker (ex: 2.0?,
2.1?...), otherwise they should be nominated as device branch blocker (ex:
2.0M?, 2.1S?…).
This is base on time frame and stability consideration for main release. Device
team is also regularly triage these device specific nominations.
Please let me know if you have any question.
Sincerely,
-------------------------------------------------------
Josh Cheng
Engineering Project Manager, Firefox OS
Mozilla Corporation
✉ [email protected] <mailto:[email protected]>
-------------------------------------------------------_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
