Kubernetes SIG Release, 12 Jul 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20230712

Description

Kubernetes Release Team Meeting for 20230712

A

Finally, uploads on YouTube.

B

Perfect, all right cool, hey everybody. uh My name is Mickey I'm, one of the release lead Shadows. um If you can't tell by my manner right now. This is my first time leading a call. So welcome um today is Wednesday the 12th of July, and it is week nine of this kubernetes 1.28 release cycle um Please. Be aware that this is a kubernetes community meeting, which means that the cncf code of conduct does apply and, although I'm sure, you're all very familiar with it.

B

What that essentially means is that we all should be excellent to one another um cool, also worth calling out. This meeting is currently being recorded and will be posted to YouTube.

B

um So again, if you prefer not to have your face on the screen uh feel free to turn it on for your video, and also please be mindful about what you're saying is being recorded, um awesome, okay, so as people are filling in their information, um we're gonna jump down to the open discussion section.

B

uh The only discussion topic we have right now is the one we've seen on for the last few weeks, which is to please add any comments and suggestions to the 1.28 Retro doc um and that's in order for us to discuss that's going to come up in a couple of weeks from now um and cool we're, seeing some comments added right now, so I will give folks a couple of seconds to add additional topics.

B

All right uh Mophie did you want to do the introduction for the bug, triage team.

C

Are we starting off with that? Okay yeah, why not cool.

C

Like a good presenter, I did prepare some slides, so I don't know if I should jump on that now.

B

C

B

It's not nice here and you.

C

Can do that yep I'm, just looking for the window, that's gone, never to be seen again. I found it. It is okay good, so you go there and I will bring you here for you, oh nope, I cannot. Screenshot host has the disabled in the screen sharing.

A

Well, Mickey, if you can make him co-host.

B

All right: do you want to try.

C

Now uh yep, then my screen changed. A little bit looks like I have um unlimited power now, but I'll do it? Okay, if anyone please give me a thumbs up when the screen is being shared, that would be awesome. Yep looks good fantastic. Thank you, hello. Everyone, my name is movie. I am one of the bug trash Team Shadow. We have workout as well in the call who is our lead, so um I was asked to quickly give an introduction with what the bug trash uh team does as well as kind of the recent discussion.

C

That's been happening about the margin of the team and what that kind of means in the future. For us, this CI signal unbox team together. So again, if you were to ask her, what would you say you do here like the classic office space meme? uh Basically, the theme is responsible for looking at all the different issues and peers that are open at the moment before the 128 release at the Milestones. Keep track of.

C

All of them are in track for release and like maintaining all the code freezes uh we periodically reach out to the maintainers and the issue. Creators and the peer openers, so that kind of nudge them that oh, this is like the deadline, for example this week, pretty much all the issues that we're tracking got an update that next week is going to be code free so that they should get their Affairs in order before that happens.

C

um We also like President Besame in this call every week, just to let them know that if any issue is in at risk, we keep track based on like five different, like on track at risk and like or like this kind of status of individual issues and PRS, and we periodically reach out to the issue owners and maintainers to make sure that it's all moving along for the release on time. So the discussion I've been reading and like hearing about the two teams merging like the um Buck trash and merging with.

D

C

Signal there has been discussion from a long time. I think the goal initially was to do it for 128, but again it was kind of too late. So it's going to happen for 129.. So if you have not been like reading up on, all of this I have done the reading for you. So I can kind of give you a quick TL there of what that means. So CI signal and Bug trash are Marching as a single theme for 129.. A new name is still funding that I think in the last couple of meetings.

C

There's a lot of good suggestions, I'll list them in the next slide here, so people can take another look again. Team will consist of folks from both existing teams and new Shadows. So, ideally, usually what happens in the kubernetes release cycle, uh the previous Shadows usually take a lead position and new Shadows are added, because two teams are merging I think the plan is to then grab Shadows from both the existing teams, because they know individual theme, functionality pretty well, and the new team will take on combined responsibility of both teams.

C

Again, CI signal and Bug triage usually does like seven to eighty percent of similar things about tracking issues. There's some difference outlined on the individual handbooks, so possible names I think there are three Front Runners right now, really signal CI bug, Bashers and release tracking, but there is again some good suggestions. I think this is still up for discussions if you feel strongly about any of the names.

C

I think uh we'll probably talk more about this today, um so we'll probably come up with the name before the 129 release team is declared and the Shadows are asked for so again. This is what the state of the name situation is again in Computing naming is one of the hard things, so it's going to continue going on that way, so the handbooks has been updated, I think forgot. We have a couple of peers open on that regard. To update both of the handbooks.

