[URGENT] Kubernetes 1.22 Code Freeze is Tomorrow, July 8th, 2021!

2 views
Skip to first unread message

Savitha Raghunathan

unread,
Jul 7, 2021, 1:58:22 PM7/7/21
to Kubernetes developer/contributor discussion, le...@kubernetes.io, kubernetes-sig-release, releas...@kubernetes.io

Hi Kubefolx,


Tomorrow on Thursday, July 8th, Code Freeze comes into effect at 18:00 Pacific Time.


All code PRs related to enhancements tracked in the tracking sheet need to be merged by Code Freeze. After the Code Freeze comes into effect, the Enhancements Team will start removing enhancements from the milestone. Post that, you would need to file an exception to keep your enhancement/s in the 1.22 release. Please keep in mind that after code freeze, only release-blocking issues and PRs will be allowed back into the milestone. 


71 Enhancements had opted-in to the release. At the time of writing this email, 40 of the enhancements are either code complete / on track for completion, 28 of them are tagged 'At Risk' due to their tentative status of completion by Code Freeze and 3 enhancements have already opted out of the release. You can check the status of enhancements in the tracking sheet. Enhancements Team has been actively tracking open issues and PRs. We would appreciate it if you could reply as soon as possible to any open questions the team has asked on your issue / PRs.


Here are some measures to ensure that your enhancements get accepted into the release:

  • Milestone issues/PRs with v1.22 that absolutely must land in v1.22

  • Remove issues/PRs from the v1.22 milestone if it doesn't need to land for v1.22

  • Please use /retest judiciously on “non-critical” PRs

For applying/removing milestones, please refer to the milestone-maintainers GitHub group who has the privileges to perform actions on milestones.
Note: For PRs related to the implementation of features, the respective enhancement must have been already accepted into the milestone.

The deadline for opening a placeholder PR falls on the day after code freeze - July 9th. 

All enhancement owners are requested to ensure the creation of a placeholder docs PR by July 9th, if your enhancement needs one.


In case you have any concerns, please feel free to reply to this email or reach to me or any of the Release Team lead shadows or the Release Enhancements Team on #sig-release of Kubernetes Slack.


Thank you :) 


Regards,

Savitha Raghunathan,

On behalf of the 1.22 Release Team



Reply all
Reply to author
Forward
0 new messages