Labels

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

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.

PRs related to prow auto generation automation

Issues related to prow olm automation

Further information is requested

Indicates this PR should trigger a minor version release on merge.

Indicates this PR should trigger a patch version release on merge.

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.

Denotes a PR that changes 1000+ lines, ignoring generated files.

Issues scheduled for 2026

Issues scheduled for Q1 in 2025

Issues scheduled for Q2 in 2025

Issues scheduled for Q3 in 2025

Issues scheduled for Q4 in 2025

Denotes an issue that blocks the tide merge queue for a branch while it is open.

Denotes a PR that should use a standard merge by tide when it merges.

Denotes a PR that should be rebased by tide when it merges.

Denotes a PR that should be squashed by tide when it merges.

Indicates an issue or PR is ready to be actively worked on.

Indicates an issue is a duplicate of other open issue.

Indicates an issue needs more information in order to work on it.

Indicates an issue can not be reproduced as described.