Kubernetes SIG Release, 25 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Kubernetes Release Team Bi-Weekly Meeting for 20200325

A

Hello, everyone for the week 11 uh stick release team meeting today is friday, the 25th of march 2022- and this is our weekly bruno meeting um with the emea and apec friendly time zone. I'm the host max curve here currently sick release lead shadow long title.

A

Nevertheless, most importantly, for today um this meeting happens under the kubernetes code of conduct, which essentially boils down to be nice and awesome and friendly to each other. All right with that. Let us jump directly into the updates enhancements with hossein.

B

um Hello, everyone uh so looking at our beautiful excel file, which I literally hate, um so we have already yeah yellow status because of uh having uh 40 enhancements. You know at risk. uh We are updating continuously, all those enhancements and like as soon as we get an update from the people which are updating those enhancements.

B

We are updating the excel sheet immediately, so uh we moved from 17 track to 19 today so and that's it and next week we're gonna going forward uh to go tricks yeah! That's it.

A

Perfect, do you see anything which is going to block you or where we need to intervene a little bit to get some further updates.

B

I'm in touch with grace. uh If something comes up, I think she will write to you guys directly yeah.

A

Okay, nice. Thank you. Any questions to jose.

A

Perfect cia signal hi, hello, everyone, so the elbow local and status is yellow. We seem to have a lot of issues due to the go up clip, but most of them seem to be resolved by now.

A

So we have one failing issue and three flaky issues in the master blocking and wrong failing and the four flag key in mastering forming. So I think that's all. Do you have anything to add a leo.

C

A

Okay, yeah: that's it see.

C

A

Test and the master blocking the same one from last week, oh.

C

This is a different one. Okay, this is but it like. From my perspective, this is like a very small issue. um It just relates to that. Go-Get is no longer supported and we need to switch to go install, so this should be resolved pretty soon. If somebody picks it up.

A

Okay, nice perfect any questions towards sierra signal.

A

Okay, moving right on to bactriage with tiptoe.

D

uh Hi, so our status is red. So, from the last meeting we had two more issues: release proper issues and an update about the issue is that in the question the discussion, it seems that everyone has given their consent for removing the release broker label, except there are two discussions regarding project board and two pr's to the kubernetes website and one more comment regarding the dm check.

D

The rest of the issue seems to be arising from language and quantitative migration.

D

So uh the first issue that the threats try check, which was their present last week, also there's a pr which has been which skips the test, but it seems that the issue is more than just the testing point and the two more issues have been uh addressed in the discussion phase.

A

Okay, is there anything where we can help.

D

uh There's the discussion which the document mobile issue, the first link, which has been added so that one uh someone has pointed out that some pr's need to be checked, which is really relevant. So discussion around that can be done, and second one which was added just one hour ago, was uh another concern regarding the cubanian check the rest of the issues.

D

uh It's telling.

D

Discussion going on.

A

I think we need to monitor, monitor this very closely also with the upcoming code freeze and then all the other procedures processes starting around it. um This could be a quick blogger in the end.

A

All right, thank you.

A

uh Let's move forward to doc's mia.

E

Hello, everyone, uh so our current status is yellow uh nothing major changes since last. Meeting uh integration branch is healthy and some cape is dropped uh to like remove from milestone.

E

Now we are left with uh placeholder prs of 21kbps, so yes, going uh hoping to get more ahead.

E

A

All right can we support you somehow reaching out to the um six or the contributors to get some of the maybe necessary, prs moved onwards.

E

Yes, uh we can uh reach out to six to get more.

A

Okay, so I think then um best we will later check on the document what's missing currently and give them a friendly ping to work on the pr's for the dogs.

A

Any questions towards me now.

A

Okay, um I think we don't have anyone from release. Notes in the call right. Am I wrong.

A

F

A

um Comes this part to be.

G

uh Hello, am I audible? Is it good? Yes? Finally, okay, uh so we have, we don't have any major change since the wednesday call. uh We have been following up with every sig uh to collect the enhancements that people would like to feature on the features blog. We have extended the deadline until 30th march.

G

uh The removals blog post is up for review, so mickey has opened up a pr uh I've linked it into the docs, so people can check it out um and we are coordinating with the uh uh about docker shim created press opportunity, so nothing major here, yeah, okay, okay, thank you.

A

Thank you very much. Questions towards comes.

A

Alrighty um from the release branch management, there are no big updates, just keep in mind. We have next week on wednesday, the 24 beta 0 release and then from our side. Just a few short heads up on 27th of march. Europe will enter the daylight serving time zone.

A

So keep your calendars and have a look on your calendars of the meetings still fit, not that you come a little too late to the meetings, um also very important. On the 28th of march.

A

We will start the daily burn down meeting and, as already mentioned on the 29th, depending on from which time zone you take a look into it or the 30th of march. We will begin the code freeze, all right uh anything else to add, maybe from james.

F

Nothing in, in particular, from kind of a release lead standpoint. um I think I'm going to send another another email about code, freeze, probably over the weekend, just to remind people that it is coming very soon.

F

um One small thing: someone asked in a sig release channel about adding something which apparently has gotten code pr's, merge and everything to the release because it didn't it got missed for enhancements. um I've just pointed them towards the exceptions process, but if it's all merged, then it seems a little risk to me. But we'll have to take a look. When the exception comes in that's probably coming soon. I would expect um yeah nothing else. For me.

A

All right anything from the team, something we need to discuss highlight.

A

Not three two one sold, then we will close the meeting for today, and I wish you all ready to have a very nice and awesome weekend. I hope you can enjoy the weather and then we get and enter slowly from the next speak, to serious phase of the release and to bring the 124 out to the people.

A

Thank you very much have a great day.