Kubernetes SIG Release, 12 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Kubernetes Release Team Bi-Weekly Meeting for 20221012

A

There we go okie dokie folks, uh good morning. My name is Kat and I am the host for this kubernetes version. 1.26 release team meeting today is October 12th, and this is the sixth week of the release cycle yeah the sixth week. So uh just a reminder. As always, uh this is a kubernetes community meeting and as such, it falls under the kubernetes code of conduct, which pretty much boils down to the excellent to each other. Thank you for being excellent.

A

uh This meeting is being recorded and will be posted to YouTube, so keep in mind the permanence of the internet. When you think about what you're about to say next, let's get cracking so uh open discussion items. It looks like there's not really anything super new in here other than, please remember, to add any comments or suggestions about the release process to the 126 retrospective doc, which is linked in the agenda.

A

Do we have any new people that have not introduced themselves so far? That would like to do so here.

A

No cool at this point, I didn't think so. This far end uh nothing we've parked for later, nothing not on the agenda all good onwards. The team updates then so enhancements with ryler. Take it away.

B

Yep, hey everybody, uh everything with it uh enhancements is going pretty well, our current status is green. About a week ago we had enhancements, freeze last Thursday and since then, we've received four exception, requests, three of which have already been approved, and the metrics are good as well. We are tracking uh 49 enhancements, uh 21 Alpha 14, beta 13, stable and one deprecation.

A

Excellent, thank you and congratulations on the freeze up next is CI signal.

C

So hello, everyone, uh our current status, is green and on Master blogging we have zero, failing jobs and six flaky jobs and and Master and forming uh also we have zero failing and eight flaky. So as we have no failing jobs on Master blocking and informing, we gave the go signal for the release Branch yesterday and yes, for the note uh can be taken up by nivedita.

D

So yeah hello, everyone actually I want to bring oh.

A

Am I just hearing it Echo looks like yeah. Okay, thank you for the update, glad everything's green. So far uh up next we've got bug triage.

E

um Hello: everyone, uh our current status, is green, so uh we have no plugin issues or PRS for the next release cut at the moment everything goes fine. We got a few PR's and missions today, I just updated our project about using the shutter script that you know they have about donated so I'm, also working on the automation using negative actions.

E

So the the board will be synced every day, uh yeah once in a day, so the issues and PRS will be automatically synced with their project boards. That's all from other side.

A

Thank you so much uh next up is docs who appear to be uh editing. Okay, sweet glad, you're here.

F

Hi cat, can, you hear me sure, can yeah.

A

G

Second, if we could go to cseco back because I think Nivea said.

A

Exactly yeah, oh yeah go.

G

Ahead, I'll try if the mic is not working.

A

Oh, we can you're very, very quiet, that's what I was hearing. Okay.

D

Now, is it better or not,.

A

Not not quite uh it sounds like you're very, very far from the microphone okay.

D

Good I'll just.

A

I can hear you better now is.

D

A

Go for it. Okay,.

D

So actually, I want to bring one topic. Yesterday we had a discussion uh regarding freaky test on the release, CI signal channel so actually sometimes not sometimes, most of the time, it's very difficult to actually recognize the flaky test. So we are thinking to document most of the things with the help of say, testing or also we are thinking to uh thinking to just to arrange one meeting to transfer the knowledge, okay and yeah. We are not uh like. We are not sure about this, but yeah. We are discussing on this CI signal channel.

D

So if anyone want to give any input on this, yes.

A

Okay, thank you uh yeah, that's something that we should probably all take a look at. Thank you for that and sorry about uh not being able to hear you at first I apologize is that it for CI signal or bug triage.

E

Cool um I'll find from other side, okay,.

A

Next up is Docs.

H

Hi this is Jacqueline I'm, giving the update for docs this week. um um I think I've updated everything, so our current status is green and uh we have about 79 enhancements that we're tracking and we've assigned all these to uh the different team members in the docs team and we'll be tracking them. So far we don't have any open PRS that we're actively looking at, but PRS are welcome and I wanted to I know this has already been communicated, but I wanted to like uh send out a request.

H

The enhancements lead to probably send a message about the doc deadlines so that people can keep them in mind right. So that's it from us.

A

Okay, thank you. Next up is release notes, hey.

I

