Confirmed users
217
edits
Firefox OS/ProgramManagement: Difference between revisions
→feature-b2g Flag
| Line 65: | Line 65: | ||
===feature-b2g Flag=== | ===feature-b2g Flag=== | ||
'''The purpose of | '''The purpose of feature-b2g flag''' | ||
* The feature-b2g flag is intended to be used to help define scope for a particular release. | * 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. | * 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. | ||
| Line 71: | Line 71: | ||
* The feature-b2g flag should assigned to engineering tasks falling under the user stories AND the user stories themselves. | * The feature-b2g flag should assigned to engineering tasks falling under the user stories AND the user stories themselves. | ||
* [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 | ||
* | * feature-b2g should flag to feature work only, not polish, enhancement or refactor work. Unless there's a story dedicated to those work in a release. This gives us a more stable feature-b2g bug number and better prediction/tracing. | ||
* You can only mark the flag for engineers assigned on YOUR team - not partner teams. | * You can only mark the flag for engineers assigned on YOUR team - not partner teams. | ||