Kubernetes SIG Release, 4 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220804

Description

Kubernetes Release Team Bi-Weekly Meeting for 20220804

A

There there it goes: okay, hi everyone. uh Welcome to this week, 11 friday august 5th apac friendly 125 kubernetes 125 release team meeting. My name is jesse butler I'll, be your host. We are joined by a handful of folks we're going to walk through the agenda, so this is a kubernetes meeting, which means that it is a cncf meeting and falls under the cncf code of conduct, which summarizes nicely as please be awesome to one another.

A

um Let's get started so open discussion.

A

We, I don't see anything. uh So that's we can just get right into the team uh updates. So, let's start with enhancements jason.

B

Hello, hello, we're all green, green green after our code freeze on wednesday. uh Most of our exceptions that we had are all kind of done. We have a couple of new ones coming in uh like the new one that we I put in the updates today, and we have uh an old one that is at risk.

B

We just hope that all of them should get done by monday. Yes, fingers crossed.

A

All right awesome, that's great good work. um Does anybody have any questions for enhancements.

A

Okay, fantastic, thank you, jason, nice work. Team uh brings us to ci signal. um Is someone here representing ci signal?

A

Don't think so?.

A

Okay, um let's just for the purpose of the meeting, let's look a yes, so last day we saw yesterday their status was yellow. um I think that they were tracking um at least one thing. I was aware of.

C

Yeah, so looking at the dashboard, we don't have any failings right now and one sort of massive blocking and one fading on method forming. So from that perspective, I think, is still yellow status. Yeah.

A

C

A

Seems reasonable yeah we have an implied yellow, I think, that's perfectly reasonable, um no big red flags, okay, anybody else want to say anything around ci signal.

A

Cool all right, thanks uh moving to uh bug, triage uh and hussein.

D

uh So currently we are green uh so yesterday or yellow because of the one of the release card. uh Blogger issues regarding um go 1.19, um plug-in problem, but I think it's resolved because it was supposed to be patched by co-119 ga, so that is resolved. So we are again green and everything going smoothly for us, fantastic.

A

Any questions for bug triage.

A

Awesome, thank you good work. There team um it brings us to docs. I don't believe we have anybody from docs.

A

We don't have a status so again we'll reach into yesterday's. I think that they are green, no yellow, okay. um I missed yesterday's meeting.

A

Yeah so they're. This is very typical, docs um right around now, so I'm not. This is yellow, but really just for tracking purposes. um It looks like a lot of their work, got a signed out uh thanks to ray he kind of jumped in and helped out there. So we're just going to imply a yellow status which is in in my experience, probably trending toward green but we'll we'll say: yellow um anybody have any callouts for docs.

A

Cool, um so that will bring us back to today's meeting and release notes, which also doesn't have a status update, and I don't think anybody's here for release, notes.

A

All right so august 4th tells us that they are green um yeah. They have both of the uh website and release notes. Aprs are already up and in review, which is great, um does anybody know where we're tracking um the themes major themes are? We is.

C

That underway yeah, I can't there's an issue um to discuss the major themes. I can paste the link in chat.

A

Once I was just, I just wanted to make sure that it was. It was ongoing because I hadn't seen it so good deal.

A

um So release notes is an implied green for today and then their major themes, discussion issue is up, which is which is great. The thread is up I'll, just open it briefly awesome yeah, it's been been up for a week. It's getting traffic good deal, that's what we like to see fantastic, good work team.

A

uh That brings us to comms. I saw oh any anybody have any call outs for uh release, notes, okay, cool! uh It brings us to cons and cat. I just saw filled in some uh status here, calling green um the mid cycle. Blog is ready, yeah. I think.

E

No need to scroll up yeah, it's uh yes meetings, so uh the present status is the wide cycle blog is already out, uh might need a follow-up vr, because there were few last minute suggestions uh which uh didn't uh get masked uh like the pr. What was before those changes could be made. Also, all the feature blocks that we were tracking placeholder pr are in place. So we agree yeah.

A

Nice, that's awesome, I'm so sorry. I got confused because I had to go back to yesterday's meeting so much and I I literally landed on your name in the in the participants. I was like oh you're here and now you're talking, so I apologize. Thank you so much, let's see yeah. Does anybody have any questions for comms.

A

Okay, great, thank you so much and uh awesome work player team um back on our correct meeting here. Yes, the fifth and that brings us to release branch management um that looks like so we, uh the beta release, is oh leo you're filling stuff in you wanted to speak to it.

C

I'm just updating the docs so yeah yesterday um they were better. The first beta cut has been completed. Everything went fine, judging from the comments in the thread, so that's good yep.

A

Fantastic things, yeah, so we'd we'd, say an implied green there. I think.

A

uh Anybody have anything else or questions.

A

All right cool brings us to ea ray who said he could not make it today with regrets, uh but he did put out a mid-cycle shadow survey um and he's been literally all over the place and threads so doing he's certainly doing his job, as he always does. Thank you ray um and then cc also could not make it, um but she has filled in um status here. So a lot of exceptions came in um five were rejected. Fiber approved one is still under review.

A

um She calls out. The beta cut from yesterday is out and she is currently working on the release theme. um I think I call out most most of the exception. Rejections were around the time, so the timing and the amount of time needed um around soak and just trying to protect the build so I'd say um probably for for retro, we'll probably bring this up again and just um I think, the release time team is always trying to balance giving um cigs enough time to get things in and protecting the the quality of the release.

A

So, that's that's always the sort of set of trade-offs in the balancing game so um see that is still underway, with one exception to lender review. Does anybody have anything else to call out around release leap.

A

Cc's doing an awesome job I'll just take the opportunity to say that um and then I don't have anything on sixth scalability, um so we'll risk it and roll back here yeah. We, I don't think I don't know if we've had an update from them for a while, um which usually is no good. No news is good news um team agree, basically we're good there. um I don't know if we want. Does anybody want to walk the project board with so few people here?

A

I'm I'm kind of up two minds.

C

I don't think there's anything new on the project court.

A

Yeah, I think that we can. We can keep this short and sweet unless anybody.

B

A

Else to bring up.

A

Oh okay, all right! I'm gonna stop recording thanks so much everyone for coming and have a great rest of your day.

D

A