Kubernetes SIG Release, 23 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 202211223

Description

Kubernetes Release Team Meeting for 202211223

A

Hello, everyone today is uh the start of I, guess not the start, but this is our week 12 um kubernetes 1.26, release meeting this is an official kubernetes meeting and as such uh falls under the kubernetes code of conduct, which is um can be paraphrased. uh Please be nice to each other. uh So uh just a note, we are recording um so this will.

A

uh This will show up on uh YouTube at some point uh so feel free to um if you're not interested in being on video keeping keeping off um so uh to start, let's um I, don't think we've got um we'll start with the open discussion. Is there uh any new members or attendees uh I'd? Be surprised at this point? If anybody came in and was new but I'd like to open up some opportunities in case just in case foreign.

A

Looks like everybody's fairly familiar here, um so, let's jump into the enhancements um rohina. Are you.

B

Yes, um hello, everyone um we are still on free Status. um Things are looking good. um There are there's, not many updates since last week um it's pretty much the same number of um attract issues that we have yep. That's it.

A

All right are there any um questions for the enhancements team.

A

Okay, let's move on to CI signal.

C

Hello, everyone so currently on Master blogging. um We don't see any failing jobs and there are eight flips.

A

Well, I think we might have lost Mayha.

C

uh They are trying to fix it as soon as possible and there are eight Legion Master informing. Also we are tracking the test grids of 1.26 blocking and informing, and currently we don't see any failing jobs, but yes regarding the flaky ones, uh we are tracking that. So, yes, that's all from CI signal. Thank you.

A

All right anybody, anyone have any questions or comments for, uh and the CI team.

D

Maybe one question: so: um did you detect any any flakes or is? Is so we record I mean test grid always shows like there are like eight Flakes and so on, but most of them are not recorded flakes, so we cannot detect the pattern if we like detected um Flex in the past. This cycle I think only failings right.

D

I mean otherwise it's not so important. Just curiosity, I guess.

C

E

Actually in the morning, I have to check that at that time, I haven't detected any patterns so yeah, that's okay, awesome.

D

F

um I have a question so on the release. 1.26 informing board I see only three jobs, whereas on 1.25 informing there are six. So we have some Q radium upgrade related tests in the previous release cycle so have we have we confirmed that those are not needed?

F

um So if you see here, we we have like six tests and cubadium tests are missing from 1.26, informing and.

D

There was like this one one issue open to, um because the 1.26 dashboards were very light on jobs in general, yeah.

F

D

Seems like these are fixed I, don't know why there are, if you left- maybe it's it's probably worth to follow up on that yeah. That's that's! A good catch.

F

Yeah I did I think it's a nice opportunity for the ca signal team to like get bootstrapped on even like okay, what jobs are needed per City Cycle and that's a really great learning opportunity if people are up to it.

E

Yeah yeah sure I'll follow up on this one also.

F

Do compare with the master, informing ones um and see the pattern of like previous release, informing ones.

E

Okay, yeah sure thank you.

A

Anything else for the um CID.

A

Okay, moving on to bug triage Jose.

G

On is out today, um but I can give a quick update on that we're we're green here. So uh nothing really blocking at this point um pretty much in sailing for us.

A

Excellent thanks.

G

A

uh Any questions for the bug to be asked you.

A

No okay, moving on to docs um Carolina. Are you uh you around or is there anybody from the uh docs team who would like to take this foreign.

A

A list of participants.

B

Do we have anybody.

A

From the docs team on.

A

That doesn't look like it: okay, we'll Circle back see if anybody comes back uh comes online, a little bit later, um release notes for dolphin.

H

Very Nate, hey team, hey we're currently status is yellow. Hey no issue has been added to the no issues yet and I will post a message in the release: management management, Channel, hoping to have some luck and maybe this release. We don't have any no issues that maybe we are not reaching the right people for that. Also I am going to work on the release, notes for RC 2crc.0 and have those release, notes, ready.

A

Thank you, Rodolfo is there. Anybody has any questions or comments for uh the release, notes. Folks,.

D

um Just one question so I said: do we require any inform or input for known issues? Os is just like a general catch issues, issue yeah.

H

Just a general catch issue.

D

Okay, but so okay, so it's kind of kind of green status, but right or not.

H

Yeah he's more a green status, but I am worried that a we don't have any known issue for the release: okay, okay,.

A

Awesome sounds like it's kind of more of a chartreuse I'm, not sure that we've got that shade on this dock. uh Moving on to uh comms harshita.

E

Hey everyone, uh our current status is green and we have four feature blocks that are ready for rupees and the deadline for the review is on November 29th and the more information on the release theme. uh We are actively working on release article and uh further discussions are going on in the hack.

A

E

File yeah. Thank you.

A

Thank you so much is there any questions or comments for comments.

F

um Considering there are 11 open ones right now and we just have six days to the deadline. Should this be more yellowish like yellow to reddish, comparatively I'm, not sure like how active the reviewers are so just putting that up as an option.

I

Yeah I I, you know it's Federico here um I would say: that's uh in the next burn down that we have likely, it would be more yellow. The reason why it isn't is because we do have a lot of comments they are saying. I can only push this in near the deadline, so people are aware of it. They know that the deadline is there and just like the future Vlog opt-in, we got 90 percent of the actions in the final two days. So it's it's.

