Jump to: navigation, search

Difference between revisions of "Tags and Prefixes"

(Created page with "== Tags and Prefixes == === Tags === Each new Story created shall be marked with Tags to: * Show what kind of a Story it is - a Bug, a Feature, etc... * Show what release the...")
 
(Replaced content with "This page was created in error and can be deleted.")
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Tags and Prefixes ==
+
This page was created in error and can be deleted.
 
 
=== Tags ===
 
Each new Story created shall be marked with Tags to:
 
* Show what kind of a Story it is - a Bug, a Feature, etc...
 
* Show what release the Story is targeted to: stx.2018.08, stx.2018.11, etc...  See the TBD section for more info on our Release plans
 
* Show which sub-project of Starling is responsible for completing the Story.  See the TBD section for more info on the project's sub-projects
 
 
 
Tagging new stories is mandatory. 
 
 
 
Tags for Story kinds currently defined are:
 
* "stx.bug" - for defects
 
* "stx.feature" - for new features
 
 
 
Tags for Releases currently defined are:
 
* "stx.2018.08" - for bugs or features intended to be completed before the August code freeze for the September release
 
* "stx.2018.11" - for bugs or features intended to be completed before the November code freeze for the December release
 
 
 
Tags for Sub-projects currently defined are:
 
* "stx.security" - for defects and features for the Security sub-project
 
* Additional tags e.g. for the project sub-projects will be defined shortly
 
 
 
=== Prefixes ===
 
To make it easier to visually identify categories of work and to search on them, you can optionally add a prefix to the description for a Story.  The following prefixes are defined:
 
** [Bug]: A problem which impairs or prevents the functionality of StarlingX
 
** [Enhancement]: An improvement or enhancement to the functionality of StartingX; typically smaller scope items
 
** [Feature]: A new feature/functionality to be added to StarlingX. Ideally, the scope should fit within a release time-frame (ex: 3-6 months)
 
** [Build]: Build tools, environment, repo organization, etc
 
** [Process]: Process and project related work items
 
** [Test]: Test/Validation related work items
 
** [Doc]: Documentation related work items
 
** [Upstreaming]: Work items that need to be pushed in the core openstack projects or other 3rd party repo's
 
** [Help]: Request for assistance, questions
 

Latest revision as of 18:21, 20 July 2018

This page was created in error and can be deleted.