Closed katcosgrove closed 1 month ago
I agreed to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.
I have completed the Inclusive Speaker Orientation training. My certificate ID is LF-af0vblifys.
@fsmunoz @sanchita-07 @neoaggelos @ramrodo -- please confirm with a comment here confirming that you agree to abide by the Security Release Process guidelines like I did above. Please also confirm that you've completed the Inclusive Speaker Orientation training, with your certificate ID. Thank yooooou ❤️
I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.
I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF-5j3swg5mzq
I agree to abide by the Security Release Process guidelines.
I have completes the CNCF Inclusive Speaker Orientation training. I can't find it in my history and the certificate URLs I got in my confirmation emails are dead, but the Credly badge is there. If this is not enough, I will redo it during the weekend.
I agree to abide by the Security Release Process guidelines.
I have completed the Inclusive Speaker Orientation training. My certificate ID is LF-buucxchj50
Subteam leads, please confirm with a comment that you have completed the Inclusive Speaker Orientation training, along with your certificate ID. Thank you!
cc: @drewhagen @kcmartin @salehsedghpour @rashansmith @pacoxu
I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.
I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF-aoiq9wdo0f
I agreed to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.
My certificate ID number: LF-5l8akc7m1l.
I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.
Here is my certificate ID number: LF-mv5hfqlibk
I agreed to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.
My certificate ID number: LF-9bcppiglad
I agreed to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.
My certificate ID number: LF-k4qpwuxd2o
I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.
My certificate ID number for LFC101 is: LF-p4td5jii9x
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Kubernetes 1.30
Additional information can be found in the release team lead handbook. If tasks are not needed to be done or additional tasks are required, make sure to update the issue template!
Release Lead tasks
1. Before the start of the Release Cycle (Week 0)
[x] Captured feedback from previous release cycle retro and planned to incorporate it into the release cycle
2355
2383
[x] Release directory named
release-1.XX
added to k/sig-release/releases2403
[x] Started planning the release schedule by opening a thread in
#sig-release
https://kubernetes.slack.com/archives/C2C40FMNF/p1704197979224879[x] Release Lead Shadows are confirmed
[x] Team leads notified that all release team members read the release team onboarding document
[x] Update slack channel descriptions for the
#sig-release
channel and all#release-xxx
channelsRelease Lead Onboarding:
kubernetes/org
) - https://github.com/kubernetes/org/pull/4643milestone-maintainers
release-team
release-team-leads
sig-release
kubernetes/sig-release
OWNERS
approvers
entry inreleases/release-1.XX/OWNERS
- #2403OWNERS_ALIASES
, add an entry in the following sections: #2404release-team
release-team-lead-role
kubernetes/k8s.io
) - https://github.com/kubernetes/k8s.io/pull/6273k8s-infra-release-viewers@
release-managers@
release-team@
release-team-leads
Slack Group (kubernetes/community
) - https://github.com/kubernetes/community/pull/7682users.yaml
, if they are not yet in the fileusergroups.yaml
OWNERS_ALIASES
only includes Release Team personnel from four (4) releases, including the current one.Create Release Team Documents:
bit.ly/k8s1XX-releasemtg
bit.ly/k8s1XX-retro
bit.ly/k8s1XX-contacts
One week before the start of the release cycle:
2. First weeks of the release cycle up to Enhancements Freeze (1-3 Weeks)
First Week of the release cycle:
[x] Checked in with team leads and verified that the release team is complete
[x] Reminded release team members to subscribe to the kubernetes-release-team and kubernetes-sig-release google groups and to the kubernetes-release calendar.
[x] Notified team leads to update the contact sheet with shadow information
bit.ly/k8s1XX-contacts
[x] Release schedule finalized
[x] Begin paying attention to CI signal, as it may begin degrading soon after the prior release is cut and any slips must be caught and rectified promptly.
[x] Meet your Shadows and create a communication channel with them. Establish expectations and share out work - delegate!
[x] Request review of this document by the Release Team Lead shadow(s). The shadow(s) should also take all actions in this document around joining groups and requesting access permissions.
[x] Update the SIG Release groups in the
k/k8s.io/groups/sig-release/groups.yaml
with the following:k8s-infra-release-viewers
release-comms
release-managers
release-team
release-team
release-team-shadows
release-team-shadows
already then add Lead to manager ofrelease-team-shadows
k8s-infra-rbac-triageparty-release
[x] Ensured that there is a branch manager available for cutting 1.XX.0-alpha.1
Assist the Enhancements Lead in collecting planned work from SIGs
[x] Discussed and scheduled a weekly Release Team meetings on a day that is most acceptable to the team. Invite the
kubernetes-sig-release
group.[x] Poll Release Team membership and schedule a weekly alternate meeting to better enable more attendance outside of the Americas.
[x] Major release cycle events have been added to the Kubernetes Release Calendar with one week in advance reminders set. (defer to the handbook for more information)
[x] Checked in with ci-signal and branch managers if 1.XX.0-alpha.2 is ok to be released and master-blocking tests are all green
A week before Enhancements Freeze:
#sig-release
and#chairs-and-techleads
Slack channels referencing to the k-dev email.3. Enhancements freeze up to Release Halfway Point (~Week 5 - 7)
General Tasks:
Release Cut Alpha 3:
Release Cut Alpha 4:
4. Release Halfway Point up to Code Freeze (~Week 8 - 11)
General Tasks:
Removals, Deprecations, and Major Changes Blog:
Major Themes & Release Blog:
5. Around Code Freeze (~Week 13)
Defer to the code freeze section in the release-team-lead handbook.
Shortly before Code freeze
Code Freeze begins, and it’s now the home stretch of the release. SIGs will need to ensure all work moving forward is carefully curated with required merge labels.
With Code Freeze
/milestone clear
After Code Freeze
release-1.XX
branch has been automatically created at the start of Test Freeze6. Test Freeze up to Release Day (~Week 14)
7. Release Day (~Week 15)
Note that release day can and should be postponed if any of the conditions outlined in week 11 are not satisfied.
Every issue in the milestone is considered release blocking
If you have to push the release date back, try to avoid Friday since it makes release publicity extremely difficult. Also, people seem to have patience with delay as long as the reasons are clear and openly communicated. This is your duty. You must over-communicate and ensure the team is also talking to their stakeholders (CNCF, community, press, etc.)
The following final actions must occur in order, with successful completion of each being the entry criteria to the next.
[x] After the release, it’s time to lift code freeze. The bot will need to be updated.
[x] The Docs lead thaws k/website
[x] Use all of the appropriate communications channels to announce the lifting of Code Freeze and thawing of k/website, this can part of the release announcement.
8. After the Release Day (~Week 16, 17)
Release Lead Offboarding tasks:
kubernetes/org
)milestone-maintainers
release-team
release-team-leads
kubernetes/k8s.io
)k8s-infra-release-viewers@
release-managers@
release-team-leads
Slack Group (kubernetes/community
)users.yaml
, if no longer in a groupusergroups.yaml
Further comments
NONE
cc: @kubernetes/release-engineering @kubernetes/release-team