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
Issues in Github is a flat list of work items. There is no concept of priority, severity, and status like other systems. When this list is small, it may be easy to prioritize and manage, but can quickly get out-of-hand as the repositories grow. We need a way to help us manage the issues.
I am not suggesting that we need these for all repositories, but should be considered by Repository Committers based on how they want to manage issues.
Here's a list of proposed labels to help with issues management:
Category Labels
Task
Bug
Feature
Discussion - I think this discussion category is helpful as we have been using issues for a lot of discussions.
Idea - anyone who wants to propose an idea, can use this. Different from feature where idea is a proposal / suggestion. Features may result in actual coding being done. We may want to use this tag for repository proposal to separate them from project admin discussions.
Priority Label
HIGH
LOW
If unassigned, it is by default medium priority. Allow developers to prioritize work.
Severity Label
BLOCKING
MAJOR
NORMAL
MINOR
If unassigned, it is by default normal. Allow issue reporter to let us know how bad the problem is.
Status Labels
triaged
in-progress
fixed
invalid (not-reproducible, working as designed, etc.)
need feedback
With the labels, we can then create queries to help us look at issues that we want. With no status label, issue is new and not-triaged.
Thoughts?
The text was updated successfully, but these errors were encountered:
Standarized labelling makes sense, and these label definitions sound good, though I don't know if all people will use all sets of labels.
One problem is that I believe that only people with write access to a repository can assign labels to the issues in that repository (see #11). So...
"Idea: anyone who wants to propose an idea, can use this." & "Severity: Allow issue reporter to let us know how bad the problem is." aren't going to work.
I think people from outside a project who want to have a discussion or use an idea label should instead put discussion or idea in the title of the issue. We may want to encourage them to use BLOCKING or MAJOR in the title of a bug that is a big issue.
Issues in Github is a flat list of work items. There is no concept of priority, severity, and status like other systems. When this list is small, it may be easy to prioritize and manage, but can quickly get out-of-hand as the repositories grow. We need a way to help us manage the issues.
I am not suggesting that we need these for all repositories, but should be considered by Repository Committers based on how they want to manage issues.
Here's a list of proposed labels to help with issues management:
Category Labels
Priority Label
If unassigned, it is by default medium priority. Allow developers to prioritize work.
Severity Label
BLOCKING
MAJOR
NORMAL
MINOR
If unassigned, it is by default normal. Allow issue reporter to let us know how bad the problem is.
Status Labels
With the labels, we can then create queries to help us look at issues that we want. With no status label, issue is new and not-triaged.
Thoughts?
The text was updated successfully, but these errors were encountered: