Kubernetes SIG Release, 5 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Kubernetes Release Team Meeting for 20221205 (1.26)

A

All right welcome to another uh release team meeting. We are in week 14. uh just a reminder. This is a kubernetes release, team meeting and as such, we are required to follow the kubernetes code of conduct, which boils down to be nice to each other. Thank you, uh open discussion items.

A

um I, don't think we have any other than please add any comments and suggestions about the release process to the 1.26 retrospective doc, so we can discuss it that is linked in the agenda as well.

A

uh Let's get straight into it with updates. We are very close to the end of this release. Cycle uh first up is enhancements.

A

Nobody is here from enhancements. That's okay, um but status is green, so I'm not too worried about it. Anybody here from CI signal.

B

Hello, everyone, so current status is green on Master blocking we don't see any failing jobs and there are nine flaky on Master informing. Also, there are no failing and six flaky, and also we are observing uh 1.26 blocking and informing. There are two flaky on it, so that's it from CI signal. Thank.

A

You thank you. Any questions for CI signal.

A

Sweet easy meeting so far uh next up bug triage.

C

Yes, hello, everyone uh so last time this is green. Nobody can use lprs, so we're good.

D

A

Okay, any questions for bug triage.

A

uh Next up is Docs.

E

A

There you are, can you hear.

E

Me yeah I'm, sorry, I was okay. uh Well, I am wearing the status red because I I have two pull requests ready to review that I will try to marriage today, I am being I, am sending a message in the secret note. Well, the responsible seek for this pull request and yeah I think this will be my status. I, don't know if you have some questions.

A

uh Is there anything we can do to help you.

E

Yeah I will put in CCC and copy to Leo and the documentaries also to help me to push the review, because it's an open pull request that the maintainer needs to apply to the suggestions. That's all okay,.

D

Yep, so the the two ones are open for quite some time or work under work in progress for quite some time and I. Think the first one or the second one in the list just recently opened up because there was like basically um like a dependency, so the dependency merged I think on Friday. It was was a huge discussion around it. um So that's that's clear so hopefully um I mean both are kind of ready to get merged. I think so. Hopefully we can get this pushed through soon. Today, yeah, okay,.

A

uh Any other questions for docs.

A

Okay, uh release notes.

C

Okay team, our current status is yellow the website, release, notes, PR for Arch, C1 was merged, and but the Alpha 2 is beginning to be interviewed and I added to copy to those people that we need to review and we are Jello because we are working on the other two pull requests for Alpha, 2 and rc1, and we hope we can have those before Wednesday and but yeah. We are pushing to to do that before that before that day,.

E

A

Any questions for release, notes, cool and then comms.

F

So we're green um all 15 feet: blogs um have their dates. They have been communicated to the owners. They have changed them. uh We are ending the the review process for most of them, so that part I think it's fairly uh done. um Cncf we reached out to cncf both the pr and the webinar are taken care of in Terms of the announcement, and also of the date of the webinar.

F

Just waiting for the event link uh the review, the release article, it's nearing the the final release form commits, were squashed and um just waiting for a couple of the link for the webinar and stuff like that, pending any last minute review from someone it's as good as done so we're in the pipe five by five.

A

Perfect any questions for comms.

A

Okay, uh release Branch management. Do we have Jeremy here.

G

Believe Jeremy's out today, yeah oh poor thing, I guess my camera's not working too whatever um yeah I I guess not much of an update beyond the release is Thursday um so yeah following the the delay for the go release, push to Thursday, um yeah and I. Believe Jeremy will be the one to cut that release.

A

Nice, clean, perfect, uh okay, then it's the Emeritus advisor number one. Are you here, hey.

H

Everyone I'm here hello and happy Monday, so the issue for assembling the release team for 1.27 is our um and we already have our next studies lead and Emirates advisor congrats to Xander for.

A

H

Nominated as the 1027 release date and James I think he's not on the call uh he's nominated to be the Emeritus advisor for the next release. Cycle really excited to have this team um and for any leads on this scholarly PSA.

H

um If you have already decided to nominate whenever you can, uh whenever you're, free or if you still have doubts like please contact like Leo and me about any pending doubts, you might have regarding selection, um going ahead, uh Thanks James again, James uh graciously like volunteered to uh take notes for our part, two retro and Jeremy is already uh has already volunteered to uh run the electron meeting.

H

um That's all! On my side, um two things are still pending, uh sending out the lead survey and Shadow survey, which I'm going to do maybe tonight or maybe tomorrow morning, uh but we are on track and I'm going to work with James under Leo to get like uh to get the process for the Shadows survey. uh The selection survey for next release cycle up and running so that we can at least send out the form much before the vacations and close it out right after the vacations.

H

um That's all on my side! If anyone has any questions comments, certain things.

A

Thank you. Any questions for Navarone.

D

No question but um for the next Shadow survey um probably I mean we discussed it I think in the last sick release meeting. Maybe we will make some small adjustments just to compress it a little bit.

H

D

It's a little bit easier also for the release: Team, Shadow application tool to process process the form and everything. So if anybody is interested also in the tooling, because there's also a couple of issues open, maybe they bought already closed them, but I can also link the project in a second. So you can also get involved. If you like,.

A

Okay, uh next up is the release lead so Leo did you have anything else you wanted to say for the.

D

End of the no not not really I mean just following up on with dogs stocks at the moment, also because of the red flag, but also with um like it's it's it's sometimes a little bit tough to basically get responses uh very fast from people and merge things in, but I think we are kind of close.

D

um Hopefully, everything will work smooth with the version bump of golang on Wednesday or Tuesday, depending when.

A

D

Yeah tomorrow, but like who knows when the versions will be cut in maybe I don't know in the evening on Tuesday, so for us on Wednesday, but hopefully everything goes fine and um I think everybody did a great job and yeah thanks. Everyone.

H

A

uh Nobody here from Sig scalability as usual: that's okay! um Is there anything else we wanted to discuss on the recording other than congratulating Xander.

A

Okay, stop the share and stop the recording.