-
Notifications
You must be signed in to change notification settings - Fork 397
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
[1.33] Release Team Lead Cycle Progress
area/release-eng
Issues or PRs related to the Release Engineering subproject
area/release-team
Issues or PRs related to the release-team subproject
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-priority
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2705
opened Dec 18, 2024 by
npolshakova
100+
Assemble Kubernetes 1.33 Release Team 🚀🌍✨🦇
area/release-team
Issues or PRs related to the release-team subproject
kind/documentation
Categorizes issue or PR as related to documentation.
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.
Update documentation on k/k CHANGELOG/OWNERS
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-priority
#2695
opened Dec 12, 2024 by
justaugustus
Cut v1.32.0 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
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.
Cut v1.31.4 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
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.
Cut v1.32.0-rc.2 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
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.
Cut v1.32.0-rc.1 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
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.
Promote arm64-linux to Tier 1
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-priority
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2647
opened Oct 21, 2024 by
ameukam
[1.32] Comms Subteam Lead Progress
area/release-eng
Issues or PRs related to the Release Engineering subproject
area/release-team
Issues or PRs related to the release-team subproject
kind/documentation
Categorizes issue or PR as related to documentation.
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.
#2625
opened Sep 15, 2024 by
mbianchidev
55 of 57 tasks
Cut v1.29.9 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
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.
[1.32] Release Team Lead Cycle Progress
area/release-eng
Issues or PRs related to the Release Engineering subproject
area/release-team
Issues or PRs related to the release-team subproject
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-priority
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2603
opened Aug 21, 2024 by
fsmunoz
100+
Enhance a template/checklist for KEP contributors to determine "Needs Docs"
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
#2595
opened Aug 10, 2024 by
drewhagen
Automate Release Docs subteam's Branch Syncs of the k8s website
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2594
opened Aug 10, 2024 by
drewhagen
Add a How-To adjacent to Docs handbook on how to pull in tech reviews/contributions to missing feature gate docs
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2580
opened Jul 31, 2024 by
drewhagen
Subproject Lead access for Grace, Kat & Marko
area/release-eng
Issues or PRs related to the Release Engineering subproject
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-priority
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2516
opened Jun 3, 2024 by
justaugustus
7 tasks
Determine access levels for SIG subproject leads
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-priority
#2515
opened Jun 3, 2024 by
justaugustus
Create new label for feature blogs for Release Comms and Blog Team tracking
area/release-team
Issues or PRs related to the release-team subproject
kind/feature
Categorizes issue or PR as related to a new feature.
needs-priority
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2496
opened May 6, 2024 by
natalisucks
Cut 1.26.15 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
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.
Cut 1.27.12 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
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.
Cut 1.28.8 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
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.
Cut v1.29.3 release
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
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.
Update process and release team handbooks handbooks on Major Themes
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
#2393
opened Dec 12, 2023 by
fsmunoz
Milestone maintenance enhancements
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.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
#2386
opened Dec 4, 2023 by
saschagrunert
Updating documentation: Post 1.29 Enhancements Role Handbook Updates
area/release-eng
Issues or PRs related to the Release Engineering subproject
area/release-team
Issues or PRs related to the release-team subproject
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-priority
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2375
opened Nov 25, 2023 by
npolshakova
2 of 8 tasks
Update Release Manager Handbooks to document processes related to OpenBuildService
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/documentation
Categorizes issue or PR as related to documentation.
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.
#2291
opened Jul 24, 2023 by
xmudrii
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.