Kubernetes SIG Release, 13 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Weekly Meeting (1.25) for 20220713

Description

Kubernetes Release Team Weekly Meeting (1.25) for 20220713

A

Hey everybody welcome today is july, 13 2022, and this is week eight of the kubernetes 1.25 release team.

B

A

uh Just be aware that this meeting is being recorded and will be uploaded to youtube and we do abide by the kubernetes code of conduct, which can be summarized as please be excellent and kind to one another, all right, um taking a look at the open discussion items um looks like the only thing that we have on this list for today is to please make sure to check out the 125 retrospective doc and get stuff added to that before the retro meeting.

A

So um that ends up being a super, valuable experience and we get a lot out of that. So definitely share any any feedback you have there. We definitely look through that. um So, let's get started with the enhancements team um enhancements. What uh what updates do you have for us today.

C

So the status for this week is green. We do not have any uh further updates from the past week. We did not receive any exceptions, so the status remains exactly the same as it was in the past week.

A

Awesome sounds good. Do we have any questions for enhancements.

A

All right, let's move on to ci signal.

C

So hello, everyone, our current status, is yellow on master blocking. We have two failings which we already reported and eight flakes in which two of them shown shoulder pattern. So we reported that and all, and also for the last three days we are observing a lot of uh flaky and failing issues. So thanks to the folks who are already working to resolve those issues and also on the master informing, we have two feelings and 10 fakes, so yeah, that's all from ci signal.

A

Sounds good, definitely let us know if any additional help is needed there do. We have any outstanding questions for ci signal this week.

A

All right bug, triage.

D

Hello: everyone, the bacteria status, is still green.

D

We have seven important soon issues and the 33 uh 36 prs and we are currently working on migrating to the project peter instead of spreadsheet, and everything works fine, except that we have to update it manually, but priyanka thinks for her she's working to make this happen automatically soon, um no plucker so far,.

A

Awesome, I'm so excited to see progress made on the projects beta stuff. Moving to that, I think it's going to be a huge help for everybody. um Any questions for bug triage.

E

All right, docs you're up yo uh docs, is green. We have reached out to uh almost all enhancement owners to verify if they need doc to say almost all, because I know I have a few to chase down so we'll be chasing that down as the cycle continues and uh looks like just about an hour ago, the latest uh dev branch sync pr merged, so we are green uh chugging along nicely.

A

Sweet any questions for docs this week.

A

All right release notes.

F

Okay, good morning team uh we're current status for release. Not theme is green. The release, notes, draft pr and the past release website pr are merged, so we are on track.

A

Sounds good any questions or release notes.

A

All right, let's move to comms.

B

Hey everyone, uh our current status is green and we currently have nine feature blogs in tract and a few more in the pipeline this week, we're continuing to reach out to six to collect more before we start assigning them to the shadows and the mid-cycle blog pr is going to be about this week, keep an eye out for that. That's it.

A

Sounds good a lot of green this week um any questions for comms.

A

All right- and I will pass it over to veronica- for release branch management.

G

Hey veronica couldn't be here, so I'm going to give the update real, quick. uh We are on track to cut the alpha 3 with new versions of the tools, so we're going to make sure all that stuff is good before we do the the actual beta and rc cuts later we're tracking the ci signal team status, so we're marking ourselves as yellow just to kind of follow along no no real issues.

G

If anybody has any questions uh happy to answer them or reach out into the release, management or sig release channels, if you have anything after this.

A

Sweet sounds good um and it looks like rey is out this week, but uh he mentioned he will be sending out the mid-cycle survey when he returned so um shadows when you get that it would be awesome if you uh were able to respond and get us some feedback there. um And lastly, I will pass it over to cc.

H

Hi good morning, everyone um so we started the apec final meeting last week and I just want to mention it's a great way to get involved, provide feedback, ask questions, etc. So please feel free to come if the time suit and the things um they're always a big issue to schedule the time things were around the world and the initial kind of doodle link is sent to all the team um which might also get response from the people who are not in um the specific area.

H

So if you have any questions regarding visit time, please comment provide feedback and also, please feel free to reach out to me directly on slack. If you have any questions on that, I was trying to double check confirm with the time last on last week's meeting, and it seems it's okay with all the current participants, but I'm not sure if I missed anyone, so please feel free to let me know and we're looking forward to the alpha 3 card next week. Thank you.

A

Sounds good looks like we might have an update from sig scalability here too. So anyone on the call that can speak to that.

I

Xander can I say a quick question. I want to jump back to cc real quick.

A

Yeah, of course,.

I

Hey cc, um I asked this rate: are we do we have a mid-cycle retrospective scheduled yet.

H

um We haven't got it scheduled, yet it's uh on week, 10.

I

So, okay, I have some deliverables like. I need to follow up from the last one, so just trying to check timing.

H

Oh yeah, so uh normally we will have the first retrospective meeting scheduled on week, 10 roughly and the third part or, if necessary, the or the second and, if necessary. The third part is scheduled roughly around the end of the release or after the end. After the release is getting out.

H

A

Cool cool: um do we have anyone on the call that can speak to this uh scalability update here.

A

If not, we can uh we can wrap this up in a cool 10 minutes.

A

All right, I'm going to stop the share and recording.