Confirmed users
243
edits
B2G/Triage: Difference between revisions
Jump to navigation
Jump to search
→FxOS Core Group
Bobbychien (talk | contribs) |
Bobbychien (talk | contribs) |
||
| Line 10: | Line 10: | ||
* Before feature complete (FC) date, FxOS functional teams are in development and stabilization stages. Each functional team should cover the triage process. | * Before feature complete (FC) date, FxOS functional teams are in development and stabilization stages. Each functional team should cover the triage process. | ||
* After feature complete date, release management team handles release based triage process. | * After feature complete date, release management team handles release based triage process. | ||
* After platform branches are created, FxOS device group(TAMs, EPMs and EMs) drives the triage process on bugs that are reported for platform launches. | * After platform branches are created, FxOS device group (TAMs, EPMs and EMs) drives the triage process on bugs that are reported for platform launches. | ||
* Blocking-b2g flag indicates where the fixes should be landed to: | * Blocking-b2g flag indicates where the fixes should be landed to: | ||
** If a bug matches the blocking criteria, it will be tagged with blocking-b2g:version#+ value(for example, blocking-b2g:2.1+). Fixes will go to corresponding version branch and master / mozilla-central. | ** If a bug matches the blocking criteria, it will be tagged with blocking-b2g:version#+ value(for example, blocking-b2g:2.1+). Fixes will go to corresponding version branch and master / mozilla-central. | ||