Kubernetes SIG Release, 2 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting (v1.25) for 20220802

Description

Kubernetes Release Team Meeting (v1.25) for 20220802

A

This meeting is being recorded.

B

Hi everyone good tuesday, welcome to our kubernetes 1.25 greatness meeting. Today we are at week 11., it's tuesday burn down meeting on 2nd august and as europe, this meeting is under the same safe code of conduct, which could be summarized as please be nice and respectful to each other.

B

I have pasted the link to the meeting note on the chat, so please feel free to register or attend this there, and if nobody has any open discussion topic, let's move to the enhancements update anyone from enhancement team in the call.

B

If no, I will quickly give an update on mostly I just said before. We currently have 22 enhancements marked as at risk- it's maybe not as accurate as it is, but it's your huge number and- and we have received a full um exception- request now um before code phrase. Our code phrase is in eight hours and while the pull request has been approved, two of them has been rejected and we are still evaluating the last one.

B

That's the current status and we will look for more exceptions coming around code phrase or after cut phase and let's move to ci signal um arch. If you are here or if anyone from ci signatum here, no, let's just quickly checking the report, it seems like we still have to fill in um hope that will not block our um beta card this week.

B

C

Guess I'm just looking at master blocking and there seems no failing right now. It's not totally fighting right now, but one failing master, informing.

B

Thank you so much. That's a good good to know.

B

um I'll double check in the ci signal channel after the meeting, and hopefully people will.

B

Thanks leo for adding the details, um that's great, we don't have any fitting jobs currently on master blocking and, let's and in question for ci signal.

B

If you know, let's move to bug triage hussein, if you're here.

C

Hi, yes, um since yesterday we received few new prs and issues. I just think the the folks in the in the team, uh I'm just going to update uh the guitar.

B

C

Board with the new uh issues.

B

D

C

But currently we are green. Nothing um c is for the uh release cut, so we.

B

C

B

Thank you so much any questions for about triage team.

B

No, let's move to dog's team cat. If you are here hello,.

E

Oh wait: there's two cats.

B

Sorry, I'm asking both dogs tim.

F

Hi I'm doc's cat. um uh The current status of the docs team is green. um The pr from last week has been merged. Another one will be opened either today or tomorrow. um We're continuing our outreach with our placeholder, our placeholder deadline for august 4th, so um the sheet has been updated and they have it's been reflected. It's been updated to reflect, remove milestones and approved exceptions.

B

Thank you so much any questions for dog's team.

B

No, let's move to release notes tiptoe. If you're here.

A

Hi, so we have contended all the 6 for the major themes and some of.

B

Thank you so much great to know. The major scenes goes well and any questions for release notes.

B

If no, let's move to comms cat.

E

Other cat: it's me this time, uh so we only got four placeholder prs outstanding, which is um pretty good, and I think we will track down those last four in the next two days and anyway, it's not really like catastrophic.

E

If uh some of them come in a little bit late, they are just placeholder pr's and it's kind of just for tracking, mostly um got more changes requested to the deprecations and removals blog, some of which I think I am going to shut down, because it's feeling like it's getting a little bit nitpicky um it's supposed to mention like api, deprecations and major changes.

E

But it's getting to a point where people are requesting every single little tiny, conceivable thing be added to it, and the blog is getting very long at this point, um but it is still on track to fire on the fourth I'll. Make final calls on what gets added and what doesn't after code freeze tonight, so I uh don't have to go back and edit. It afterwards, like we did last cycle, but um we're we're all good over here on the comms team.

B

Thank you that's great to know, thank you for the update any questions for comms team.

B

Now, let's move to release branch management veronica, if you're here, yes,.

G

Hello, um the code freeze, pr was just submitted a few minutes ago by jeremy and we will remove the hold at 6 pm pacific time so yay. That's it.

B

That's great, thank you and question for release brand management.

B

If no, let's move to ea ray.

D

uh Such one thing for me it just the um mid cycle. Shadow survey is out it's completed by uh and update this friday, I'll, probably close it early saturday mornings, there's so end of day, it's very fluid um and then other than that I've talked before about succession, so we're talking about about the 1 2016 or start to think about building out the 126 team.

D

I'm going to reach out and um uh two row leads independently in the next after code freeze or a day after code freeze, I want to make you know like to have some breathing room between cold freezing and um in the next milestone. So uh just look out for that um and that's it for me.

B

Thank you so much and for my update on the major thing of course, obviously the code phrase in eight hours and please feel free to join the code first party, if you're interested and as I previously mentioned, we received four exception, requests and we're still evaluating the last one. If you have any import, um feel free to um ping us or like join the um slack discussion and let's move to any questions before I move to other area.

B

No, um we don't have the scalability updated today and I believe we don't have the board update as well just to protect yeah. Before I end the recording any questions.

B

No, I will go ahead and the recording.