Kubernetes SIG Release, 31 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Kubernetes Release Team Bi-Weekly Meeting for 20200331

A

B

Is being recorded.

A

Hi everyone uh welcome to the release meeting. uh We are now in the week 12 of the daily burn down meeting and this meeting is under um since they have code of conduct which could be summarized to just be nice to each other, and this is cc I'll, be hosting the meeting today and uh um just a brief updates. We passed the code phrase the day before yesterday and we received, I think four exception requests uh yet and I'll pass over to enhancement team, to give the further update enhancements.

C

I think we can't hear you.

A

Yeah, posing, um I don't think we can hear you.

D

Can you oh yeah, okay,.

A

Sorry, um yeah that.

D

Would mute uh so hosting from enhancement team? uh So, as you just mentioned, uh we just received uh four exception requests and yeah. They are currently gathering approvals and beside that we are green and that's all from our site.

A

That's awesome. Thank you. um I think we're still reviewing some of the exceptions and maybe reply. um I guess by today. Let's move to ci signal laura.

C

Hi, yes for ci signal our status right now is yellow.

C

We have one failing test on master blocking, though it is currently being fixed by the linked pr, and we still have a long-standing flicky test on master blocking on master informing. There are two new failing tests as of this morning.

C

Very recently, one is from six scalability one from sig cloud provider, so opened issues for those um overall, just um keeping an eye on flakes and failures and trying to open issues uh extra early and preventatively. So we can get ahead of things for next week's release. Candidate cut.

A

Nice, thank you for the update right now. It's not blocking the candidate card right, it's just a flicker and the one feeling yeah.

C

The one failing one on master blocking, that's being fixed right now, would be the only official risk.

A

Nice. Thank you. Thank you for the update. um Let's move to bug triage um radio yeah.

E

Hey cc morning, so our status for again for today's thread, because there are three blocking issues um which are currently being like worked on uh based on all the three. There has been a constant updates and other than that we like uh we have cleared the milestone in all of our pr's, so yeah. There is work going on looking forward for like this to this status, to come to the uh yellow and green cool for the three blocking issues. Is there already like a fix, be raised?

E

No, it's not fixed. uh uh uh The work is being going on and they're still open, yeah yeah.

A

Yeah I saw someone is watching that. Thank you. Thank you for watching.

A

Thank you. Thank you. Let's move to dogs nate you there.

F

Yes, I am um sorry I am not gonna lie, I'm doing about three things at once. uh I think that uh our status is currently yellow. uh We've had a little bit of movement. um I think we're at um six left with no pr and that's the sort of concerning um line item for me right now. um The the pull request placeholder deadline is today at the end of the day um and I'm not sure exactly what happens if a camp doesn't have a um placeholder pr.

F

um I am inclined to be not super worried if they don't, um but I also don't want it to go to the the I don't want. I don't want to wait for uh placeholder pr's until the the next deadline, which is, I believe, the um well, I want to say the 7th or the 5th, uh which is the ready for review. It's the fifth sorry doc's ready for review, so I think there might be an offline discussion to be had about um what to do about those types of things.

F

um I'm looking forward to seeing whether or not the um exceptions are um accepted.

F

If they do, please let the docs team know so that we can um uh put those back on our tracking uh tracking board and uh otherwise, um I think, we're in a fairly reasonable spot, we're about the same spot, we're we're in about the same spot as we were this time last release the there hasn't been a whole lot of movement since tuesday on the docker shim removal, uh the docker shim docks removal, so we've still got about half of the um we've still got about half the assigned issues without a pr in flight which, with three weeks left, I don't think, is necessarily terrible, but it's not um it's not where I'd like it to be either so the yellow status is, I think, appropriate here.

A

Cool cool thanks, um I noticed dog team has already started to contact the cab owners to um let them know the deadline for the placeholder. Pr, thanks for the effort- and there are only like uh 38 uh dogs needed here- is that accurate? I remember uh yesterday, we mentioned the cap track is for oh cool? No, it's perfect.

A

F

A

F

Before you move on, um are there any questions or concerns about dots from the rest of the leadership team.

A

I'll take it as a no thank you. Thank you. um Let's move to the release notes. Lucas. Are you here.

A

I saw you are editing, maybe you did yourself. Oh yeah cool, perfect. I can't hear you.

