Every issue should have a C-ategory.
Community or customer issues you’re triaging should get an O-support or O-community.
Severe bugs should have a S-everity.
When closing an issue (except after completing an implementation or fix), make sure it has an X-close-reason.
Optionally, you can use the other label groups as you see fit.
Is an issue specific to a code area? Add an A-rea label.
Does an issue or PR need a backport? Use the backport- label.
Is an issue specific to a platform? Use a P-latform label.
Does your team like to do time estimates? Make an estimate with a T-ime label.
Is this an easy issue that an external contributor could do? Add an E-xperience label.
Does this issue need special attention in the docs, that a release note will not satisfy? Add a docs- label.
You received this message because you are subscribed to the Google Groups "CockroachDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cockroach-db...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cockroach-db/b05e50a0-91c3-4e69-895e-eea23f233dad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/cockroach-db/CAHkUbgMwpDozOSR0zYi0OvncF5SN5dLATo-22JzSuH-3tUO3Yw%40mail.gmail.com.