How we triage: labels, priorities, and what to expect

[julianknutsen]

We've introduced a label system to organize the issue tracker. Every triaged issue gets a status, priority, and kind label.

If you're wondering what a label on your issue means or how to label a new one, see the full guide:

Labels and Triage: How We Organize Issues and PRs

Quick reference

Label	Meaning
status/needs-triage	Inbox — we haven't looked at it yet
status/needs-info	Waiting on you — please reply
status/needs-repro	We can't reproduce it — please provide steps
status/accepted	Confirmed and on our radar
status/help-wanted	Up for grabs — contributions welcome
priority/p0	Critical — data loss, security, completely blocked
priority/p1	High — core workflow broken
priority/p2	Medium — real problem, workaround exists
priority/p3	Backlog — good idea, reviewed when there's bandwidth
kind/bug	Broken behavior
kind/feature	New capability
kind/docs	Documentation only
kind/chore	Internal improvement (refactor, tests, CI, tooling)

Questions? Comment here or start a thread in the Discussion.