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
As discussed some time ago on the dev call, we need better GitHub labels to manage issues and PRs.
I don't think we'll manage to rebuild labels from scratch (or if we do, that it would be the perfect system). Therefore I propose to incrementally evolve the labels.
Rename all state labels label name to state: label name. Rationale: The prefix distinguishes these labels from other classes (which may or may not grow a prefix themselves later on).
Change the colors to a simple 4-color scheme based on who must do the next action to move the issue/PR forward: Rationale: By this coloring we can immediately see whether the issue/PR needs an action from our side, which is the most important aspect for issue management. IMO the 4 colors are enough. One could add slight variations, e.g. different greys for different "no action" labels, but then again, nobody will exactly remember these. So let's keep it simple for a start. We can still refine this later if needed.
I like this plan, and we should probably recolor anything else that uses these colors to something else so there's no conflict.
(also we should consolidate the MEPs to MEP: #)
Activity
story645 commentedon Nov 1, 2020
I like this plan, and we should probably recolor anything else that uses these colors to something else so there's no conflict.
(also we should consolidate the MEPs to MEP: #)
timhoffm commentedon Nov 3, 2020
QuLogic commentedon Nov 11, 2020
FYI, 'Still Needs Manual Backport' is added by the bot, and so your rename and re-color of it didn't have any effect (cf #18929).