User:Chianger/draft-bugzilla flag: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
'''Definition''' | '''Definition''' | ||
* blocking-b2g:version#? is nomination as blocker for the specific version. | * 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: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''' | '''Note''' | ||
* Triage guideline https://wiki.mozilla.org/B2G/Triage#Blocker_Triage_Guidelines | * Triage guideline https://wiki.mozilla.org/B2G/Triage#Blocker_Triage_Guidelines | ||
| Line 9: | Line 13: | ||
===feature-b2g Flag=== | ===feature-b2g Flag=== | ||
'''Definition''' | '''Definition''' | ||
* feature-b2g:version#? is defined as "this feature is being proposed for this release" | * 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: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''' | '''Note''' | ||
* [meta] bugs features and all dependencies targeted for a particular release should mark feature-b2g flag. | * [meta] bugs features and all dependencies targeted for a particular release should mark feature-b2g flag. | ||
Revision as of 08:43, 4 March 2015
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.