Kubernetes SIG Release, 28 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Kubernetes Release Team Meeting for 20221128 (1.26)

A

Here we go and let's.

B

A

Where did the oh I lost the agenda thing hello, Google.

A

There we go alrighty good morning welcome to another release team meeting. This is week 13 Monday meeting uh as usual. This meeting is a part of the kubernetes project, which means it falls underneath the kubernetes code of conduct, which boils down to be nice to each other um and if you're mean to each other on this meeting, it's being recorded, So everybody's, going to see it on YouTube and it's going to be super embarrassing.

A

So, let's don't onwards, uh I, don't think we have any open discussion topics here. Anybody have anything they want to bring up before we get into the team updates, nope, sweet, okay team updates: it is uh first we will go into enhancements with ryler which not filled out yet so they might not be here they might be doing theirs. Async anybody from enhancements here, okay, up next uh CI signal anybody from CI signal.

B

Hello: everyone, uh our current status, is green. Everything, looks good on Master blocking, as well as on informing one test on one two, six release informing uh which failed 27 tests in the last run. So we are waiting for the next one and after observing the next one, we will take an action and yeah. We have release cut tomorrow, for which we already opened outside.

A

Thank you so much any questions for CI signal.

C

Okay, um no questions but I mean it's it's on informing, so I mean we want to get this resolved, but I, don't I haven't seen like a new commit to. So if it's failing it looks like a weird flake, so you know if it fights again, we need to investigate I guess but yeah I should I wouldn't be too worried at this point. I guess: yeah.

D

A

Thank you uh up next bug, triage.

C

Yeah, we are green, um nothing, nothing really to share on our end, um to be totally fine.

A

Sick smooth sailing so far any questions for bug triage beautiful as anyone here from Docs.

A

D

I was just looking back to their last, it looks like they've left looks like they've missed the last couple of meetings here in the last, the last update was yellow, so, okay, potentially potentially, we should reach out okay.

A

Yep we will yep, we should reach out. Then okay.

C

um I was yeah, I was checking today um all the docs issues for this Milestone and most of them are followed up. We have a couple of um issues open. um Our pull. Requests are open to document things, but I think this is normal at this point.

C

All of them seem to be quite close, so yeah, I, guess yellow, is fine, so yeah, okay,.

A

Okay, thank you uh up next release notes.

E

Hi everyone, um our current status, is green. The website PR was already merged and I am addressing comments for the the rough pull request for RC Sirota and that's all for us.

A

Thank you so much any questions for release, notes, cool and comms.

F

Hello, so um we're on in status is yellow, essentially because we still have um I would say four to five. Opt-In opted in feature blogs and that we don't have any feedback. Yet um we have six that are already ready for review and uh of denying that are not four to five. We have direct indication from the owners that they have the content, but they will upload it today or tomorrow.

F

um The release article PR was opened, so the only it's and it's ready for review specifically in terms of the major themes. The only thing that's missing there is then the paragraph on the release team, which I'm I'm finishing up today and we'll share with Learners before submitting.

A

Sweet. Thank you. Any questions for comms.

A

Great uh Federico: do you need help from anybody on chasing down those uh five Vlogs that don't have any feedback? Are they people that we know.

F

I well, I, don't think so because well, the the Shadows have actually been actively doing that in GitHub and in Slack. So it's not my lack of um notification.

F

um That being said, I I will share the lists of the of the missing ones today in the Sig release Channel just so. If anyone has a more one-to-one contact with some of the owners that might help might help. Thank you, Kat yeah.

A

uh All right uh up next with our unusual guest uh release, Branch management with Jeremy.

A

uh Who may be muted, you're, muted,.

G

I pushed the button and then I had a cough and I didn't unpush. The button. Sorry um I just said all kinds of great things, and you didn't hear it. uh We were on track for cutting the rc1 tomorrow pending you.

D

G

Signal looking okay, um Xander's gonna, run that one so kudos to Xander for pushing the buttons and making sure that things go smoothly. um The last one I wanted to give a shout out to Cece who's.

G

Not here did a ton of work to get when we do the RC zero there's a ton of stuff that has to happen like branches, get cut and jobs get created and all kinds of stuff, and we found a bunch of things in the handbook that were out of date and CC took care of updating those things and did all almost all the PRS. For that, um and then also kudos to Marco.

