Kubernetes SIG Release, 2 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Release Team BI-Weekly Meeting for 20220202

Description

Kubernetes SIG Release Team BI-Weekly Meeting for 20220202

A

Perfect hello, everyone and welcome to the today's release team meeting for the kubernetes release. 1.24.

A

My name is max. I will be the host for today and please remember. The meeting is under the cncf code of conduct, which actually boils down to be nice and awesome to each other and have just a great time together.

A

So for today we have nothing extraordinary on the on the agenda. So far, therefore, we can jump actually right into the updates from the different substreams and we get started with the enhancement team by grace.

B

Hello, everyone currently we're having 33 track 21 alpha 37 beta 16 stay one three deprecation and our enhancement freeze is at 6 00 pm pt. Tomorrow um we will be having an enhancement freeze party, uh which I left, the google link there for everyone, and I will send that again to the sick release channel um everything is looking good. Our status is green. I do want to point out one of our major change. The docker shim removal uh enhancement status is still at risk. um Maybe they'll file an exception.

B

Maybe they'll get it in uh by end of tomorrow. We'll see.

A

All right I see the docker shim is coming uh in with a tough wind. uh We have also later some updates on the dark side. I think.

C

What's the what was the issue that they're having because I thought all the code changes already landed.

B

um I think they were just missing, uh like updates on the latest monsters things like that I'll double check.

C

Okay, all right! Thank you all right. If.

A

There's anything needed, please raise the hand, so we can have a look on it perfect. Thank you very much. Grace uh cia signal with uh near adida.

D

So yeah, hello, everyone, our current status, is green uh moving to updates on master blocking. We have five flakes in which two of them are reported and yeah zero failing on master informing. We have some flakes, but no high risk right now and yeah again: zero failing on master, informing and yeah ci signal. Dashboard donation is in motion so yeah. That's it.

A

Cool awesome, thank you for the update.

D

Hi everyone, so the report from bhaktraj is in blocking issues. We have two one is the docker shim removal which was followed last week and they replied. They are currently looking at it because there are no updates from the upstream, but they are tracking it and the second one is the kubernetes publishing bot is broken. So this happened at the end of the release 1.23, but we are still, it should be, follow follow this. Should we continue to follow this what's happening and mark the milestone 1.24.

D

This is a question for the release team.

A

C

Yeah I mean we need a publishing part right.

A

A

E

A

There is also if the branch management has some hands on it. I don't know, I think you're in the call do you're aware of something.

C

Yeah I haven't followed the conversation, but I thought colors will give it a closer look tomorrow.

F

A

Okay, sure perfect, then we are looking into it and see how, following up.

D

Sure, okay, maybe I can follow up in the same uh issue, what's happening and then otherwise it looks green and uh yes, and from our team perspective, we are currently going through all our issues and tracking it and replying the equality status. Yeah.

A

D

A

Cool. Thank you all right. I think that's something which we should have a look on latest next week to to double check on it. um Nate with stocks.

F

uh Hello: everyone, um the doc status, is still green. uh Our integration branch into the website is healthy for one two, four, as the.

F

Hard to keep track as they sort of keep chaining up so docs sort of starts uh working earnest uh after after uh dox freeze um and um it seems seems almost every every um team has got a docker shim uh removal update uh for the docs.

F

We have on tuesday mornings a meeting with the docker shin docs removal project and right.

G

F

That project removing uh dr shin from the dock seems like it is um moving forward quite well. We had some questions about. How do we know when we're finished and I'm still not sure that we know how we know when we're finished yet, but that's something that we are working on uh and then there were some questions during our last um meeting about external docs to uh sort of downstream documentation sets and we've decided that those uh for our part are not uh release blocking. So that's where we are.

A

All right I mean, as expected, dr shim, is, uh is not leaving us for free. He doesn't want to leave the room.

A

Okay, um release notes by the.

H

Lucas, hey uh really weird issues, slash bug with krell, it didn't like vi of all things, uh but the alpha one pr is generated. The alpha two uh pr generation has begun: uh one shot uh parole, the shadow is volunteered to do it.

A

Do we have a back report on the on the issue.

H

No, I tried just recompiling and uh that didn't work either. uh So I just switched computers. There was a slack thread that was about to have linked.

C

In the notes, okay,.

A

Awesome, thank you.

A

Then. We have comms with nikki.

G

Everything's, looking green right now uh we're starting the process of identifying content for both the deprecation and removals blog posts, and also the release blog posts. Both will follow the enhancements, freeze and I've been joining nate bright and early on those uh tuesday at 7. 00 am pacific calls for sig docs on the docker shim removal.

G

