-
Notifications
You must be signed in to change notification settings - Fork 392
Issues: kubernetes/sig-release
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
k8s UPGrade
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
needs-priority
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2538
opened Jun 20, 2024 by
Cui0526
Kubernetes v1.31 Major Themes contact
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
needs-priority
sig/release
Categorizes an issue or PR as relevant to SIG Release.
Scalability tests for beta releases
kind/bug
Categorizes issue or PR as related to a bug.
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
sig/scalability
Categorizes an issue or PR as relevant to SIG Scalability.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Assess version markers used in release-branch job configs
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/bug
Categorizes issue or PR as related to a bug.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
ProTip!
Follow long discussions with comments:>50.