... | @@ -2,20 +2,20 @@ |
... | @@ -2,20 +2,20 @@ |
|
|
|
|
|
## Simulation Domain Labels
|
|
## Simulation Domain Labels
|
|
|
|
|
|
## Issue type labels (automatically assigned in issue templates)
|
|
### Issue type labels (automatically assigned in issue templates)
|
|
Each issue should be assigned ONE of:
|
|
Each issue should be assigned ONE of:
|
|
|
|
|
|
~Bug ~Feature ~Question
|
|
~Bug ~Feature ~Question
|
|
|
|
|
|
|
|
|
|
## Status labels
|
|
### Status labels
|
|
Each issue should be assigned ONE of:
|
|
Each issue should be assigned ONE of:
|
|
|
|
|
|
~Analysis ~Concept ~Implementation
|
|
~Analysis ~Concept ~Implementation
|
|
|
|
|
|
~Duplicate
|
|
~Duplicate
|
|
|
|
|
|
## Change severity
|
|
### 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:
|
|
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
|
|
~MAJOR ~MINOR ~PATCH
|
... | @@ -27,10 +27,8 @@ For each issue, once a change is agreed upon, i.e. once an issue reaches the Imp |
... | @@ -27,10 +27,8 @@ For each issue, once a change is agreed upon, i.e. once an issue reaches the Imp |
|
### Milestones
|
|
### Milestones
|
|
These are used to define which release milestone the issues will be integrated into.
|
|
These are used to define which release milestone the issues will be integrated into.
|
|
|
|
|
|
ONE of:
|
|
>These are actually not labels but defined separately in the milestones section of the project (under issues)
|
|
|
|
|
|
E.g.
|
|
|
|
2.0 / 2.1
|
|
|
|
|
|
|
|
### Group/Category labels
|
|
### Group/Category labels
|
|
|
|
|
... | | ... | |