C

um Oh release signal is winning by a big margin. Fantastic um uh having a clear winner is great, so handbooks, both handbooks, uh like we have couple of peers open to kind of bring the bug triage handbook up to date. I think the plan is to have both of the handbooks uh around for now.

C

Both CI signals back tires after 129 we're going to merge them into a single handbook and then, after one to Nanny release, we're probably gonna get rid of the old ones and have a new uh release signal handbook for that kind of covers both responsibility.

C

So that's kind of like what I wanted to talk about. I think forgot. If you have anything more more to add, you can jump in at any point um so yeah.

E

Hey Joe thanks Murphy, that was pretty much thanks for covering uh one exception, is uh please take a look at the PRS that are open, one is already merged and the second is still under the review. So it would be nice if you could go ahead and merge that and after that um actress handle should be updated. Thanks.

B

Cool, thank you both for the update um now. Can everyone see my screen all right.

B

Cool um is there anything else not on the agenda that we'd like to talk about during open discussion.

A

um I think docs has a presentation too, but we can do that after the eventful sounds.

B

Good thanks, Grace all right cool on to enhancements.

F

Hi I'm Nina on the enhancements team. um Our current status is green, uh like it was mentioned, the code freezes coming up on Friday the 19th um and we have six C tracked enhancements: 33 Alpha, 19, beta and 15 stable.

B

Cool very exciting any questions for enhancements.

B

G

Right nice on the CI.

D

G

Yeah so for Signal, word green as well we're we only have one failing and the fix for that was already sent out. The test just hasn't ran yet so we expect that to be passing uh later today, um so yeah we're looking good Alpha 4 is live now, and the beta is scheduled for next week. So yeah.

B

We're good awesome, that is great news. Any questions for CI signal.

B

All right moving on to bug triage Mophie.

C

Hello, everyone me back again uh uh back trash is also seeing all this green. We have tracked all the issues. All the some of the issues uh are at risk for missing code freeze, but we have informed all of them of the deadline for code free. So on that we are all green.

B

Awesome uh any questions for about triage.

B

Cool answer: docs cat.

H

Hello uh Fox's current status is yellow.

H

um We have 26 caps remaining with no docs PR, yet um ahead of the deadline next week, but all of those cap owners have been contacted again with a reminder to even just open like an empty placeholder PR.

H

um This is not particularly atypical for docs um a week out from the deadline, though so I'm not worried.

B

About it, yep totally agree based on our experience at the last time in the docs, so no need to be discouraged. uh Any question for docs.

B

Cool uh release notes.

I

uh Hello, everyone.

I

So we are going to Marcus of yellow.

I

Time off uh the same issue was also faced in alpha one as well as in Alpha 2., uh but they passed the safety retriggering the job, but the CI issue itself here.

I

B

And is there any additional help that you'd need to unblock that or do you feel like you're all set.

I

Try to referencing, you have created a discussion trade in the last early, smooth Channel as their big trucks. um If it's.

B

Okay sounds scary. It sounds like we can try to talk more about that offline.

A

Yeah are not worth mentioning that we for that um I, don't know when Arnold are you here can should should someone do that or is there a PR out for that right now,.

I

A

Yes, sir, um so Arnold mentioned that, because it's an npn build, it might take a little bit longer and we can follow PR to just extend the time out and see if that fixed a problem. But I don't know if, if anyone is extending that time out to send the link to this last discussion in the chat and then we can pursue that.

B

I

B

Thanks Chris all right on to uh once it comes Brad.

D

I'm stepping in for Brad today cool um just green, uh nothing much to report. We just have some placeholder PR for the blogs for um storage, apps and infra, and we're just reaching out to more of the sigs.

B

Sounds good any questions for comms.

B

All right now, once you release Branch management.

J

Hi um I think instead of the screen right now um lights. Yes, you know say Alpha for is out so getting ready to do godfreys and beta0 for next week.

J

I, don't think, there's like something specific regarding red orange, but what we see.

B

Thank you um now, I, don't see Leonard on right now, but it also looks like he does not have uh any updates from his end. um So Grace on see you.

A

Any new updates from me either um this might be a good time for the docs team to do their presentation.

B

uh Sounds good unless we have anyone from six scalability on. We want to knock that one out.

A

B

