Kubernetes SIG Release, 16 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting (1.26) for 20221116

Description

Kubernetes Release Team Meeting (1.26) for 20221116

A

A

So uh good morning uh my name is Kat and I am the host for this release team meeting uh we are currently in week. What 12 week 12 of the 1.26 release um Please, be aware as usual, that this is a kubernetes community meeting, which means we are under the purview of the kubernetes code of conduct effectively boiling down to be excellent to each other. uh Also, a reminder that this is going to be publicly posted to YouTube, so be careful. What you're saying you know, let's get in there.

B

A

So uh I don't think we have any open discussion topics nobody's parked anything in here, so we'll dive right into it with Team updates. uh First up we have enhancements with Mark hi.

B

uh No real updates from since.

A

B

Time, we're still green and I think we're still tracking all the same number of caps. So nice and short.

A

Perfect, that's that's what we want this late in the cycle, honestly, I, don't wanna! Nobody needs to be listening to super long uh updates. When we've got three of these a week, uh CI signal. Do we have anybody from CI signal with us.

A

Moana are you here looking like no light meeting today, that's okay uh bug triage with Hussein.

C

um Yeah I am from the bacteria stream and it is also green for us. There were some issues that had been added to our port and the team already assigned them to themselves. So this is update from our side.

A

Okay, perfect. Thank you.

C

You're welcome.

A

uh Docs with cat.

B

I sorry couldn't find my unmute button, um so our current status is yellow. Our ready to review deadline has passed, but we do have some. We still have some missing PRS, so we're doing some Outreach um updates are kind of where we're at we're tracking our insights. In this um you have a little uh graph that pulls all the all the information Reddit reviews at 16 draft is at 10. Complete emerges at six and no PRS are at two, so we're just working towards um getting some answers there sweet!

B

Thank you yeah I, just one more one. More item. Sorry I forgot to add this one in, but we do have an open, um an open PR to merge uh or to keep our branch in sync. So if anyone is able to take a look at that, that would be great. I can add it here. Okay, you.

A

Can get that taken care of uh any questions for docs.

A

Cool uh up next is release notes with Rodolfo.

D

Okay, um our current status is green. The draft board request for release notes for Alpha 3 was merged yesterday, so we are good for now. uh We also sent a second reminder to slack channels in six in order to collect mayor teams and known issues for this release, and that's all for now.

A

Perfect uh questions for release notes nice comms with Federico.

A

I know I saw him oh you're, muted in Zoom. Sorry, yes,.

E

Hello, um so um current status is yellow. This is It's just yellow because of the last Point, uh because uh the the deadline for the initial draft for the release blog article and is today I, don't think that's realistically, we will uh publish it today because there's still, as it could also said, some work being done on the major teams, um but nothing major I think that until the end of this week this will be um up. Apart from that, everything is fine.

E

We have 15 feature blocks being tracked um and we we've opened the mid cycle deprecations and removals block PR for review for publishing in the next couple of days.

A

D

Ly we have only two major teams. Can we add those to this draft.

E

um Yeah yeah, that's exactly what I'm doing so, since it's a draft, obviously there's it's easy to comply with. Is that that with this deadline, I just need to put something but I I actually wanted to add something closer to the final uh thing. But yes, uh I will use what we have in there um and uh in if tomorrow uh we have something more um I. Think it's it's better to reflect that immediately and publish the draft with that. So I I I had to take more care of the mid-cycle pr block yesterday.

E

So I wasn't so up to speed with that one I'm targeting um this for tomorrow, so that we I think we're good and I'll I'll reach out to you for a further discussion on this. Okay.

D

Sounds good I also will review the blog that you posted in this week in order to to do a look, excellent thanks.

A

Up next is release Branch management with Jeremy, who uh is not here.

F

Yeah I got this one, get it um yeah, so uh we cut RC zero yesterday and that that went well. So if you look on KK now, we've got the release. Dash 1.26 Branch live um so yeah. Hopefully continued smooth sailing from here.

A

Perfect, thank you. uh Emeritus advisor nabaroon is also not here and I'm here, because Leo is not here. So the update from release lead is that we're just focusing on bugs and failings to get the test grid green. uh Do we have anybody here from six scalability.

A

As usual now but says, the test look good, so we're all good there. um I guess! That's it for team updates. Is there anything else that we wanted to discuss on the recording.

A

No okay, I am stopping the recording, then thank you all.