So release notes is looking green. We are currently working on release notes for Alpha 0.1 and later this week. We're also going to be shifting for the release, notes PR for Alpha 0.2 and on the back, we're currently working on improving some of the the stuff that goes into the work for release notes. So that includes the n2s test infrastructure, as well as upgrading Cyprus to 10 to version 10. so posted that PR on there depressed.

A

And up next is comms.

F

All the six have been notified about the feature block, opt-in and the Shadows are assigned to eat sick for following up on that, and there.

H

F

A discussion going on about the mid cycle in the slack in the release, note Channel and it was decided to I'll bring it here in this meeting. In short, it was about the discussion was about um to whether to have a regular mid-cycle blog or to postpone it and add the nature themes. Can it as well.

A

um We've we're tracking one deprecation right, just one.

G

Yes, so right now, there's there's not much actually to to like to write on the Block, so we, the idea, was to combine both um blocks together. So it's it's a bit more lean, but if we publish um the major themes a bit earlier, it's not guaranteed that actually, all the features are making it past cold, freeze and past great final release cut. So there was the concern: if we publish the block soon sometime soon, we could communicate something which we at the end don't deliver.

G

So the idea was now to either propose the deprecations the major themes block so keep it together or um just add the deprecations in the final release block. So basically, if, if the um after the release got cut in in the block which announces the changes, we could also put it in there. So.

A

uh Rodolfo has his hand up.

J

Yeah I vote for the second option, that is, to get together, duplication, removals and major teams in a single block, and we can do that after the code freeze it, since uh some changes could happen between today and the day of the release. So I would like to have a only one block for all those three I.

A

Agree for what it's worth, uh the deprecation blog doesn't actually have to come out in the middle of the cycle. Right so I think it's fine uh Frederico has his hand up yeah, no.

K

Just to say that it's no obstacle from comms, uh obviously, and thank you ashita- for uh sharing our position here. Our position is essentially the one that we get through consensus. uh The mid-cycle blog is an optional one. We are very light in terms of actual duplications. The discussion was about. Maybe we could just Identify some major changes which are not deprecations but in the same Spirit of the 125 release. Obviously, but um I think that, with the such a small number of actual removals, uh maybe would we would be grasping at straws with that.

K

So uh for for me, I think, that's uh if the majority um degrees that we can bypass this mid-cycle blog, because we do not have enough material. We can surely add it to the to the major teams block.

G

I think it's it's still, even if we don't have like a lot of deprecations, I. Think and I also comment. This in slack I think there's still value in just communicating, there's just a few deprecations there's also. This is also a message and it might also be interesting and yeah.

G

That's good excellent.

A

Thank you uh anything else for comms.

A

Okay. Next up is release Branch management.

A

L

So CC yesterday I, don't think she's on the meeting um she cut the Alpha 2 release, um so everything went according to plan there smooth sailing and then we've got Alpha three coming up on November 1st. Well, we're all you know basking in that post, kubecon glow. We will cut the uh the Alpha 2 release and uh yeah. That's uh that's everything. Everything from Branch management.

A

Woohoo, nice good job, Cece, uh no notes from our Emeritus advisor. It looks like unless he wants to pop in and say something nope then onwards to our fearless release, lead Leo.

G

Hello, everyone so um the first topic we already created from ryler about the exception, requests we received. Fourth, we are accepted.

G

You can check in sick release, there's a threat which discusses, if, like the exception, request, goes into the release. So, if you're interested into how this process works, um you can check it out, there's currently one which is the second one in the list sub second probes, which is currently a bit unsure where we tend to approve it, but we're waiting for Signal chance to give a thumbs up um because there's like some concerns, which we discussed in in the fetch. But it looks good, hopefully, by the end of today or later tomorrow, we can.

G

We can finally decide um so so far, so good um I right so I sent out a doo-doo I think on Monday to find, like the best time spot for the Apex friendly meeting. So next week we will start with another meeting, so we have two each week um the one on Friday I stand for folks who are in Asia Pacific somewhere in this time zones, which is currently a bit difficult to to attend on the Wednesday meeting.

G

So um if you have not done so, it would be good too just check your time boxes and we can find the best time slot awesome.

A

Thank you. uh Is there anybody here from Sig, scalability I think there usually isn't.

A

Nope, okay! uh Well then, that comes to the end of the team update. Is there anything else that we would like to discuss on the recording.

I

A

And I'll stop the recording.