Kubernetes SIG Release, 15 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: (1.25) Kubernetes Release Team Meeting for 20220615

Description

(1.25) Kubernetes Release Team Meeting for 20220615

A

So this is the kubernetes 1.25 release team meeting wednesday june 15 2022.. uh Please be aware that this meeting is governed under the kubernetes code of convict, which can be summarized as please be excellent to one another.

A

All right. We are gonna kick off here with uh enhancements.

A

Actually, let's, let's visit the open discussion items first right like let's actually follow the meeting structure, xander um all right.

A

Looks like um so yeah. I think the the retrospective is a good call out here, as we uh get closer to the first retrospective. Please make sure to go ahead and add any items to that document that come up.

B

Yeah, I think it really also has a topic.

C

I had one um yeah, it's not really really simulated, but it is coming related. The uh kubernetes monthly community meeting is tomorrow at 10 a.m. Pacific. I I put the link to the agenda on this risk team agenda.

B

Yeah and I'll be there to give the release update so um welcome everyone to be there with me. Thank you.

A

Yeah thanks for calling that out. That's that's a really actually nice meeting uh folks who haven't joined that before I would. I would recommend it. It's definitely worth your time all right and now we can go to enhancement. Sorry, priyanka now is your chance.

D

um So our overall status is green. um We have received 59 kips, as of uh today um we have dragged 18 uh out of them and then 37 are still at risk. Out of all, we are tracking 27 alpha 13, beta, 14, stable and one duplication on the uh uh ones that are at risk. At the moment, most of them are having their kept open.

D

um The team is actually like continuously tracking them, so we'll have the number increasing uh in coming days. um Also yeah biggest update uh is enhancement, freeze, move by a week, so the new enhancement date is now june. 23Rd um and another update for me is I've, sent out the 1.25 enhancements update today to the kubernetes dev mailing list.

D

That's all from me.

A

Sounds good, do we have any questions for the enhancements team.

A

All right, let's move on to ci signal with arch.

E

um Hey everyone, so our current status is yellow. We had like two failing tests in the morning, both in master informing one of them has been fixed by cluster life cycle folks and for the other one it's a bit of an odd ball because, like we did create uh issues for them and, uh like carlos, uh told us that, like it, has been fixed but on the dashboard it like still shows as like failing, but it's actually flaky.

E

So I also posted about this in the release ci signal channel, because the particular test which shows it's failing that has not had like any runs like in on tesco. It just shows white boxes for that. So that's the only one, but I would consider it as flaky since, like folks have confirmed that, so uh those uh should not be a blocker. The thing I wanted to ask was like: are we having the alpha 2 release this week because it said week 4 in the timeline.

A

um I guess they don't actually know where we are on that.

B

um I I'm not sure if um veronica is here to give the update today, um but we are targeting this week. We are currently blocked by some um cigarette engineering work, um we're kind of waiting for the two to be fixed before we actually cut the alpha.

F

Yeah I'm here um I cannot edit the document but um yeah I'll figure out after this meeting uh but yeah I I can wait till it's my turn to give the update.

E

Okay, uh so the reason I brought that up is like, if we are doing it this week, then it's a go from like ci signal for the alpha to release and the last.

F

Thing I wanted.

E

To bring up was sorry.

F

Yeah, it's okay! uh No we're doing alpha one today uh alpha two! I just updated the the schedule um and I'll talk about it later.

E

Okay, all right, thank you so much. uh The last update from my side was that, like uh only like, I had been posting weekly updates, but now, from now on, you will see like ci signal shadows, also posting updates in slack and on the mailing list. Those were the three things from my site. Thank you.

A

Awesome. Thank you. Any questions for ci signal.

A

All right, let's move on to bug triage with hussein.

G

um Hello, everyone um at the moment there is no uh plugging um issues for the current release and also uh no blocking pr for the next um release. uh Beside that, we are tracking all the targeted uh prs and issues for the next milestone uh by reaching out the owners and the signings to the pull, requests and issues. uh That's all from my side.

A

Awesome any questions for bug, triosh.

A

All right, let's move on to docs with kristen.

H

Hi we're um our status is green. um We get the required github access set up for the team. uh Our two new shadows were uh added as uh org members, and I got the pr open for the integration branch for 1.25 docs and also merge the pr for updating the website config ahead of the release, and that is our update. Thanks.

A

Thank you. Any questions for the docs team.