What I've been trying to do more recently, there is look through all the backlog items that we have and identify, which ones might be uh appropriate for inclusion in that deprecation center of a blog post.

G

So if anyone has any additional ideas, feel free to, let me know, but that's not it on our end, you know it's still early days for coms, so I'm not doing too much right now.

A

Well, I think you can maybe find also some good inspiration on the previous communication and really posts which happen on the blog about the docker shim. So you do not need to reinvent everything from from scratch. Yeah.

G

I

F

And there's uh sorry just interact, there's also a couple of blog posts um that have been proposed by the doctorship removal. uh Folks, uh it's it's they're kind of buried in our in the um in the board, but I can I can send you the um the issue link specifically after this meeting.

I

And sort of surface those for you, okay, that sounds good. I may have caught a couple of them already, but any help is appreciated. Oh good.

A

Maybe you can add them directly here to the document so that everyone can have a look onto it.

A

I will do that next. Thank you guys. um Moving onward release branch management with nabaroon.

E

Hey everyone, um so the first update is yesterday. We released the first in-cycle alpha release for kubernetes 1.244, which was uh 1.24.0 alpha 2. um everything went smooth.

E

We did not face any issues in cutting the release um and it happened quite fast as well. I believe, because this is alpha, there were some steps which are not needed, um but yes, if anyone consumes our alpha releases, please do use them and find more bugs.

E

um Next up, uh jim angel will be the branch management shadow for this release. Again, I'm not sure if jim is there in this call, but I let him introduce himself like in the future- calls um I've created prs to include him in the mailing lists and also in the listing roster, so he should get the invite automatically from the next time onwards.

E

um Next up, we have the alpha 3 release on february 15th and alpha 4 on march 22nd 22nd. If I remember currently, um and then we have like beta0 postcode phrase, so uh more on those things later on, but for now for the next two weeks we don't have much updates on update and that's all right.

A

Awesome very excited about having jen with us in the team. Great news um I think the emerald's advisor can skip joseph has not made it so far into the call and can move on directly to james.

C

Hello, um just on joseph's thing: yes, he didn't make a difference. um I think I believe the first of his two sessions is directly following. This call is my understanding and then there's another one kind of later on, so shadows do go along to back. They are. They are very useful. um My update um still trying to make every sick it's difficult. Some of them are a bit elusive.

C

um I had this naive impression that every sig would have their segment in the community calendar and that does not appear to be the case, um so I'm having to go through and and find all of them, which is interesting as an experience, but I will going on this is less valuable now, because I was going to be going in and reminding people about like code reasons stuff, but it's a bit late for that now so, but I'll probably still try and do it. um I am also looking for input.

C

I want to introduce more meetings, there's a slack thread about this. If people go look at that, they're really useful um in this schedule. We don't add another meeting until week, 11 in march. I want to say, like another weekly meeting, um I'm wondering in previous cycles: we've had an apac eu one added on fridays earlier, um but it was never kind of like a formal decision on the schedule. I think it's just something that got done.

C

um I'd be interested in people's thoughts on on when we should add those should be adding them right now, they're, just opinions in general um and I'm gonna give the mid-cycle release doodle another week or two for people to respond to it before I. I could have closed that and pinned down a time and then I'll open another one for times for the end of cycle. The two ender cycle- ones, um that's it from me.

C

Does anyone has any questions for me.

A

Thank you very much. uh I just shortly looked up the um shadow orientation meetings and there's actually one schedule for today. um I guess right after this meeting and then a second one for tomorrow.

A

I just can tell you the european time, which is around 5 00 a.m.

A

I'm not sure if this is right, because it would be a little bit early for us, but every shadow should have an email, at least in your.

A

Favorite email service and an invite- please check it it's from joseph sandoval. Maybe it could be also end up in spain. Just double check it and have a look. If you got it, if not raise a hand or write us a message or better write, joseph a message and as a shadow so that you uh not missed in the car.

A

Perfect, um do we have anyone from six scalability in a call I haven't seen someone just looks like alrighty. So with that we are once through today's agenda. Do we have any updates on top here? Also, it looks like perfect. So then we can have a short look on our release.

A

Team projects board uh nothing big, it's more about to raise the awareness that they're from time to time are popping up some of the potential topics and issues you can have a look at um where your input is very valuable, and sometimes we have also some tickets running a bit longer and always very good place to contribute, in addition to improve the whole process and procedure around the sick release, team.

A

And other than that, I think we don't have anything currently burning here on the board any further input from the team things you would like to ask mention highlight.

A

Also, nothing in the chat perfect.

A

All right, then I'm going to stop the recording and if you have any first of all, I wish you very great day and also soon a great weekend.