The April community meeting covered several ongoing efforts in the project:
We might see Tech Leads separating from Chairs as it is hard to figure out between TL and chairs in some areas whose approval is needed or who’s responsible for what. In some cases, this will mean the same person occupying both seats until they can recruit more. Relatedly, folks proposed adding terms for chairs. The proposal establishes 2 year term between reviews.
Paris reminded Leads about the upcoming annual reports, and discussed potential improvements.
The longest discussion was about not closing high priority bugs. Some serious bugs that are unresolved are being closed by the bot. Proposed: don’t auto-close
priority/important* issues with a
triage/accepted label in kubernetes/kubernetes repository.
Next Deadline: 1.24 Release, May 3rd
1.24 is nearly here! [RC1 is available] for your testing pleasure, or you can just wait for the final release.
With that, the 1.25 team is accepting Shadow applications, so if you want to experience a release cycle close-up, give it a try.
The 1.25 release cycle starts on May 23rd.
Quite a number of fixes have been cherry-picked back to 1.21, so expect a bugfix-full May patch release.
Last Week In Kubernetes Development (LWKD) is a product of multiple contributors participating in Kubernetes SIG Contributor Experience. All original content is licensed Creative Commons Share-Alike, although linked content and images may be differently licensed. LWKD does collect some information on readers, see our privacy notice for details.
You may contribute to LWKD by submitting pull requests or issues on the LWKD github repo.