Kubernetes SIG Release, 29 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Bi-Weekly Team Meeting for 20200329

Description

Kubernetes Release Bi-Weekly Team Meeting for 20200329

A

Hello, everyone and welcome to this beautiful tuesday, the 29th of march 2022 to the weekly burned on meeting this is week 12 of the kubernetes release 124. My name is max. I will be the host for today and just in some terms of housekeeping, please be aware that we are under the kubernetes code of conduct, which boils down to be nice and awesome and great to each other and ensure the respect you all deserve with that.

A

We can jump right into the updates and I would like to hand over to priyanka from enhancements.

B

Hey everyone, so our current status is yellow, uh we are tracking 35 and there are 23 uh enhancements still at press uh and we are like 49 for the code. Freeze.

B

The last final friendly reminder of the quad phrase. So uh let's see what's the final number but yeah, that's the page. Thank you.

A

Okay sounds like we maybe should also maybe leave a friendly nice message jameson when we have 23 on risk. Yeah.

C

What do you mean? Go you mean, go through and uh poke each of them. I mean.

A

Yes, excellent.

C

A

14 hours left to start on risk. uh It's uh I like to be optimistic, but um well.

C

Yeah, the thing is that we want to poke, because I presume that enhancements is poking on the issues already yeah. Do we want to go poke? Some some sticks just give them a gentle. I would.

A

Say like uh we can give them them some more hours until the the clock has rushed a little bit and then we can poke the seeks again like hey, please don't forget. Code freeze is closed and currently we have a need to have a eye on you. um I think it would be helpful.

C

Yeah, I think it could be helpful. Let's I'll tell it offline I'll I'll mention that in the release enhancement channel and we can- we can coordinate what we're doing there, because I don't want to travel live what the enhancement team is already doing.

A

Okay, that's good perfect! Thank you. uh Any other question comments to priyanka.

A

Nope then moving onwards to see guys, nikon and laura.

D

Hello, um we have no failing test right now on master blocking or master informing, and none of the flaky tests. Besides this one on master blocking already listed, are exhibiting any pattern of behavior, so the ci signal current status is green.

D

um The flaky tests mentioned gci gc ingress is not considered a release blocker for wednesday's beta release cut by sig network, as mentioned yesterday too. So we're okay with that, um and otherwise we are observing the four release. Blocker tagged bugs, but thank you to james for confirming that they are not a blocker for the beta candidate this week. So from ci signal we are good.

D

A

Awesome. Thank you very much questions to ci signal.

E

Hi, so our current status is red, so we have had some progress, so one of the pr's one one of the release, blocker issue, one pr was merged, but the issue is not closed yet so we'll be thinking them about whether all the work is needed on that, or is that enough to close the issue? That is a pending discussion and one more thing we wanted to know from ci signal whether this go 1.18 pls unit test is going to be a big issue further down the line.

E

So there has been some discussion going on in it and it seems it's some golang related thing.

D

Yes, I think the position is that it needs to be resolved before the 124 first release candidate, along with the other, about three issues related to go 118..

D

So, while that's not an issue for this wednesday, we do need to be pushing it, for I think the next week is our next candidate right.

C

The the fifth is rc zero, I believe which means tuesday. Yes,.

D

Yeah, so it's not that we have so much time. I guess yeah.

C

We have one week to hold.

D

And if I recall from the slack uh message from jordan too, this one is the and I don't think anything has changed, that this is the highest risk, one because it hasn't no one's working on it. Yet.

A

It also looks like that this current issue is something which appears on your mac os, which could be a reason that it's passed on. The linux builds.

A

A

Are related to the go 118 update right.

E

uh Yeah out of them two are there, two are impacting the tests. Another two have fias.

A

E

A

All right, thank you very much. Any further questions to bactriage.

A

Cool moving on to rehab stocks.

F

So hello, everyone, uh the current status of dark steam, is yellow. um We are almost like two days around after uh there is doc's placeholder pr deadline and we are still uh remaining with 15 placeholders, so, probably by today we will try to reach out to six for the heads up to get the placeholder behaves.

F

So, yes, nothing major updates. Since yesterday's meeting. Thank you.

A

All right, thank you.

A

Do we have anyone joined from the release, notes or comms.

A

Sounds like this, um then maybe one short heads up from our side. You should have currently two meeting invites for friday. um James will tidy up this later. The time that.

C

We will meet.

A

C

I've issued the uh I've issued the update, so it should be updating if people's car, because I just made a mistake, a long time zone when I created it. But yes, every as I put in in slack all meetings are either 11 am utc or 4 pm utc. Those are the only two times for these main real estate meetings.

A

All right, perfect, good anything else from your side.

C

C

um No, I I don't have anything else. uh We have a lot going on this week. Of course um we have code freeze and then we have a beta curt and we have a docs deadline and we have a dedications blog coming out. So things are starting to get exciting.

A

Fun we're coming closer to the movies.

A

All right, then, thank you very much to you all. I wish you a very pleasant week and you'll see us tomorrow. Thank you, bye-bye bye.