Home
Contribute Contact Us Browse all meetings
Home Contribute Contact Us Browse all meetings
Kubernetes / SIG Release / 27 Jul 2022
Kubernetes / SIG Release / 27 Jul 2022
Previous Meeting Next Meeting
⏯
Add meeting Rate page Subscribe
youtube image
►
From YouTube: Kubernetes Release Team Meeting (1.25) for 20220727

Description

Kubernetes Release Team Meeting (1.25) for 20220727

A

This meeting.

B

Is being recorded, hi everyone welcome to our weekly release meeting. We are now at the release. 1.25 week, 10 wednesday 27th july 2022 welcome everyone, and this meeting is under the cncf code of conduct, which could be summarized to just be nice and respectful to each other and I've pasted the agenda link to the chat. Please feel free to register your attendees and add any add any topics you want to discuss in the open discussion area.

B

Let's go ahead and look at our open discussion topics yeah, I just add one. Regarding with the go update um regarding with go 1.19 update. We have the announcement released yesterday to kubernetes dev channel regarding this update, their dev environment to 1.19 rc2, which has been merged in kiki side, and an announcement was released from goalside that the go 1.19 ga release is planned for next tuesday august 2nd exactly the same date as our code phrase and an extra reminder.

B

We have the code phrase next tuesday, so be aware of that and expect more work after code phrase and also at place time. Oh sure, colors. You have anything any questions.

C

I was submitted to my child.

B

Oh never mind so, um please also add any comments and suggestions about the release process to the 1.25 retrospective talk on the link added below in the open discussion area as well, and we will have our first retrospective meeting on one hour from now. Yeah, please feel free to join and anyone has any questions regarding of our open discussion topic.

B

If no, we will go ahead and move to the team updates enhancements jason. If you're here, hello, hello,.

D

I'm here so we've started following up with folks as we approach code freeze and with all the updates that are coming in. We are now uh we after I mean earlier after our earlier freeze. We were at green and now, with everybody's code uh at various stages, we've dropped to yellow because uh close to 38 uh of our caps are at risk. We continue to follow up with everybody. Most folks are very helpful and they uh touch back so hopefully, by the time of four trees, we should be clean.

D

That's all from my.

B

Side, thank you for the update. I guess people are all busy with the code phrase hopefully like make it. Thank you and any questions for your husbands.

B

If no, let's move to ci signal arch, hi or if anyone from ci signal is waiting to give us an update.

B

If nobody is from ci signal joining the meeting today, I'll just uh read the status, the current status is yellow and ash mentioned that like, even if, if nobody from ci signal join like they will keep the updates in the dark, so um they have several fittings.

B

um I guess all the issue I create created and the people are tracking it and.

A

People.

B

Are tracking with it.

E

Yeah I hear that as well. I think someone else is um mike might be on. I don't see anything. Maybe.

B

Yeah cool- I guess it's! Okay now so.

D

Thanks.

B

Thanks for confirming yeah, so um I just reviewed the ci signal channel people are like tracking the issue currently so it looks like looks like everything is under control and I'll sync with them again after the meeting, and if no questions for ci signal. Let's move to bug triage ashita, if you're here.

C

Our current status is green and, as the code is coming, so the team is trying to reach out to all the issues and vrs to know whether they are still relying on 1.25, milestone and yeah. That's all from the triad thanks.

B

Thank you so much um any questions for bug triage. If no, let's move to dogs carl, if you're here.

C

Yeah, I am here: hi hi everyone. uh Well, our current status is green and together with the shadows and the leader, we are following the pull requests and the documentations.

C

We have an open, approve request open to to sync with the main branch it's waiting for review and I think that's all.

B

Cool thanks for the update any questions for dogs team.

B

If no, let's go to release notes colors, if you're here.

C

Yes, I'm here uh we are green. uh We are processing the alpha, 3 uh release, notes uh draft. So that's the pr guy open and it's currently on review.

B

Cool, that's awesome. Thank you. Any questions for release, notes.

C

I'll be starting the process to do reminder pings to six for the major themes. Oh.

B

Yes, the major sims um that I believe is within two weeks, thanks for working on that and let's move to cons cat if you're here.

A

Hello good morning, I am in fact here uh so we are now tracking 18 feature blogs with uh the feature blog freeze in effect and we're all now chasing down individual blog owners for placeholder prs, because the deadline for those is, I think, the fourth um also the mid-cycle release blog pr is up. I linked it here in the agenda. It's worth noting that this one is a little weird, because we only have like one major removal and like one or two things that could maybe step towards a deprecation but aren't deprecations yet.

A

So this is more of a um major changes and removals blog as discussed, but it's trucking along so suggestions. Welcome. Thank.