G

Hi um alpha 4 uh draft pr is up and currently going through the approval process, and um the discussion for major themes is oh, it was supposed to be a hyperlink I'll fix that, but um it's there.

G

So if anyone uh I'm also reaching out to the sig leads to get um to make sure they're giving their input, um if anything, they think if they think anything specifically needs to be called out or worded in a certain way and other than that um nope. That's about it.

A

Thank you so much, and so people started to um put, can uh major sim candidates on the discussion and plea, please feel free to keep doing that and let the seek chairs know thank you for the updates. uh Let's move to comms mickey.

B

Hey folks, um so we're we're green, I'm just trying to be optimistic. uh We do have one slight delay on our end, which is the removal blog which was originally scheduled for today uh is not going to be going out today, and this is a sort of a learning event for us.

B

um In retrospect, uh the removals blog shouldn't actually be shipped until well after everything's shaken out after the change freeze happens, and that's just because right now we're having to ship around content, that's changed due to people filing exceptions or things not making the cut off. So, even though that's not going out quite on time, I'm still feeling good about it.

B

Aside from that, we have finalized the list of our feature blogs. So we have, I believe, 11 pr's. You know again, certain things are going to change depending on what comes through as an exception, but I'm feeling pretty good about that and, aside from that, I've reached out to the cnc fpr folks about scheduling the release webinar, so uh james I'll probably be picking your brain for a time that.

A

Works for you, that's nice! Thank you. Thanks for the update, um looks everything went well and let's move to release branch management apparent. Are you there.

H

Hey um so we got beta0 today it was quite a roller coaster ride. um There were some uh issues which cropped up along the way, but eventually we managed to release today.

H

um So beta0 is up, and the next thing is we will cut rc0 next tuesday, so that is going to be more involved uh and we will also cut the branch during release during rc0.

H

Now I hope that the exceptions which will be accepted the prs, get uh merged soon, so that consumers who want to consume kubernetes uh release candidates. They can do so with the code that we will be shipping a statement.

A

Yeah thanks for mentioning that I do have a question regarding with like do. We need all the uh prs which uh being the which the exception being approved, got merged before the release candidate being card.

H

We don't necessarily need to have them merged.

H

uh The the only caveat is, if you don't get them merged, we would need to file a cherry pick to pick them to the release branch, although there is something under the words by sasha which will automatically fast forward the release branches, uh if that gets in by then we don't need to, but I'll keep an eye.

H

So usually what I do is, uh after the branch cut, I usually keep an eye on master and if any er gets into master, I check with the owners, if that needs to get cherry picked so with or without automation, and try to keep an eye on most of them and the changes which don't go into rc0 for sure they will be picked up in the release candidate, one that we have planned.

H

I guess which is again five days later. I think that he should, on friday or some something.

A

Thank you. Thank you for the um answer. Thank you. um So I think we should be in pretty good sport and uh um I don't think joseph is here today and if you are here please let me know, I think he already the updates yesterday um regarding this um started to formalize the team for the um coming release cycle. I guess, and let's move to the um release, lead james.

I

Hey yeah, uh I think my webcam is having oh there we go.

I

I was having difficulties um okay, so a couple of bits: um I'm gonna try to give decisions on the four uh exception requests today, I'll probably leave them about hour or so, and then kind of roll up roller feedback and and make a choice from there um one the hour we have an interesting meeting coming up, so this is absolutely not required for people, but um if people are interested in the enhancements spreadsheet and the future of enhancements tracking uh grace and others have been doing a lot of work on what that could look like going forwards, and that is owned by the enhancements subproject system architecture, and we have a meeting for that at the hour.

I

So if anyone is interested in in the spreadsheet come along and talk to us about the spreadsheet.

A

F

Thanks, I'm not sure that that sorry, I just clicked on that.

A

For sure, go ahead.

F

Sorry um does it not work, no it it it didn't, and now it does uh so I'm going to blame my own internet on that. Sorry for the interruption.

I

Yeah um other than that I have, I have no particularly update other than everyone's doing a great job.

A

Cool any further questions- and I think we don't have the six scalability of this today, but it's green this last time, so it should be good, and if we had our release card very smoothly today, so should be fine, and um before I stop recording any man has any other questions.

A

If no I'll just stop recording.