Hi all,

We currently have a lot of GitHub labels for issues and pull requests.
Many of the labels serve(d) a temporary purpose, have no clear meaning
or are superfluous as GitHub offers more sophisticated approaches. The
following list serves as a proposal to apply to the project's list of
labels.

Note: There's no way in GitHub to "hide" or "deprecate" a label.

Labels used for "release version associations". GitHub offers
Milestones for this use case. All the labels can be legitly removed.
Generally, IIRC, we agreed on not using a "blocker label".
- 1.0-blocker
- 1.1.0-blocker
- 2.0-blocker: We haven't agreed on any content of version 2.0 - so I
don't think this label is needed.
- 1.0.0 bug bash: the meaning of this label is unknown

Unused labels, should all be removed:
- approved: unclear what the meaning should be
- wontfix: use GH functionality
- dependencies: unused
- duplicate: unused
- help wanted: unused
- invalid: unused
- question: unused
- rebase: unused

Rarely used:
- documentation: I think this should be used to associate issues and
maybe PRs with changes to the website. Or we rename this label to
"website", which seems clearer.
- IdentityRoleFederation: only one PR has this, should be removed

Used labels, should be good to keep as is:
- bug
- enhancement
- proposal
- good first issue
- renovate-polaris: dependency bumps by Renovate
- Stale: stale-PRs workflow


Robert

Reply via email to