C

You.

B

So much.

A

That's.

B

It yeah. Thank you. Thank you for the update for security policy is a big thing, so it's worth a like dressed like.

A

Yes, yes, it's it's worth addressing and um also we we are working with somebody else to write a pod security policy, slash pod security, admission, blog similar to the like historical context of docker, shim blog. We did last release that we're going to try to get out around the same time as the mid cycle.

B

Cool. Thank you any questions for comms team.

B

If no, let's move to our release branch management veronica, if you're here, yes,.

F

Hello, uh so, as cece said, um go 119 is going to a in a very critical time for us, and so following different discussions that we have had offline, uh the most sensitive thing to do would be to move our first beta well, our first and only data to just delaying it one day for the fourth of august. um There shouldn't be any any uh terrible things happening after that.

F

All those main stakeholders already proposed this and or approved this, but if any of you are affected by this or have any questions, uh let us know um to either jeremy joe or myself and other than that well code. Freeze is will also be executed next week by us. So let us know if you have any questions, I'm going to announce this and um on the channels, but, as I said, we have already discussed it.

F

So if any of you that uh are have any problem with this uh are basically the only ones keeping us away from this.

B

Thank you so much for the update yeah. Please feel free to raise any concerns. If you have thank you and any questions for release branch management, if no, let's move to ea ray.

E

Hey folks, uh so I just sent out the mid cycle shadow survey. I have a link in the agenda as well. Please fill it out in about 10 days or so so. It's friday august 5th that's end of next week um and also, if you have any other con any questions or concerns as well feel free to reach out to me privately.

E

On slack, um I will I, as the em, I'm the only one who's going to uh to see the results and the emails associated with these, uh with, with the um with the survey results uh when uh when and then I will anonymize it so um so, as you see on this on survey, we we call it studio anonymous because I'm I will have, I will see the emails and um and names associated first and then I will anonymize it for uh for uh for anyone who needs to take a look at it afterwards, um all right.

E

On the second point, the first 125 retro follows this meeting shortly at 10 a.m. Pacific I'll place a link to the retro agenda. um So if you have any action items from the 124 release, retro, please add your updates. I've also reached out to folks about this as well, um and also, if you have any things about what went well in 125 so far and what could have gone better. Maybe we could course correct uh before the end of the release and also what will we do differently in 126 and beyond?

E

So if you have any uh suggested topics, uh please add that to the retro agenda as well. Like I mentioned, this is the first retro. If you're new, to releasing will have uh an additional or maybe two additional retros after the release is, is out um so that'll be after release. uh The dates are on the release team on the 125 um timeline. uh Third topic is start to think about succession as well.

E

um So with the sort of winding down to the last four weeks of the 125 release, we need to start to build a team for 126., um so if doing shadows out there who are interested in taking on the role lead, uh please reach out to your role, lead uh for uh and then we'll. I will send out a little bit a little tidbit out to rolling I'm really it's about succession as well.

E

um If you're interested please reach out to the world, lazer myself as well um and yeah, so that's just so that's my my updates and just another reminder that the retro surely falls out after this call at 10am pacific.

B

Thank you for the updates. If anyone has any questions, please feel free to reach out to either real me, um but for specific topic like feel free to do a um private chat with ray as well yeah and, let's move to release lead update. um I have pasted again the following release: schedule all together with some major milestones here, just as a reminder.

B

They have code phrase the coming week, tuesday, and the beta card, as ronnie has just mentioned, was postponed by one day on uh still next week and the dogs placeholder pi, also um due next week, together with the deprecation and the removal blog post, which mentioned by cat earlier and also we have test phrase, one big following um after the code phrase and also the release branch card um yeah, um some other things worth to mention is like the major sims deadline is also within two weeks.

B

So I guess, release no sleep already aware of that and mentioned it earlier. um So um if um you have any questions or concerns or uncertainty uh around those kind of deadlines, please feel free to reach out and a final reminder again. Our retro part one scheduled like at uh 10, am pst. Today so please feel free to join and read your concerns or any feedbacks you have. Let's move to seek scalability update someone from six scalability provided update earlier today.

B

um Is anyone from seek scalability on the call want to um give us a live update if no I'll just go ahead and read it so the six scalability status is green and there is some issues with displaying linked below, but it's not a blogging. So I guess our status is green.

B

Thanks for the updates and let's just do a final check of the board, we didn't use it much. I believe so. It's updated 14 days ago yeah. We will try to figure out if we want to leverage the power of the wall project board more further in the future and before I end the recording anyone has any topics or any questions want to raise.

B

If no I'll go ahead and stop the recording.