add exempt issue labels

[tac0turtle]

No description provided.

[alessio]

Please add launchpad to the list as well

[tac0turtle]

this repo really needs to clean up its labels, it has 78...

[alessio]

Please add launchpad to the list as well

Sorry @marbar3778, I take it back. There is already a 0.39 LTS.

And I agree, here is a list of labels that IMO we should let go:

• API: what API? Go API? REST API? Lacks a description. And frankly this is an SDK, nealry everything we do is about some APIs.
• build, ci and tooling should be merged. tooling sound the most generic and appropriate to me
• dev-ux, client-ux should be merged into a single UserExperience (developers are a subset of users)
• baseapp, crypto, keys, kvstore, types (pointless, we should just use a core label for all the SDK's core packages - meaning everything that does not live in x/)
• either feature or feature-request
• nice-to-have (if we want to keep track of bug's priority to get better at prioritization then we should copy from tendermint, see the P: labels)
• question (this label begets many indeed)
• refactor (never managed to understand the value added by this label)
• non-determinism means nothing, and in fact it has been used only 10 times. If a bug breaks determinism, then it should be tagged bug and P: critical.
• vesting - only one issue open Create Vesting Account Message #4287

There might be more, what do people think?

[alexanderbez]

IMHO we should just add pinned to those issues instead of having the config support a bunch of ad-hoc labels.

[tac0turtle]

we should merge this. there is chaos every morning i wake up lol

ill make a doc a doc for a label system and if accepted ill overhaul

[alessio]

Yeah sorry @marbar3778, I've kinda hijacked the conversation. It's a great idea to create a doc, can you please incorporate this #6602 (comment) too? Thanks!