97
edits
WeslyHuang (talk | contribs) (→Development Detail: fix Sprint number) |
WeslyHuang (talk | contribs) (→Development Detail: Add whiteboard usage) |
||
Line 25: | Line 25: | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
===== Bug Priority/Uplift Management ===== | |||
In general we'd target to land only on Nightly (both fixes and features), and land on Beta when requested/really have to. With that idea we adopt a similar way of the P-system that P1 means "this Nightly cycle" while P2 refers to the "future Nightly cycles". Whiteboard tags involved with above principle are: | |||
* For bugs considered in a specific Sprint, 3 tags will be added | |||
** [FNC]: short for "Fennec" | |||
** [SPT#XX]: Stands for the Sprint number XX (each Sprint period is defined in above) | |||
** [MVP] or [BL] or [INT]: stands for "MVP (must have)", "BackLog" (may have), and "INTerrupt (unplanned)", respectively | |||
** For example a bug with whiteboard [FNC][SPT#57.1][MVP] means it's a bug we targe to get resolved in Sprint #57.1. | |||
* For bugs that we intend to uplift to Beta, we'll add both tags "[FNC]" and "[PLANNED_UPLIFT]" in the whiteboard field. So people (e.g., Release Management) can get the visibility of potential uplifts for tracking. | |||
== Quality Assurance == | == Quality Assurance == |
edits