User:Chianger/draft-bugzilla flag

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.

Note

• Triage guideline https://wiki.mozilla.org/B2G/Triage#Blocker_Triage_Guidelines

feature-b2g Flag

Definition

• The feature-b2g flag is intended to be used to help define scope for a particular release.
• The feature-b2g flag enables us to isolate the particular engineering tasks that make up the completion of the feature in a release time frame.
• 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"

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:+
  • tracking-b2g:backlog
  • 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.