Repository Labels/tags needs an overhaul

[retailcoder]

The wiki page for labels has been kept more or less up-to-date, but a recent chat conversation highlighted that we need to review our labelling.

Let's move this discussion over here, for posterity. So, what's a good way to label our issues?

We have:

• Bugs
• Features
• Meta-labels that apply to bugs, features, and pull requests.

Bugs break down into severities / priorities. Useful for tracking what the problems are and how severe things are.

Feature tags break down into categories; useful for filtering individual feature groups (e.g. inspections, refatorings, etc.)

Meta things is...well, everything else.

We have too many labels. What do we cut?

[Vogel612]

The discussion has been duplicated to the team-internal discussion

[PeterMTaylor]

^ the link doesn’t work for me @Vogel612.
My thoughts is to ask consider how tags could support RD in a workflow fashion starting from users using RD and then ending up with a green release or hotfix which the cycle repeats (wash rinse spin)as I believe we are still evolving! and as such let’s update tags reflecting this pseudo workflow now @bclothier has summarised the current flow alright however are we able to filter the bug list given sub categories of technology or technical bits to help “context” that we crave for at times.
The pull request tags are ideal over a number of releases with WIP and conflicting. These are literally good quality assurance steps we do before the bucket is kicked onto the big pile.
So is our limitations of hue colours up to the maximum of 8 or 4 or 3?