Kubernetes SIG Release, 10 Mar 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20230310

Description

Kubernetes Release Team Meeting for 20230310

A

I've done my work, so it will be quick, hey everyone. um My name is Priyanka sagu and we are in the week nine of the release uh cycle. 127.

A

um I will be the host for today's meeting and this meeting abides by the kubernetes cncf code of conduct, which pretty much come down to. uh Please be nice and respectful to each other.

A

um I have Brad on the call with me, and this meeting will be a little quick uh because we'll be mostly repeating the updates from our Wednesday meetings, uh with some exceptions here and there. So um I will start and just a note for you. Brad I will put a link to this document and please.

B

A

It on my screen: okay, good- um if you can add yourself as an attend leader yeah. Thank you. So um we can start with the team updates quick, um but before that uh we have a link to the 1.27 retrospective document. uh So if there are any feedback, uh please feel free to add them there now to enhancements.

A

um We are green um I think there will be more activity for enhancements in the coming weeks uh because we are reaching code freeze next week and after that enhancements team will start tracking the already tracked enhancements again for whether they have reached the code um requirements code, completion requirements or not.

A

So we might see some activity from them polling next week, um but for right now it's green over to CI signal um I, just checked the test grid board for master, informing and master blocking release jobs, and it's same as for what is what was on Wednesday. We have six flaky and one failing on Master, informing the difference being the one flaky we have, which is uh capsi Windows container D master. um It's dragged as flaky in the CI signal tracking board at the moment, but it has now started to fail.

A

So I might reach to one of the shadows, and maybe we can start tracking it as failing and look into it um otherwise rest of the rest. Everything is okay and we do not have any failing on Master blocking uh and for flaky, which are already dragged um on bakriage.

A

um It's same as last week. We have one release blocking issue at the moment: uh that's being worked upon by the community, so we might see some more updates on that um and it's regarding yeah.

A

um We don't have any critical, urgent issues, no important, soon issues, um just in total five flake issues um and 39 open kkps for 127 out of them. One is critical, urgent and 22 are important soon for docs, it's green for them. uh The docs theme have started to refresh the docs branch and they're planning to do it continuously. Every week on a weekly Cadence, now onwards and um same as enhancements, they also have assigned their Shadows to the track enhancements and they are reaching out to them.

A

Talks. Placeholder PR deadline is March 16th, which is six days from now, so there is more activity going on there and we might get an email from Xander on the dev mailing list. Regarding the same release, notes um it's same uh as last as well as they're meeting it's green.

A

They have uh published the release, notes website for 127, Alpha 3 tag, and the draft PR is also moist for the same comms. um For comms. There is a bit of a difference from Wednesday uh 22 feature: blogs were up opted in with the placeholder PR, but I I saw some update from the comms lead a while back so at. As of now, the number is 19.

A

um and same is there on the tracking board um from release Branch management again the status screen? uh It's it's around 127 Alpha, three cut, which is done now and uh announcement email is linked in the document from Emeritus advisor James. So we had our mid-cycle retrospective meeting last last to last week um and following that, uh the Shadows uh might expect a shadow survey to come soon from James um Xander are released from them.

A

The update is only about the code freeze which is coming next week, so we might see more activity in the release cycle again: uh postcode, freeze and yeah. That's all the updates we have for today um with that. I will stop the recording and thank you Brad for joining me on the call um you are part of the com stream and if, if I see it correctly, like number has changed from 22 to 19, that's correct.

A

uh You are on mute. Sorry, sorry.

B

The one thing I'll just copy shame has been okay, uh it's disabled, I can't share it. Oh let.

A

B

A