Confirmed users
628
edits
B2G/Triage: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Joshwalker (talk | contribs) |
No edit summary |
||
| Line 273: | Line 273: | ||
* '''status-b2g18-v1.0.0''' represents the fix status on v1.0.0 branch (gaia v1.0.0 and/or mozilla-b2g18_v_1_0_0) | * '''status-b2g18-v1.0.0''' represents the fix status on v1.0.0 branch (gaia v1.0.0 and/or mozilla-b2g18_v_1_0_0) | ||
* '''status-b2g18''' represents the fix status on the v1.* branches (currently v1.0.1 until it branches, we'll add a separate status flag for it) | * '''status-b2g18''' represents the fix status on the v1.* branches (currently v1.0.1 until it branches, we'll add a separate status flag for it) | ||
== Project Flags == | |||
===blocking-b2g Flag=== | |||
'''Definition''' | |||
* blocking-b2g:version#? is nomination as blocker for the specific version. | |||
* blocking-b2g:version#+ indicates as release blocker for the specific version. Decisions are made during triage process. | |||
* blocking-b2g:--- (default flag. indicating undefined) | |||
* blocking-b2g:- (meaning non-blocking to any release) | |||
'''Note''' | |||
* Triage guideline https://wiki.mozilla.org/B2G/Triage#Blocker_Triage_Guidelines | |||
===feature-b2g Flag=== | |||
'''Definition''' | |||
* feature-b2g:version#? is defined as "this feature is being proposed for this release" | |||
* feature-b2g:version#+ is define as "this feature has been committed or done (by the engineering team(s)) for this release" | |||
* feature-b2g:--- (default flag. indicating undefined) | |||
* feature-b2g:- (meaning not a committed feature to any release) | |||
'''Note''' | |||
* [meta] bugs features and all dependencies targeted for a particular release should mark feature-b2g flag. | |||
* The feature-b2g flag should assigned to engineering tasks falling under the user stories AND the user stories themselves. | |||
* Who has the permission? PM and EPM, engineer managers and partner peers have the access | |||
===tracking-b2g Flag=== | |||
'''Definition''' | |||
* The teams need such a bucket to track backlog items apart from blocking-b2g and feature-b2g. | |||
* Attributes, sorted in priority | |||
** tracking-b2g:+ is the TopX item in the backlog | |||
** tracking-b2g:backlog is the regular backlog item | |||
** tracking-b2g:--- (default flag. indicating undefined) | |||
** tracking-b2g:- (lowest priority) | |||
'''Note''' | |||
* Permission? Everyone in the team should be able to set such flag. We're encouraging the backlog grooming to happen frequently and can be presented by using tracking-b2g flag. | |||
* We don't specify version# because supposedly these are neither release blockers nor feature blockers. | |||
===ux-b2g Flag=== | |||
'''Definition''' | |||
* Marks UX bugs required for a front-end feature (usually OS-wide) to work properly. | |||
* Distinguishes polish and non-blocking UX bugs from blocking UX bugs. | |||
'''Rationale and History''' | |||
The ux-b2g flag was created during the 2.0 release, which was a "UX heavy release:" 2.0 included a lot of UX changes to gestures, animations, the home screen, and so on. This meant that there were numerous OS-wide features -- like the thin, pale blue notifications bar, for example -- that needed to block 2.0+, and that required many UX bugs to be completed (graphics, transitions, animations). Each of these UX bugs needed to block 2.0+ if the finished, front-end feature was to look and behave properly across the OS. The ux-b2g flag was added when these "smaller" bugs were incorrectly marked as "polish," and were actually needed in order for a feature to work. | |||
'''Note''' | |||
Only members of the Firefox OS UX team and Release Management should set the ux-b2g flag. | |||