Kubernetes SIG Release, 21 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20221021

Description

Kubernetes Release Team Meeting for 20221021

A

Hello: everyone welcome to the first Apec Friday release team meeting for the release like 1.26, so that a is Friday the 21st of October. um We are a couple days before kubecon um and today.

A

We will walk over the notes, as always all right. So, let's see if, if you like, you can add yourself to attendees list the link to the meeting notes this in the chats and, let's start with the open discussions.

A

So as it seems there is nothing really on the open discussion list. As always, if, if you have like any ideas how to improve the release team in general or um any any feedback, maybe some things that bothered you during this process or things that you really liked. You can add it to the retrospective.

A

There will be a retrospective in I think, like a month around the mouth and then also another one at the end of the cycle. So this is a good, a great time to hand feedback all right. Is there anybody new um who would like to introduce themselves I think everybody is already.

A

Have already introduced themselves to the previous meeting, so let's move on to enhancements with atawa.

B

Hello, uh everything is looking good for enhancements. uh This current status is green. Some of us has already started uh the reach out before the code freeze, but uh because of kubecon will almost complete most of our reach outs uh after the cube Conway. uh So that's that and currently we have the same updates as the previous meeting. We have currently four exception, requests which about which three are approved and metrics are 52 currently are now dragged, and there is one alpha. The alpha announcement, stacking alphar about 24 uh tracking for beta is 13..

B

The deprecation is one we have one deprecation enhancement and um yeah.

A

Awesome sounds good, I think also the um exception. Requests are already done right, so it's yeah yeah.

B

A

In everything, from PR reviews and stuff, great yes,.

B

Yes, uh also, we had a meeting uh on 19th where we discussed about the further reach outs and about uh code freeze and uh improving the GitHub project board. So we have a issue about it in the GitHub, so we are currently working on how we can improve the overall GitHub project Sport and how we can automate all this stuff.

A

I think on on Wednesday somebody asked if there was a recording of this meeting, that you.

B

Yeah I couldn't uh there was not. Unfortunately, uh let me ask again to the lead uh if he had that recording, but.

A

I think it is I think about it. Yeah I think there's also meeting notes. So that's that's great. um All right any questions or two enhancements.

A

I think this topic will also get picked up at kubecon. So if, if you're interested in the enhancement project board, there will be a session Graces, organizing this or hosting this on the contributor days, I think on Monday.

A

um So that's also good good time to discuss the enhancement project board, all right. Moving on to CS signal new Vietnam make it with us or somebody else from CSI.

C

And I can give the update, so there was one failing job a few days back, but now it is kind of flaky and their status is green. For now,.

A

Okay, okay, did you receive any feedback on on the failing job or no? No, okay, fixed?

A

Okay? Now, that's good! Okay! Yes, all right any questions to see a signal. Otherwise, let's move on to bug triage.

D

Hello, everyone uh we are green, uh nothing has changed the only changes that you know. We are using a daily job to sync new PRS and issues to our guitar projects. So there's automation there, it's now it's relying on a private repo. You can see yeah it's a fork of the cigarette repo. uh As soon as I get green light. I will uh yeah I will merge it back to the Upstream project.

A

Awesome, that's nice.

A

Okay, did you already open the pr or no.

D

Not yet I think I will open it today or tomorrow. All right.

A

No more no rush awesome, so everything looks good. um Any questions about triage, otherwise to the docks I see, there's no update, so I will quickly check the class update. So last update on Wednesday was Green.

A

We are tracking docs changes that are uncovered by caps right, um so there there's a discussion um about that. They created a new project board so at the moment docs tracks on the enhancement project boards and also now on this new project board. So this is obviously not so ideal to have multiple places to look for so there's a discussion happening, probably at kubecon, and how to improve this.

A

um But besides that I think the overall status is is good. It's green should be green, and so, let's move to on to release notes it's there. Somebody from release, notes who would like to give the update.

A

Otherwise, let's check again also green draft PR for release notes for offer to merge to website PR police notes for author to merged. So everything looks like things are in motion. That's great.

A

And let's move on to columns is somebody from cons and yes.

E

I can give a update, sorry uh we're two weeks um before the sort of cut off for the feature block opt-in, so we're reaching out to the six and the the stakeholders to see if they are wanting to do the PRS for the blogs and then we're working on the initial draft of the midline. The mid-cycle interpretations, so um we're yellow at the moment. But we're hoping to sort of turn that around by by next week.

A

A

Do you need any other reviews on on the feature block or something like this I I posted some comments in the chat.

E

um I haven't seen that one sorry, um sorry.

A

Yeah no worries um I think just because next week is kubecon, everything will be quite chill, I guess so. After a coupon yeah.

E

Yeah I'm hoping to talk to a few people there about it as well.

A

All right sounds good, any questions to comms.

A

Otherwise, let's go to release Branch management. I guess nobody from release. Branch management is in the core, but actually right now, there's nothing nothing to do so.

A

Last last status was green. I guess this one should also be greened for today. So next cut is on the 1st of November and then release engineering is improving the image promotion, tooling, yeah.

A

So this is maybe also if, if you're interested in general, like for or sick release- and maybe some other places there's also another team. So we are the release, release team, that's also the release engineering team. So, if you're interested into like how the overall, like processes, work, image, promotion stuff like this there's a meeting on Tuesday which you can join, which is always very interesting.

A

All right, then, to the EA I'm going to I think also not in the call but I guess he didn't edit anything to the meeting notes. So I guess everything is looking good and then to my updates. So this is just a reminder. I think everybody's aware next week is kubecon, because everybody should be quite busy around this time or it's usually usually the case that most of us are quite busy or are at qcom.

A

We will not um set up this meeting next week, so we will just I will just post a threat in in a meeting channel uh in in Securities, and then everybody can give an update via chat. There should be a little bit more relaxed and we don't have to jump on a call for that.

A

All right, that's that's it! For this meeting. Are there any comments or questions before I? Stop the recording.