Issue tracker organization - cockpit-project/cockpit GitHub Wiki
How others do it
Current labels - list
- blocked
- bug
- enhancement
- hubbot:f22-atomic:check
- hubbot:f22:clean
- hubbot:fraw:check
- hubbot:fraw:clean
- invalid
- needinfo
- needsdesign
- needswork
- patternfly
- priority
- question
- starter
- ui-fixes
- wontfix
Suggested labels brainstorm
- One for each category System, Network, Storage, Containers etc.
- I don't think it's good to split things into application-categories - the project just isn't that large(dperpeet)
- Priorities apart from "priority"
- Priority:high
- Priority:medium
- Priority:low
- I agree with the spirit, but would prefer a different wording: "priority" means high priority, and I propose "goodidea" for something that's a good idea. Alternatively, we could reuse the "enhancement" tag for this. (dperpeet)
- What's a good tag for something with low priority - "archived" / "future"? (dperpeet)
- Needs-discussion status
- how is this placed vs. needsdesign? (dperpeet)
- Split up into status (needsdesign, needswork etc.) and type (patternfly, ui-fixes, bug, enhancement etc.)
- OS labels: RHEL, Atomic, Fedora, CentOS
- do we need OS-specific labels? (dperpeet)
Proposed list of labels
- blocked
- bug (unexpected failure, needs fixing)
- enhancement (good idea)
- future (not currently being worked on)
- hubbot:f22-atomic:check
- hubbot:f22:clean
- hubbot:fraw:check
- hubbot:fraw:clean
- invalid
- needinfo
- needsdesign
- needswork
- patternfly
- priority
- question
- starter
- wontfix
- wontimplement
removed: ui-fixes added: future, wontimplement