Kubernetes SIG Release, 7 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Kubernetes Release Team Meeting for 20221207 (1.26)

A

Hello, everyone welcome to the release team meeting today is the last release team meeting for the release cycle. 1.26, it's Wednesday. The 7th of December tomorrow is the final release, cut planned um Please, be aware this is security meeting, so it falls under the cncf code of conduct which can be summarized to be just excellent to each other, and with that let's get started with this meeting.

A

Are there any open discussion items for the last meeting.

A

I didn't think so. So, let's move move to the updates team updates, starting with enhancements mark, but no updates. Since the last time I'll get the numbers. The final numbers in right now right, awesome I mean at this point. We don't expect any updates. Any updates is probably a bad update. So that's good.

A

um Let's continue with cs signal with bawana.

A

That's correct.

B

Oh hello, everyone, our current status, is being uh nothing major update. Everything looks great, so yeah, let's see.

A

Awesome great, hopefully, the version bombs from Golden will not uh let any any job fair. That's that's good that we don't detect anything any questions for CS signal.

A

Otherwise, let's move on to bactriage with Hussein hello.

C

Everyone, um so basically we agreeing a couple of hours ago, new issue just popped up. If you open the link, you know in the blocking issues it's regarding kubernetes release boat. If I remember correctly previous release, we had the same issue, but it was fixed quickly. So I don't think it's gonna be a blocker. So that's why I put our status in green right.

A

I saw this um I think dims posted this in a chat. I, don't know if you.

B

A

To posted something here: no, but.

D

A

In the chat so there's there's a fix, yeah, ready or already merged. So exactly.

C

Yeah, the same was in previous release, so final um yeah status from our side. It's a goal.

A

Awesome yeah for for that I will I will open up a thread tomorrow again for the final go and Logo signals. Okay, you see, that's that it's green any questions for bug, triage.

A

Otherwise, let's go over to dogs.

A

That's Carol.

E

Hi, can you hear me yes, okay, yeah I was putting the informations uh yeah I think uh our current status is green, I put yellow because we have this pull request that we have a lot of discussions. That I think is these documentations about this cap. It will be improved after the release. uh I think Leo. You know about this.

E

That is a big discussion. We open I already opened an issue. I think I would put an issue to track this for the next after the release and I think if, but uh after that, I think we could think that this aggregate status, because we need to continue with the next steps, that is, that I I was writing here for a then before release.

A

Okay, I I, haven't saw in the last couple of comments. I thought this. What naproon posted was kind of the uh end of this story? I mean at the end this this cap, I mean the documentation. Part is very minimal, and the problem with this one is that we didn't had like the um like documents ready to document this particular change.

A

So it was basically a dependency and dependency was quite huge, so this was delayed for a long time, um but this I mean this should not block the release, because it's like a small documentation, change, I, don't know number one or somebody else maybe has more I.

D

Think I asked the clarification Down Below in the thread. um Can you scroll down.

D

Yeah, so by Tim's response. What I understand is it's.

E

D

Kind of a blocker for one or two six and it can be merged, Post Release as well. They will just merge into the branch and the dock would be available. Yeah, okay,.

E

So I think I can change to current status to Green. Okay for.

A

D

I think I would also just tag it as no docs for this release, because essentially they did not merge in Docs.

E

Okay, following the Nexus test for the day before release, I am doing these steps that I will change to hyperlink after that and I create this. This last pull request to sync the branch and also open the issue about the freeze.

A

All right awesome.

E

A

Think do you need any support on that or no.

E

I think the document trainers is helping me in this.

B

E

So I need the help.

A

I see Tyler is involved, it's it's great.

C

A

All right sounds good awesome. Any questions for dogs.

A

Otherwise, let's move on to release notes with Rodolfo your last.

F

Update yeah from from the last last update, we were Jello, but we moved to Green since the pull request for Alpha 2 was merged and the rough pull request for release candidate one. Let's meet it and review it. We are just waiting for addressing those comments and to be merged. Even if this pull request is not merged before tomorrow. It's not a blocker for the release day and since it can be merged any later. On.

