Kubernetes SIG Release, 25 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting (1.25) 20220725

Description

Kubernetes Release Team Meeting (1.25) 20220725

A

This meeting is being recorded.

B

Hi everyone welcome to the um kubernetes 1.25 release meeting. um We are at week 10 now- and this is the first monday burn down meeting on 25th july of 2022, and this meeting um as euro is under the code of things. They have code of conduct which could be boiled down to just please be nice and respectful for each other, and we finally reach to week 10 and happy mondays. Everyone, let's see if we have any major updates.

B

um First, let's go to the open discussion section and I guess I'm the only one who have a topic here. I'm here just provide a quick update on the goloan 1.19, which I promised last week and from last week um we didn't actually know about the detailed released it yet, but the uh after our meeting last week, the go long side released a announcement saying they are targeting uh first week of august, which is next week for their go, 1.19 ga release and we have a tracking issue from kikiside as well, which I linked below.

B

um Please feel free to take a look. So basically, we already done um all the work on the um go, 1.19 rc2 release and we're just waiting for the final g release to be cut.

B

That's it so, hopefully it would catch the current release. If not it's okay, to move to the next release, which is, um I don't think that will happen if no major issue comes up yeah, that's the golan updates and any questions for that.

C

No, I guess just one comment, so this is similar to what we have we had in 124 uh golang 118.0 was released uh pretty pretty uh a few right before the the actual first initial targeted release date for 120 for kubernetes 124, but there were some issues with it, but uh for this one, so we had to wait for 118.1 uh and then the 124 release was delayed a few weeks um with golem 119. It looks like we're going to have at least at least one rc out- that's going to test out, maybe two rc's.

C

um So that's great. So hopefully you know fingers crossed that. We won't have a similar issue um with the golem 118.

B

Yeah thanks thanks for the um comments. Yes, we do have issues last release with golong 1.18 and we now uh have tested for like two rc releases from golan 1.19, as we just mentioned, and even if we caught some major um bugs from go alongside, I don't think we will postpone our current release this time we might just revert back to goal 1.18, which is also acceptable by um um architecture side.

B

So um I'll we'll see, but hopefully the rs2 rc release will help us will like protect us from running into major issues thanks and let's go to the update session um enhancement.

B

D

um Here uh I just have one: we just have one uh update that we are still reaching out for the uh to the kep authors regarding the code free uh and our current status is yellow uh yeah, there's also one more that we are uh going through the github beta project, uh the sheet, so we are trying out stuff. We.

B

D

Experimenting yeah.

B

So, just to be clear, the yellow status is only for the github beta projects, not for the enhancement themselves. Right.

D

B

Yeah yeah, thank you so much cool thanks for working on the beta products and let's move to ci signal arch. If you're here.

E

Hello, hey folks, our current status is green because we have like no failing jobs and master blocking. We have two failing on master informing one for one of which we have an issue created and uh it has been triaged so folks are working on it. The other one has uh we haven't, created an issue for it, but we'll do so if it stayed, this does not change in a couple of days.

E

uh The other thing I wanted to ask was that a lot of my shadows, I think only me and one other shadow on my team- is available to like attend meetings so between the two of us, uh like, especially since both of us are in the indian time zone. The meetings is it fine if, like we provide our updates on the dock because, like attending all the meetings, would be tough between just that.

B

Oh um sure sure um that sure would be fine just to update from the dock, but we do like expect, if possible, when the go and non-gold day, uh if, like one of you, could attend that. That will be awesome like before. Like we cut up like the rc, the formal releases.

E

B

Yeah yeah totally.

E

I'll try to run as many as possible. I just wanted to let the team know that yeah. That's the case. Thank you. So much.

B

Sure, thank you. Thank you for bringing it up and we do also have like the um slack thread, the four go and on gold. So if you could provide there, that will also be work. Working, thank you and let's move to bug triage busing. If you're here.

F

uh Yes, um so um I normally agree uh after you know resolving this plug-in issue with the kubernetes publishing boats, so that's resolved and yeah. We are green again so beside that we are reaching out all the issues and pr's regarding um code freeze coming soon and we are just letting they know that you know uh yeah if they are still aligning. You know with their 125 milestone, that's all from parks.

B

Thank you so much. um Let's move to dogs, please, if you're here.

G

Hey uh sorry about that, um doc's team is green. I think we need. It looks good to me on last week's branch. Sync pr we're just following up with enhancement holders uh owners for placeholder pr's, and then we did have a question uh for caps that are at risk. Do we still uh kind of follow up with it, with enhancement owners to get placeholder pr's open and then, if, if their cap is, if their enhancements removed, do we just close out that pr should we still be better safe than sorry there?

G

I don't know what the normal action is. There.

C

G

B

Still be better.

C

Safe yeah, sorry cc, god.

B

Oh no, I was just want to clarify, like uh the caps like as long as it's marked as tracked, I guess it's okay to go ahead and open the placeholder pr for other stackers. um I guess now it's safe to close their placeholder pr, since they are not targeting for this release like if anyone has any other yeah questions, please feel free to reach out. Otherwise we can we, I guess we can safely close them. Thank you awesome. Thank you.

G

That's it for dogs.

B

um If there's no further question for dogs, let's move to release notes if color is here.