G

I was also not here for uh kind of coming through and cleaning things up and helping us identify what we needed to update in the handbook. So next time things should be better.

A

Woohoo, that's what we want right. We want. We want things to be always better than last time. uh Any questions for Jeremy.

G

Nope yeah so we'll keep an eye on CI signal and hopefully tomorrow's Anders doing the magic.

A

Cool cool all right, uh Emeritus advisor nabaroon. Are you here, hey, hey.

H

So uh expect the shadow survey to be out this week, um I urge like every shadow, to go ahead and like answer what they feel about the release cycle.

H

um We don't yet have a form for the leads but I'm trying to like noodle on that and send out something to the leads as well for knowing like what they felt about the recycle and how we can make it better. uh This is just to get like more feedback about, or the cycle, and also give a space to say things which may not be like uh suitable for the Retro.

H

um That's the intent behind the service that we send out and to have some data and Matrix around the activity around the release. um The succession issue or the team assembling issue should also be up uh this week. um I've been talking to uh like almost all leads about what they feel about, who should succeed them in their role. uh I hope, like everyone, would have a decision by probably next week, no hurry um and the last topic about retro part.

H

Two we were Leo and I I was just talking about like can we have like third party facilitators and not uh someone amongst us to run the Retros I reached out to Jeremy and Jeremy graciously stepped up uh towards the Retro part, two thanks Jeremy and now we are trying to find a note taker who would be taking awesome notes for us and that's all um from my side.

H

Also one thing if there is any shadow on the call please do reach out to your lead. uh If you want to like lead that very role for the next cycle. Just let them know that you intend to lead so that they can also Factor that into the conversation.

H

A

Thank you thank you, but last but not least, our fearless release lead Leo.

C

Hello, hello on so yeah today, I was checking all the docs open website, PR's and issues that are still open. There are a few um but, as I already said, at the docs update, most of them are pretty um finished or very close to getting finalized. So that's great also for KK. There are a few ones open, but nothing, nothing too. Concerning um so that's. That's great um I found that we probably missed one enhancement, so the enhancement 1672, which is basically done also everything merged before code freeze, but we removed it from Milestone I.

C

Don't exactly know why, but the docs is already done it merged in. So we probably just have to add it to the Milestone and yeah I. Don't need to I, don't know um what happened. um Maybe we just forgot to follow up on this one.

F

But it was in the it was being tracked for a while and then.

C

F

Okay, I, don't know I believe some other PR, because maybe it it has a featured blog opted in. But we are not tracking the ones that were removed from Milestone.

C

So I will check.

F

C

No yeah so I just checked for docs, not for the blog post for dogs it or it already merged I. Think so. That's good, um so yeah I will follow up on this one and right. The last point: the release theme is finished, was quite quite some time. Developing or working with a friend of mine who designed the logo like I, can I can paste it in here. Wait a second!

C

So this let's wait. Oh it's too big!

C

You need to scroll down. Okay,.

A

There we go there.

C

A

C

We had a couple of different versions, and um so it was more or less actually also like a collaboration or team effort. So I reached out to the team leads into the lead, Shadows to get feedback, and we had two major different versions and um yeah.

C

So then the theme is electrifying and my my first idea was that, because we founded the tag, environmental sustainability, everything is right now about electricity and kubernetes does not at least not today does not have so many um like components focusing on sustainability, and this could be one of like a major theme, maybe in in the future, um but discussing with the team leads and Lead Shadows.

C

We also have like a couple of different ones, so not just like the sustainability aspect, but also we have, for example, now the dashboards, so we electrified, maybe some processes, and so on so they're, like multiple I, don't know like versions or ideas around this theme, which I quite kind of liked and yeah I hope you like it.

A

It's very cool, it's very my advice. I.

F

I need a t-shirt to go with my pink Blazer and white trousers, uh because this is this looks very very nice yeah.

A

I want this on a t-shirt. We still good.

C

Good luck getting the.

A

Release Swag by.

C

The way yeah you can expect the release swag, probably at kubecon. So that's probably the best time to hand out any swags.

E

B

C

It's your Amsterdam yeah.

A

All right uh anything from Sig scalability anybody here from scalability at all, no cool. um Is there anything else we would like to discuss on the recording.

A

A

Stop share: stop the recording.