StarlingX/Tags and Prefixes

Tags
Each new Story created shall be marked with Tags. We are using Tags to:
 * Show what release the Story is targeted to: stx.2018.08, stx.2018.11, etc...
 * Show which sub-project of Starling is responsible for completing the Story.

To help us all keep things straight and to enable us to share queries and searches please follow these rules:
 * All newly created Stories shall be tagged as described here

Tags for Releases
Stories and defects should be tagged with a release target. The project releases 2 major releases per year. Point releases for bug fixes are sometimes made, bugs for these features are tagged with the underlying major release tag.

Prefixes
This page is under construction. ToDo: Break out the prefixes by "kind" like the tags, and define Prefixes for the sub-projects.

To make it easier to visually identify categories of work and to search on them, you can optionally add a prefix to the subject of an email or to the description for a Story. The following prefixes are defined:


 * [Enhancement]: An improvement or enhancement to the functionality of StartingX; typically smaller scope items
 * [Build]: Build tools, environment, repo organization, etc
 * [Process]: Process and project related work items
 * [Test]: Test/Validation 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

Examples
A new defect for the Security Sub-project would be tagged as: stx.security. The description can optionally contain "[Security]".

A new feature for the Networking Sub-project should be tagged as: stx.networking. The description can optionally contain [Feature][Networking].

Note that each Tag needs to be entered separately in the web UI.