I

um That's why it's it's win, but but you're right it could be yellow.

F

Awesome I just wanted to point out because um the earlier we find like the earlier, we Panic it's better for us, because we can course correct with a large timeline in hand. We have.

H

F

Can rally people into review if we right now make it like, yellow or red, because we should be on priority right. The.

I

Problem with deadlines, that is, that most people see it as the the day of the liver. It's.

B

F

That's an eternal issue: yeah.

A

Not just on this project either.

A

Thank you for that. um I. Don't think. Jeremy is on this call. Is there anybody who can speak to the release? Branch management.

G

I can speak to that a little bit, um no updates at this point. We are cutting the um RC one um I believe next Tuesday. If my memory serves me correctly,.

D

29Th I think yeah.

G

Let me I have it on my calendar yep next Tuesday, the 29th. That's our C1.

A

Awesome. Thank you so much Xander I appreciate that uh any comments or questions for Xander on the release branch.

A

Nope doesn't seem like okay moving on to our Emeritus advisor in avarin.

F

Hello, hello, so my updates are mostly related to 1.27 and not one to two six, so we are just two two and a half weeks away from release.

F

um So I wanted to bring everyone's attention to the fact that you need to think about people that you want to succeed yourself in the role and discuss with me um about your options and also discuss with them if they have bandwidth available in the next months. uh Basically, the first quarter at a little more of 2023.

F

um That's one thing: I'm, also working to find the next ea uh for the release 1.27. So that should also be in by the by release date. I guess, because I'm coordinating with people to understand like who would have bandwidth to come back and spend spend time with the listing, and meanwhile I've been thinking like how can I accelerate some of the decision making processes by you folks.

F

So we usually send out the release survey on the week of release uh practically the last week, I'm thinking if we can uh send out the survey a little earlier, so people can have time to think about how do they respond to this, and then maybe we can incorporate the feedback in current decision making somehow, but that's an idea. So if you see it for next week, probably uh that would happen earlier.

F

um That's all from my side. Any questions, comments, concerns.

A

I think releasing the survey early is not a bad idea. I think that can be helpful.

D

Yeah, why why do we have this survey so late in the release? Is there any benefit, because I I think it makes sense to have it earlier just to get feedback in and so on? So maybe we.

H

I

D

The schedule for next or the Habit in general.

F

Yes, so this is mostly like end of release cycle survey to understand, like how did the release Shadows like feel about the day cycle, what to learn uh the goals that they came with when they applied to the releasing Shadow program? Where the satisfied, um then there are two forms, so one goes to the shadows and one goes to the leads uh for the leads it's more to understand. Like hey. Did you have fun mentoring? People uh did you? Are you satisfied in mentoring, people? Have you gotten your success as well?

F

How can we do better next time? So as a like people, program, kind of thing,.

F

And I also hope, like people to ping me proactively whenever they face issues and not wait for the service to raise red flags, um that's what the role is for, essentially to offload all the people related problems to the Emeritus advisor rather than those coming to the release, lead.

A

Thank you for that now. Bro um I just want to I I thought. I saw some folks come online, so I just want to Circle back.

H

A

Anybody from the docs team on the line.

A

I

It doesn't look like it no, but but Carol Carol did mention, did Warren in the in slack that she was having internet problems and that she would do to the updates async yeah.

A

No problem um and thank you for that piece of information: um okay, um Leo.

D

um To my updates, hello, everyone and welcome, um not welcome I'm, not saying this video. Thank you for for joining this meeting. It's it's I feel like it releases. Almost over I mean I can I can see the deadline, the release uh deadline very close, or maybe that's because I'm I'm working on the release theme so so uh also the last things on the release are are taking on shape. So um yeah, we're quite close, I would say.

D

um I was now working on the release theme, which is more or less done working on out some small details, um but the theme name will be electrifying or just Electrify. I, don't know about the I ing, maybe maybe we will drop it but more details on the release theme, probably on Friday I, think in the meeting, um also on the logo and yeah I scheduled two retro sessions.

D

um So we already had one release: team, retro, mid-cycle, I, think the week or two weeks after kubecon, and we will have another one or two once um after the release. One week after the deadline, or after the release cut and depending on how much like traffic we have on the first retro, we need also another one or or not so I.

D

We usually we just schedule two Retros at the end, just to be sure, we have enough time to talk about everything, but in the past sometimes we just had one meeting so the one on the 13th of December.

D

um So keep that in mind so yeah. If you have any ideas, how to improve the program um I mean you can just add your thoughts into the Retro doctor would be very great and yeah. That's it.

A

Thank you, Leo. Any any questions from anyone for um Leo um request.

F

A comment I added the times to the release calendar as well. So please have a look at the pr once you are left in.

D

I think I approved it already. Thank you. Yeah I missed to update that.

F

A

Okay, and uh is there anybody from the sixth scalability team on the line.

A

Doesn't look like it, but it also looks green, so I'm not going to be too concerned um so I think. That's uh probably all we need to do at this point so I'm going to open it up to um uh what I'll do is I'll ask um uh Leo to stop recording I'll, thank all of the future viewers for taking the time to stop by on YouTube here um so Leo. If you could.