All right going once going twice cool, see the docs team presentation: okay, I'll I'll, stop my share book and someone. Let me know who to uh give co-host duties to.

G

Go to receipt sounds good.

B

All right, you're up.

A

Yes, you thought no one has a question. Should we.

J

Yeah after after the press, okay, again.

A

Yeah sounds good.

A

I don't know we can hear you yeah.

K

Sorry my word I had selected another my consume. We.

H

K

Now yeah uh hello, hello from the Dogs release, team and dogs, has been around for all of these releases. So I'll just take you another in a quick walk through through what the talks team does, uh what kind of deadlines we have and yeah it's just like a quick walk through uh about what we do so hello from the docs team for one two one point: two eight I am rishath and uh also hello from uh other people in the docs team this time.

K

So let's take a look at what does a clip look like, and there was a lot of talk about this at the last release. Team mutants I'll not go into that, but this is what a clip looks like uh and let's take a look at this part of the clip. So so there's the so there is. The K website update the origin.

K

This could be anything from just just a small, um just a small feature get change which it says that uh the state of this feature for 1.28 H beta or this could be a huge PR here- uh a lot of documentation here, a tutorial here. It could be whatever or there could be. No need for documentation at all, so so that's what goes into this part of the Gap, and uh this is mainly what the docs team is involved with.

K

So uh so one of the first things you do is uh try and identify if there is even documentation needed uh for a clip.

K

uh So uh if there is no need for a documentation, oh well, then that's pretty straightforward, but if there is some need for documentation, then we do some other ships, but first we need to identify if, if there is any need for documentation at all next up, uh if there is some need for documentation, we track these documentations either a huge PR or just a feature will change on the Enhancement, Board and uh I'm.

K

Pretty sure everyone might be familiar with the Enhancement Board, but I could probably pull it out, and so so this is the enhancement report uh from one of the earlier releases, and this is what the docs looks like, where we truck uh what the dog status is, if it does require docs and all of that, so so that is also one thing we do and now that we know that if something requires a docs or if something requires a docs PR, and we track these on the announcement board so and then we come to the talks VR itself.

K

So this is what a docs PR looks like and particularly I want you to take a look at how this PR is made. So this is made into the kubernetes. Are the 1.28 branch uh in the kubernetes website repo? So we also create this branch on maintain it and sync.

K

uh At the end, what happens is uh all of the 1.28 docs updates are merged into the dev 1.28 branch and which is in merged into main, so we can have all the 1.28 documentation on the kubernetes docs website. So uh so the docs release theme also creates this branch and maintains it and sync, with the main branch.

K

And we also try to uh we. We. What we also try to do is help help and offer guidance contributors on how to contribute new features uh or even understand if a feature needs any documentation or modify existing docs to uh to make sure the feature documentation is appropriate.

K

So so all of this is another 1.28 Branch also and uh for. Furthermore, so all of these documentation peers need to go through the documentation cycle, just to make sure that uh the quality of each VR is maintained. So we collaborate with sick talks to review documentation viewers uh according to the documentation style guide and there's also an aspect of technical accuracy if all of these documentation pairs appropriately uh appropriately show what the feature does or what the cap does. So. This is also another thing uh that uh that the docs team does around this.

K

We also have a deadline where we just make sure that uh all of the cap owners have created a documentation via a draft documentation, PR and then another deadline to make sure that all of these draft documentation, peers have been reviewed and then another deadline to make sure that all of these have been merged uh into the dev 1.28 branch.

K

uh At the end, uh you would also see that there's always a release log, so we also collaborate with the release comms to review the release blog and when all of these changes are made that have 1.28 Branch there's also all of these localization uh localization efforts. So there are quite a few languages in which the kubernetes documentation is localized, so we also collaborate with these localization branches uh to make sure that the 1.28 updates have been uh localized as well in all these other languages.

K

And finally, when all of this happens on the website, you see uh kubernetes documentation versions. So so we also migrate the docs website for the release, so that is uh have so when the 1.2 it would be released. There should be a 1.28 being showed up over here and all the 1.28 docks should be shown up over here. So that's also something we do, and this is- um and all of this is pretty near to the release when the when the release happens.

K

So so that's pretty much what uh the docs release team does and a bit about how we work and what we do. uh It's just like a quick overview of it and and of course none of this is possible without the doxylease team and the release team in general and the whole kubernetes community, so so yeah, that's the toxic does.

B

Awesome. Thank you.

B

D

Any questions before you.

B

B

All right cool! Well, thanks everybody I'm going to stop the recording.