You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently HPE conventions remain in a few places, e.g. splitting issues by severity as defined by e.g. S1 - High format. Similarly for issue type format, e.g. T1 - Defect. While this naming standard is certainly very good, it is specific.
Better to come up with something more generic and have that be standard. Issue types could be bug, documentation,enhancement,question ideally prepended with type - .
Some of the standard processing labels could also be taken into account. E.g. duplicate,good first issue,invalid,help wanted,invalid. They could have some sort of modified prefix, e,g. mod - , but this is perhaps not strictly necessary.
Then there should be a set of priority and/or severity of labels, similar to S1 - High....
One suggestion is to keep all labels lower case (allowing digits and symbols of course).
The text was updated successfully, but these errors were encountered:
Currently HPE conventions remain in a few places, e.g. splitting issues by severity as defined by e.g.
S1 - High
format. Similarly for issue type format, e.g.T1 - Defect
. While this naming standard is certainly very good, it is specific.Better to come up with something more generic and have that be standard. Issue types could be
bug, documentation,enhancement,question
ideally prepended withtype -
.Some of the standard processing labels could also be taken into account. E.g.
duplicate,good first issue,invalid,help wanted,invalid
. They could have some sort of modified prefix, e,g.mod -
, but this is perhaps not strictly necessary.Then there should be a set of priority and/or severity of labels, similar to
S1 - High
....One suggestion is to keep all labels lower case (allowing digits and symbols of course).
The text was updated successfully, but these errors were encountered: