Kubernetes SIG Release, 15 Mar 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20230315

Description

Kubernetes Release Team Meeting for 20230315

A

A

All right, good morning, everybody uh welcome to uh week 10 of the kubernetes 1.27 release cycle, uh just a reminder that, as this is a kubernetes project meeting, we do have to comply with the kubernetes code of conduct, which boils down to just please be nice to each other.

A

um If you are here, please remember to put yourself in the attendees list: I see everybody doing that which is which is great and lovely and helpful ow. My cat's biting my chin. uh That was a code of conduct, violation, espresso and we're going to talk about it later.

A

um Anyway, let's get started: do we have any open discussion topics here? The day after codes code freeze, nope, sweet uh we can get going with sub team updates, then first up is enhancements. Enhancements. Are you here.

B

14Th of March, uh now we have total of 54 PRS, that code Piers that are totally merged. So uh that's a lot of peers that are that have passed the uh kep requests uh and um we have received for now. We have received for an exception request and we have granted all of those and I have. We have just uh mentioned all of the exception: requests in the notes. So yeah, that's about it.

A

Thank you so much any questions for enhancements.

A

Cool, so up next is CI signal.

C

So hello, everyone, so the current status is yellow because we are seeing the two failures on Master informing and it is being actively worked as we speak to the respective sync, like we reached out to the API Machinery folks and uh they are working on it, so it will be resolved soon and we are seeing some flakies, like nine flakies on Master, informing and uh no blockers on Master blocking and five flaky on it.

C

So, yes, uh we would like to resolve this to failing on Master informing before we uh give the go non-go signal uh for tomorrow. So yes, that's it. Thank.

A

You thank you, questions for CI signal.

A

Alrighty bug triage.

D

Hey everyone, uh our current status, Who's Back trash, is yellow. We have one release blogging issue that we are tracking since last week, which is still open, and the discussions are ongoing on that issue. Otherwise, a lot of PR's tracked by the team members were merged this week, just before the code 3 started and some moved to the next release milestone.

D

um So our goal from now on until the test free, is to watch for potential the release, blocker issues and make sure they're resolved before test freezes in yeah. That's all for back trash team thanks.

A

Thank you, questions for bug, triage.

A

Alrighty uh next is Docs.

E

We have given the bathroom speaker and updates from outside.

E

A

Okay, uh do we have any questions for the docs team.

F

uh Not a question just to follow up on the OneNote there. uh Yes, the communication was sent out to leads at kubernetes.io to remind them to get placeholder PRS in by it by the deadline. So um yeah perfect.

A

Okay, next team is release, notes.

G

Hey everyone uh release notes is green. um The major themes Divine is next Tuesday, the 21st, so we're continuing to engage and work with the six to finalize uh the this.

A

Okay, great uh any questions for release notes.

A

Sweet uh up next is comms. They haven't entered any of their updates. Here is anyone from comms here who can kind of fill us in.

A

No okay: we can follow up with the comms team offline. This is uh just now when comms tends to get a little bit hectic. So it's probably fine uh release Branch management. uh Cc. Are you here, nope.

A

And James is also not here, so we probably don't have an update from our Emeritus advisor then uh Xander, it's over to you.

F

Yeah so code freeze last night, um we've gotten a couple exception, requests that have all been approved so far and I I anticipate there will be some more coming through, but um all in all it's it's been pretty straightforward.

F

um Yeah from here I'd say um you know, continue to add things to the retrospective document, um because we'll do another one of those after the release and then leads um continue to to think about succession um Shadows reach out to your leads, if you're interested in in leading your role for for the next release um and leads, if you need any help with that or have any thoughts or anything, please feel free to reach out to myself and James we're we're here to to kind of help with that process, um yeah trying to think.

F

If there's anything else, um oh I believe we will kick off. um Yes, we will kick off Monday meetings, starting this coming Monday the 20th will be the first month. So at that point we will start meeting Monday Wednesdays and then the APAC time on Fridays um and then we'll do I, don't I We're, not gonna. Do the like go to everyday meeting like we have in some past releases, we'll as we get closer and closer to the release day, we'll do asynchronous uh check-ins on Tuesday and Thursday um yeah I think that's everything ahead.

F

A

Perfect uh six scalability, not here as usual. That's that's fine. They don't need to be here um so I think we're we're good. Is there anything else anybody would like to discuss on the recording.

E

A

Okay, uh I will go ahead and stop the recording. Then thank you for coming. We happy code freeze.