Kubernetes SIG Release, 24 Mar 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20230324 (1.27 Week 11)

Description

Kubernetes Release Team Meeting for 20230324

A

A

Hey everyone: my name is Priyanka sagu and I'll be the host for today's meeting. We are in week 11 of the 127 release cycle um and yep. uh This meeting follows the cncf code of conduct, which pretty much comes down to, please be nice and respectful to each other. uh Today we just have myself and furkat on the calls, so uh it would be a quick one before I start with the team updates. uh Just a quick note that will be having a retrospective meeting uh around the closure of this release cycle.

A

So if anybody watching the recording are on the call wants to add any feedback or suggestions um for any Improvement for the release feel free to add them to the retrospective document, which is uh Linked In the meeting agenda document. Thank you with that. We can quickly go through the team updates.

A

um First, we have enhancements um I believe from from Wednesday update. It looks like BL green. We are past enhancement, fees and Court. Freeze. uh The only update from the enhancements team is, they have opened up enhancements, uh sorry, exceptions, um uh tracking PR for for tracking all the exceptions that they had received during enhancements, freeze and code. Freeze time so, uh if there happens to be not no more exceptions, now uh enhancement steam would be merging that.

A

So that's the update from enhancements um moving next to CI signal um I from last uh Wednesday update. They were green, but we just had a RC cut, maybe yesterday or today morning, depending on the time zone and after that I see some activity on the master, blocking and master informing boards. So there are failing as well as flaky jobs.

A

um So that's a bit of a change from Wednesday. Maybe it's because of the RC zero cut um and I am hoping. uh The ca signal team is looking at that uh moving next to back over to you.

B

Sure, thank you on the battery. We are green. We don't have any rules blocking issues or PRS, there's just one um on issue for the late test that the discussions are ongoing. So overall our status is clean. Thank you.

A

Call it uh just just a question: um does bug triage uh Team for them anything changes? If, if the CI signal boards are red, uh would you be the team tracking those issues or those issues will come up on your board? Something like that.

B

um Most probably not uh because I didn't see it so far, the correlation between CI team board and the bug tree dashboard. As far as I know, they are separate.

A

B

But if they are, if there are failing tests and like with specific Milestone that, then it should end up in about three years old I believe.

A

Okay, okay and and that's uh what I can see yeah, they are tracking a few flaking tests, so good I believe the failing one started later. uh Okay, thank you for that for the uh updates, and uh next we have docs. um So Mickey has updated. Their overall status is green. They are still waiting on the PRS from two caps um that made into the code freeze.

A

um They have reached out to the cap owners through the issue and wireless live channel, so I believe uh they have received some updates.

A

um Not yet so, maybe on slack and yeah they're also reviewing the rest of the doc PRS that they have received um out of all uh I, believe 39, March and 40 are still um ready for review and they're still, two, no no PRS I believe that's corresponding to these two ones and out of all, um there are five gaps which do not require any Docs. So that's the update and they're also waiting on com's completion for of the release blog draft uh in order to provide a review with that.

A

uh Moving next to release, notes, I, don't see any update here so I'll just try to quickly read Wednesdays um looks like they were green. The team is working on release, notes, draft and website PR for 127, beta0 release so and, and last update was they were expecting the pr to be merged by this week.

A

So maybe uh that's that would be the update now and I have seen some activity from release notes reaching out to six individually to find out the major themes for this release, so I think that's going to be an ongoing task for this week as well.

A

um Next we have combs and uh it's the same. uh They are also working on the release. Blog and overall status is green release. Branch management uh I believe, like the overalls uh status or update from release. Branch management side is the RC zero cut which happened uh yesterday or today morning, based on the time zone, but that happened successfully. So that's the update from release Branch management side um next, with Emirates advisor James, um I'll, just repeat: Wednesday updates.

A

um The advice is to look for succession for 128 release cycle so uh for leads uh reach out to your shadows. If anyone is interested to participate or if not uh reach out to Emirates advisor for any help finding out the next lead and for Shadows, if you are interested in being the next release, lead uh or team leads um definitely reach out to your lead and share your interests. Thank you.

A

um There are not any updates from our release. Lead site uh other than uh I I would believe the r60 cut. So with that six scalability um no updates- and we are done with our team updates for today's meetings. So with that I'll stop the recording um I'll just check with you forgot. If you have anything uh to discuss.

B

Nope, not nothing from I said. Thank you.

A

Thank you and with that I'll stop the recording. Thank you for joining the call.

A

I hope it foreign.