Labels

Issues or PRs related to proposals.

Categorizes issue or PR as related to removing dead code, or deprecated apis/features.

Issues or PRs related to security or CVEs.

Parked issue that required triaging/revisit in a near future.

Issues or PRs related to UI changes

Issues or PRs related to UX changes

Indicates that a PR is ready to be merged.

Indicates that an issue or PR is actively being worked on by a contributor.

Indicates that an issue or PR should not be auto-closed due to staleness.

Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Denotes an issue or PR has remained open with no activity and has become stale.

Indicates a PR needs to be cherry-pick to a release branch

Indicates a PR that requires an org member to verify it is safe to test.

Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Indicates a non-member PR verified by an org member that is safe to test.

High-level Outcomes that appear on the UX WG Rodmap

Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Higher priority than priority/awaiting-more-evidence.

Highest priority. Must be actively worked on as someone's top priority right now.

Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Further information is requested

Denotes a PR that changes 100-499 lines, ignoring generated files.

Denotes a PR that changes 30-99 lines, ignoring generated files.

Denotes a PR that changes 10-29 lines, ignoring generated files.

Denotes a PR that changes 500-999 lines, ignoring generated files.

Denotes a PR that changes 0-9 lines, ignoring generated files.