A

All right and then is there anyone from release notes here.

I

So we are still waiting for the alpha tag to be created to create our first draft.

A

Sounds good uh any any questions for release notes.

A

All right, let's move on to comms.

I

Hi so uh comms we are, as usual, a bit slow in future days, so sido onboarding has taken place and initial discussion uh regarding dividing among the status is taking place for future blocks and uh thanks today, most of the comms regarding the extension of deadline finance process has been sent out. I think.

A

That's it sounds good. Any questions for the cons team.

A

All right and then I will pass it back to veronica for release branch management.

F

Hello, so, as I said, I haven't figured out how to edit the document. I think someone has to give me access. I have already tried requesting it but anyway, uh so, as I said uh earlier last night, I pushed uh the proposal for the schedule for on our behalf.

F

uh It has three alphas uh one beta and the release candidates. We really don't have time for more, unfortunately, so this week uh today, actually we're cutting alpha one, uh let it bake for a bit and then alpha two. I don't remember where I put it, but I think two weeks from now, um but anyway, it's all in the I submitted a request and it's merged, and so you can see it in the calendar uh already. uh Let me know if you have any questions. I know that.

F

um Ideally we would have two betas, but, as I said, we don't have time so yeah that that's it thanks.

A

Thank you. Any questions for release, page management.

J

Yeah I well yeah, I may have one so regarding the two videos uh during some of the past releases and the request to have two betas came up, because some sometimes so. The idea of the beta is that people will test their final code in the beta and if any adjusts, adjustments or any last-minute fixes have to be pushed.

J

The some of the seekers requested a second banner to to ensure that they get a release on what to do.

F

J

F

I hear that and also uh since I have been cutting those beta uh in my experience, it's always like um open to whatever is needed. You know like for 10 23.

F

I remember we caught the last minute later so, and that was not even in the schedule, so um I think I am happy to to put another beta there, but I think that the towards the end from beta to the first release candidate there is only a week of difference so uh because we all know uh that we were a little bit behind on the alpha one cut. Another thing that we could do is cut alpha one today as planned and instead of waiting two weeks just uh speed it up.

F

But I don't know if there is a benefit in that, because at the end of the day we end up cutting last minute things many times so happy to to to update it. Us.

J

Yeah: okay, yeah! That's that's yeah! That's that's! Well! Yeah! Let's carry the conversation to the to the to the actual pull requests, but the idea is to actually schedule those beforehand so that we don't have to do it in the last minute and uh I.

F

Know but since we didn't have a branch manager, yeah.

J

Yeah, the the final goal is to when we cut the rc. We want to have that as stable as possible. So if, if uh folks find any issues and last minute changes that need to do in the first beta, we need to ensure that they can test it and not play around in the rc. Because then yeah.

F

Exactly yeah yeah yeah for me, oh actually, yeah for 123. We ended up cutting another rc yeah. It was.

J

F

A

Sounds good as always. Thank you all to all you do relinch team. It's uh seriously awesome um all right um pass it over to ray for any of his updates. Hey.

C

Folks, um so we held two release team shadow orientations last week and today is the last scheduled release team shadow orientation. uh It's at 1pm pacific. If you are unable to attend any of these three sessions, please reach out to me. uh We could schedule something one-on-one or we could uh probably have a fourth uh shadow orientation sometime next week or anyway. That's it for me feel free to reach out. If you have any questions.

A

B

And cece you're up, thank you. So um the biggest update would be the enhancement phrase extension uh as mentioned earlier uh by enhancement team. So it's now on june 23rd. So we have our prrs of deadline also extended to tomorrow. um I've been talking with the pr review reviewers. This seems okay with that and they're working fine.

B

So I should be smoothly and also I was still doing some of the onboarding work, the rest of the team who um just got the kubernetes member um access was being awarded to the sikh release team and also for uh veronica's previous question like if you don't have access to edit the doc that might because you're not part of the release team. Yet um I can open up here later today to add you there as well um yeah. That's all I have today. Thank you.

A

Sounds good and then do we have any other final topics that anyone would like to discuss.

A

Sounds like not. um I see we do have the walk project board on the agenda here. That's not something that I've done with previous meetings, that I've run um is there anyone that would like to take point on that.

A

I can um can open it up here to have a look, but.

A

If not, I can end the recording and uh we can call it a day.

A

Thank you, yeah thanks. Everyone.