A

All right sounds great.

A

Looks everything on track any questions for release, notes.

A

Otherwise, let's move on to comms with Frederico.

B

um Com status is green of the 15 filter blocks that we have eight are ready to publish right now, an additional five should we get there between today and tomorrow, and the rest is still far enough away to to sorry. I was reading the the screen now I lost that.

A

B

I I've shifted to the to my own copy, so um as far we will have time to to get there. um The webinar is schedule the event link. Is there we I've added it to the release article, which is reviewed and ready for publication and um and um and that's it so we're in a pretty good shape, as as we should be at this stage,.

A

A

um Any questions for comms.

A

Otherwise, we can move on to breathe Branch management, I. Think there's still somebody here in the meeting I, don't think so.

A

Okay, so for release, Branch management I think it kind of looks on track, haven't heard anything bad. We had a couple of I think there were a couple of issues, for example, also the one that Hussein mentioned um about the release pipeline, um but I think there's nothing major, nothing concerning. So that's that's good.

A

D

Yeah I think there's a small snack regarding the Krill fast forward job but I guess that would also be solved very soon. I have not checked on like what's the exact issue or if it is related as well. Okay, but I agree, it's probably green. Okay.

A

Did you heard anything so I think for rc1? We had like also some problems with uh container or image signing or artifact signing in general. This is like what you um also I mean: there's like this new, like part of creel, I, think cruel stage or some some new part which was broken. Also, did you heard anything.

D

About it yeah files now um but I guess things were resolved. There was one issue with the signer identity, um but I have to like catch up to okay. What is happening there yeah.

A

I haven't heard anything about it, so I guess it's okay,.

D

Yeah so considering, like our discussions, are revolving around having the patches in for other releases. I. Think, like things are going fine, but I would also have it have a look later.

A

Awesome. Thank you all right.

A

Are there any other questions?

A

Otherwise we can go on to navaroon.

D

Hello, hello again, um so the exactly exit survey for the leads is out. I shared with you all um the link to the phone and the survey for shadow is ready, I'm, just writing the email and would be sending right after this call um and again call out.

D

um If you have decided on who is going to succeed, you in your role, please do comment on the assemble release team issue so that we can have things running as fast as possible and that's all on my side.

A

All right awesome, thank you. That was the issue for the for the next release team.

A

So now we're going to post the link, also in slack, if you're interested and to my update so last last release team meeting, um I hope everybody had had a great time saying on the team and um I mean we will have the next team incoming probably starting some time, I mean already now, but the release cycle, the meetings, probably sometime in January, but they they will work on the timeline and everything and get this out also over slack if you're interested um or the Retro, we will have it next week.

A

It's already mentioned a couple of times in this in this call and right so I was also working on two other parts, um so for the first, the first one or the second one here in the list is about we've kind of basically doing some changes in the lead handbook um I mean also all the other teams, basically from the release. Team are also working basically on the handbook. So this is also the idea that every cycle we kind of reshape a little bit the handbook or just work on it, improve it in a way.

A

For example, now with the lead handbook, I was thinking. It would be a good idea, for example, to include an issue template because there are a lot of like steps which, where you just have to cross off action items, um so I synced on that with the incoming team and there's also another tracking issue, which is probably very interesting also for Mark.

A

The next incoming enhancements lead about um basically using the enhancements project board also for future Cycles, and this is basically just a tracking issue to get all the I don't know Parts together, so documenting documentation and and so on and so forth, and that's that's it that's it for my site. Are there any questions or comments?

A

I see six scalability as a green status. So that's great.

A

Awesome I see a lot of comments in the chat so.

B

It's great fun, that's just my comment.

A

And thank you great fun. Great fun is great awesome. That's that's good to hear um all right, then I will stop sharing my screen and stop the recording.