Kubernetes SIG Release, 28 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20220928

Description

Kubernetes Release Team Meeting for 20220928

A

Hello: everyone welcome to week four of the 1.26 kubernetes release process.

A

um I am Grace I'll, be your host today, um just a reminder that we are under the cmcf code of conduct, which boils down to being kind and respectful to each other. All right, kicking off with open discussion.

A

um Is there anyone new here that haven't introduced themselves? Please speak up.

A

All right, uh if not, uh we can jump right into enhancement, mark.

B

Hi, uh so for this uh I'd say, enhancement status is still green, we're still working on collecting cups and giving the authors time to meet all their criteria. um There's a link to the tracking sheet here, as always, um One update, is we've started to add some insights or graphs around there. um You can access those via uh appending insights to the link or there's a little like graph icon on the get on the on the board.

B

You can see um it's not as robust as the sheets, but it is um better than not having these there.

B

um So that's good, we'll probably continue to refine those um we're still working on the automation for the sync job. Riley's been taking a look at that and suspects that the ariler um and suspects that the pad token might not have all the correct permissions.

B

um Other updates are enhancement. Freeze is next Thursday and ryler will be sending a mail today to kadev to remind everybody about that. um We've had so far. We have 45 enhancements that are been collected, 44 that were tracking or we're working on now, that's eight since last week and there's a breakdown of the stages.

A

All right, thank you. Mark um moving on to CI signal, Moana.

C

Hello, thank you uh so updates from CI signal team. We are seeing a few flaky tests in both the branches Master blocking and master. Informing we've created two issues for one play: key test in the master, blocking branch and another one to the master, informing branch and the issues are still waiting to be triaged um yeah. So we are monitoring all the other tests and in case we need to raise an issue. We will do that. That's all the update from CI signal. Thank you very much.

A

Thank you and then bactria Kalin.

D

Hey yeah, so uh things are still uh slow for us, but starting to pick up a little bit, uh we've got uh you can see. There are a bunch of issues, starting and uh now that all of the members have access to the project board. We've started picking up um issues, NPR's tracking them and following them up that's what we got going on. Also nice to see everyone.

A

uh Quick question I remember during the orientation there was no problem uh with tagging books in KK. Have that been resolved.

D

I think so, with the project access that I'm, not 100 sure so I'll follow up for uh next week or next meeting.

A

Right because I think access to uh K enhancement or Sig release doesn't Grant access to KK uh yeah all right. um Next, we have docs with Mickey.

E

Hey folks, nice to see some familiar names and faces on here, um so docs is green right now and we have divided all of the gaps between us on the team. So we're good to go.

A

All right, thank you and then release notes with Rodolfo.

F

Okay, team and the current status of Rhodes is green. We just merged the draft board request for Alpha One and working for website per requests. We need an approval for security. Slits I chose a tag team in the put request. Also later today we are going to create a GitHub discussion for major teams and I will post this discussion at a series. Release selection.

A

Awesome awesome: um next up we have comms with Gaba product.

G

Hey hi everyone, uh so with comms uh this time we had what we had fun so see you in the announcement board as well, so that book is done and uh basically the Nico sent messages to all six doctors offered for announcement for future blogs. So it is uh very early, but we started out in this web and the discussion is going on on. You know when to start identifying major release them so whether it should be during the advancement fees or just after the enhancement page. But to start with these different discussions.

G

As since the last two cycles, we have seen uh mid-cycle deprecation blog, so deciding on release, themes and uh major releases would help us with that deprecation block to both foreign.

A

Thank you for that. um Next Up release, Branch management well, Jeremy.

H

Hey, um we are green right now, the alpha one, one: okay, we're currently on track through the alpha two, with the current schedule for October 11th, um there's a subject of additional beta that I think Leo added to the his update. uh We can discuss that there it's going to be difficult to do another beta, but we can do more Alphas or accelerate those. If you need to. um We also just did a k, promo uh promo tools released yesterday, so we're going to try that out for the alpha two.

H

uh So there may be some hiccups there we haven't. uh We haven't tested that new version. Yet for that, but hopefully it'll be all good.

A

And when you say this gospel, though, where is that Jeremy.

H

Oh uh is the first item under Leo's update? Do we need another beta cut? Okay,.

A

Okay, let's see all right and then EA with navaroon, oh I, think number one can't make it today right. um But yes, there are two Shadows orientations. uh The invites are out um and then Leo released, lead updates.

I

Hello, everyone good to see so many folks joining this meeting. 28. That's that's great. It's awesome um right, so I have quite a few updates, but I think we can go through them fast. So first, the beta cut question so I remember something about salsa level. This is um like we have to have like um there's like some requirements for us to meet um supply chain security guidelines, but it turns out a beta card is not needed for this.

I

um So, as Jeremy already said, there was also the question: if, uh like a better cut another one would be any like helpful or something like this, um but as Jeremy already said so right now, the Sketchbook is a little bit difficult.

I

um Beta cards are cut after code freeze and we have basically uh the beta zero cut after couple trees, and then we have the week after the first release candidate cut, so there's actually not much time to play around with um so probably for this cycle.

I

um There's there's no room basically to cut another release, but I will reach out to some of the folks in the community who usually consume these beta cuts to see. If, if the release is is good, um if like this would actually help them, so maybe this is something in the future, um then to the next point right. So there's actually one changed to Cube CTL, where we have to which changes some things with um the cloud providers. So we need to make sure that the documentation and the communication comes about this getting sent out.

I

One of the docs sick release. Docs members reached out to us that this is like one of one concern from them, so we should make sure that, like we align the talks, that's basically the cloud providers are adding uh proper documentation. So everybody in the community is aware- and we also add this to our comms duplication and remove its block, um but I think uh we already aware kind of and have this done on our side. So that's nice and then the last point um regarding release, notes and cons about major themes of the release.

I

um So I checked with, like the handbook, the lead handbooks test. We should start major themes tracking in the fourth week so this week and the recent notes handbook said something different.

I

um So we sorted out in the stacks thread that I linked below when would be the best time to start I'm collecting these major themes, and um in this stack thread we discussed it would be probably best to start like with enhancement freeze.

I

So then we reach out to six and and ask them about major themes of the cycle and then with code freeze. We basically also freeze um this so I think that's great.

I

um Overall, everything is looking good um if there's like any access problems, I don't think so. But if there are any problems like this, please reach out and um otherwise I think we are looking great.

A

Through it, there is no update from six scalability. um Let's look at the board quickly.

A

Yeah I don't think there has been any new updates all right. um Any last call out before I stop the recording.

A

Okay, to do stop recording.