B

If, no, I guess we just move to the next session and we'll use the wednesdays meeting to catch up with release notes team. Is there any shadows from release notes, monitor provided update before we move on.

B

Cool then, let's move on to comms.

A

Yes, thank you. So this is fred from comms comes shadow. The current status is green. We've been actively been tracking, uh all the different different feature blocks and mapping the caps into the corresponding push requests.

A

We have been doing so on an individual basis to really get the answers out. We have a couple of sigs which we are still trying to get some feedback from um and we are currently sending out the final reminders to all six ahead of the feature block freeze. So everything is uh as planned,.

B

Thank you so much for the update um any questions for comms.

C

Yeah, um so next week um is also code, freeze which I'll talk about a little bit as well, but um we in the last few releases, we've also published a deprecation and removals blog um around the same uh week as code phrase as well. So that's something just to start to think about. um I know cats already uh started to to raise those questions about the deprecation removals blog uh so that just something start to start uh this weekend continues next week.

A

And we do, we do have a draft for that. So.

B

Yes, that's great yeah, yeah yeah. I just want to mention that I I guess can also mention that, like a couple of updates back, um they are planning uh like a mid cycle on blog post and I guess it's in draft now. Thank you exactly yeah cool thanks for confirming and let's move to. If there's no question, let's move to release branch management veronica. If you're here.

H

Veronica's not here, but I'm I'm here, and so we are yellow. We always kind of keep ourselves in a tentative state with releases. No more alphas are planned. Rn there's some discussions around the next upcoming release, which is scheduled for next week um right after the branch or the code freeze, and we may potentially add another release candidate in there. But outside of that, no other updates. Everything looks great.

B

Cool thank you for the updates. I guess like on schedule next week. It will be the beta card right. Yes, yes, cool, thanks for confirming and let's move to our ea ray.

C

Hey folks, um so we're coming into the last four weeks of the release, which will go really fast and actually most a lot of work will be done in this last four weeks we kind of had like a little. um I guess a little slow spell uh when the features were being worked on code wise. uh So next week is code freeze, um and so that is a big milestone uh for the release along with code. Freeze, as jose mentioned, is also the beta cut as well.

C

Also there's a doc placeholder pr deadline as well next week and deprecation removal blog posts that will be around next week as well. So so next week we're going to have a few several major things coming up, uh starting especially in the last four weeks of the release it just it's gonna go really fast uh and it's gonna be a lot of work most.

C

I I would in on the release team side I was uh my opinion, is always like the most work is, in the last last part of the release, uh the last four weeks of the release in two weeks. It's gonna be test for use. uh That's when the release uh branch for 125 is cut, uh then degrees candidates is a with the first release. Can it's also cut as well?

C

We also start the final phase of the release notes. We start to build the major themes and start doing draft for the final release blog as well, so uh so, the last four weeks, it's gonna, be it's gonna, be pretty intense in terms of the release team uh wise as well uh all right other than that. The next week is also the first release retro as well. So that's on wednesday.

C

That's at 10 a.m, pacific, uh and we we and we started doing the release right in the middle of the cycle in 123, so that we could course correct if we can- or we could also catch up on on some action items from the last release stretch as well.

C

I'm going to send out mitt psycho surveys for shout outs this week need to get those approved and also one final thing for me is to uh since the last four weeks. We need to start thinking about succession, so we have um roll leads uh to fill for 126. if you're highly. uh So this semester's for both rollies for shadows for really to start to think about succession for shadows.

C

If you're, if you're considering about um you know you might want to reach out to the role lead as well and I'll, send out some more communications about this, so uh so we're gonna start building the 126 team since we're um in the last four weeks of the 125 league cycle. So I jump it up for any questions. For me.

E

Hey right now, the answer should be sorry. Just.

H

E

I wanted to ask that, uh should we like uh reach out to shadows if to ask if they're interested like yeah.

C

I'll I'll send some comments out I'll reach out to the royalties.

E

C

H

Between you and myself, I don't think we had a chance to go over the action items, I'm sure you're, probably prepping, um just just reach out. I think jeremy as well mentioned this previously, but make sure we have follow-up so that we can make the retro grow faster.

C

All right sounds good, I'm gonna start reaching out today. It.

H

Was on my list thanks.

B

Okay, any more questions for me.

B

If no, I will move to the next session um for me and thank you so much for ready to list up all the like remaining works for the following four weeks and that's the reason why we added more meetings. I'm sorry. So we started the monday burnham meetings today and we will um have the daily burn meetings starting next week and our retrospective meeting, as we mentioned, is scheduled on wednesday this week. So please feel free to add any um items.

B

If you want to discuss about and yeah planning our time around and uh of course, the manger's name for this week is the code phrase um coming early next week and I have already sent out a reminder, email last week and I'll try to send another one or two at least um for this week, and hopefully people are aware of that and plan their work around um yeah and also the last thing is the golang updates. I already mentioned earlier and any questions.

B

If no, let's see seek scalability since um they're working, fine, don't have updates on today and for the wall project board, we didn't use it much. Let's see it's updated 12 days ago, so I guess nothing mentioned before, especially for current release, and I guess I'll just give everyone half an hour back, um adding questions before we end the recording.

B

I'll, take it as a no and I'll try to.