|
|
**Mouse over the labels for more information.**
|
|
|
|
|
|
## Simulation Domain Labels
|
|
|
|
|
|
## Issue type labels (automatically assigned in issue templates)
|
|
|
Each issue should be assigned ONE of:
|
|
|
|
|
|
~Bug ~Feature ~Question
|
|
|
|
|
|
|
|
|
## Status labels
|
|
|
Each issue should be assigned ONE of:
|
|
|
|
|
|
~Analysis ~Concept ~Implementation
|
|
|
|
|
|
~Duplicate
|
|
|
|
|
|
## Change severity
|
|
|
For each issue, once a change is agreed upon, i.e. once an issue reaches the Implementation status, should be assigned ONE of:
|
|
|
|
|
|
~MAJOR ~MINOR ~PATCH
|
|
|
|
|
|
[https://semver.org](From Semantic Versioning 2.0.0)
|
|
|
|
|
|
## Project-Specific Labels
|
|
|
|
|
|
### Milestones
|
|
|
These are used to define which release milestone the issues will be integrated into.
|
|
|
|
|
|
ONE of:
|
|
|
|
|
|
E.g.
|
|
|
2.0 / 2.1
|
|
|
|
|
|
### Group/Category labels
|
|
|
|
|
|
All ASAM projects have their Work Packages for projects clustered into groups or categories. These labels are defined individually for each project and should be used to categorise issues.
|
|
|
|
|
|
### Work Package Labels
|
|
|
All ASAM projects are have work items assigned to smaller work packages (that are then also assigned to a group or category). These labels are defined individually for each project and should be used to further categorise issues.
|
|
|
|
|
|
> An issue can have multiple Group and Work Package labels provided that it is relevant to more than one of these. |