Kubernetes SIG Release, 18 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting (v1.25) for 20200818

Description

Kubernetes Release Team Meeting (v1.25) for 20200818

A

This meeting is being recorded hi everyone welcome to kubernetes 1.25 release meeting today we are at week 13 wednesday 17th august, and um they are less than one week um ahead before the formal release um as euro.

A

This meeting is under the same set of code of conduct, which could be summarized to please be nice and respectful for each other, and I have pasted the notes link into the chat, so please feel free to register your attendees there and let's go to the open discussion, seems like no topic here and will directly jump into the team updates enhancements mark.

B

Hi hi uh not much has changed from enhancements. um I think we're still green. One thing of note is many of the uh enhancements still have dock spears that don't need to merge, so I don't know if that would actually should put us to yellow or if there'd be some updates from the docs team about that.

A

Thank you so much, I guess enhancements can keep growing. That's what we'd love to see! Thank you so much for the updates and any questions for enhancements. Tim thanks mark. Let's move to ci signal. Anyone from cic.tm here want to give us an update.

A

If no I'll just say um it would be green and we, since we cast our card, our rc1 released yesterday and ci signal keeps going for um at least master performing, so um yeah, that's the current standards and then questions for ci signal.

A

No, let's move to bug triage hi, hey bye! If you're here hi.

C

Yeah so hi everyone, our current status, is green, no blockers issues uh so far, and uh only uh one issue to track the release. Note so uh and this this is a regular test, failing so uh no blockers so far, uh so yeah.

A

Thank you so much for the update and it's just got confirmed the current um pr wrist against the current milestone is not a release. Blocker, it's just a test test fixing yep. So thank you so much okay and any questions for bug triage before I move forward. If no, let's move to dogs cat, if you're here.

D

Hi, um so our current status is red because we still have a good chunk of um docs just already ready to review and not merged. um Still tracking 40 32 are merged, six are outstanding.

D

um One of them is in draft just one previously that hadn't opened a pr for that and then one without uh docs required also at the top. um The pr for this week to keep the branch in sync is open, so if anyone has a chance to review that that'd be great, although I believe there might be some um errors, I was just taking a look at it earlier before this.

A

D

Other questions.

A

Cool, thank you so much for the update. I guess the six ready for review pr will be merged, like I I would expect today or tomorrow.

A

If that's up that's.

C

The hope we're chasing people down.

A

Yes hope, like the authors, will pay attention, but thank you so much for the update any questions. Both dogs team.

E

uh No questions, just just um so it's it's fine to have a few late. There is a hard deadline to have the docs merge uh is when we freeze the k website, repo, which is typically 24 hours before the release is cut, but I'd like to let folks know that to get in by before a few days before that, just to make sure it really isn't before the ko website uh repository is um is frozen.

A

Thank you. um I hope the other will be aware of this as well. um They still have I'll see a couple days before the phrase, so hopefully they could get all the prc. Thank you. um Let's move to release nodes, hello, hi, hi,.

F

Hi, uh our current status is yellow, we have and pull requests open for, partial is not for release candidate zero is spending to be approved by jose gustos or by puerco.

F

Just to point it out that also we are going to submit a website pull request for adding the missing tags at real notes. A website they're missing, like two releases there I think I I we will check those that are missing and submit requests for that.

F

Also, we are going to submit a put request for release notes for ready schedule, one that was a really suggested rating and also we have a question and we created a put request for the release, notes draft and there is the the file there and our question is that if the bot automatically converts that draft into the final release- or we need to do something.

A

I think for previous release, someone from release team will do the changelog update, um so I'm not sure if release knows team will need to take care of those or, I believe for last release. um Someone from release team did that uh from thick release. Did that I'll double confirm, maybe um and I'll? Let you know um on flag.

F

Okay sounds good. Thank you.

A

Cool thank you looks everything's on track. Thank you. um Any questions for release, notes.

A

um I'll try to um ping the uh release management ping on the release management channel for the approval yep. Thank you. um Let's move to comscam cat.

G

Hey so our current status is green all, but two of our feature blogs, have content and are under review, and you might think that two of them being uh late might mean our status is yellow, but we have so many blogs that we're already going to be monopolizing, the kubernetes blog for like a month so potentially losing one or two of them um really is not a big deal here and we are chasing down those two stragglers.

G

One of them is from an author who absolutely will get us the content, there's so there's only one real unknown here.

G

um We're we're all good the release, blog pr is, is up and we're just adding um most most of the requested edits are in now and we're just adding the user highlights and waiting for the uh like ability to actually update the project. Stats um links, I'm not sure how that has been handled in previous releases. So I'm honestly, just gonna go ask mickey what he did, um but yeah we're we're all good right now.

G

A

You um yeah, it looks very all on track for future blogs. Any questions for constant.

A

No, let's move to release branch management, joseph hi, everybody hi.

D

Yeah, I'm here so um yeah so release candidate for 125, one number one was released, so that's a great thing. You know the feeler bumps along the way as we're going through this we're marked yellow just because you know we know like how things are with like ci signal and we take the keys from there, but we're uh getting ready for the excitement for next week. So thanks everybody for all your hard work.

A

Thank you so much for the update just want to make sure it's not blocking the um the final release. Right, yes, cool! Thank you and let's move to our ea ray.

E

Hey folks just want to remind everyone that the next uh retrospective on this release is august, wednesday august 31st, uh we'll send out invite shortly for that. um We're also assembling the 126 release team. So do you want to congratulate uh leo for being the release team lead for 126.?

E

I linked the issue on the agenda as well. um I'm sure the most common question I get is: what are the shout out? Applications are going to be open, so they'll be open up shortly. um The the uh ea for 126 is nabaroon, uh who uh in napoleon and leo, will get that uh shout out shout out application out shortly uh anyway. That's it for me, uh just feel free to reach out.

E

If you have any questions um about this release, if there's any uh doc prs that needs to be reviewed, I am watching those six pr's closely, so I will ping uh any tech reviews if they're needed uh folks to conduct those tech reviews if needed and also do a uh uh awesome review for sigdocs as well.

A

Thank you and congratulations again for leo.

B

All right, thank you. Thank you. I'm.

E

Super stoked about.

B

It yeah um I'm I'm super excited. I I um yeah I will let everyone know in in the chat um as soon as the shadow application is up or naboon will will do it and um yeah. I'm excited hope. I can see most of you um still around in the kubernetes open source project or in the next release. Team meeting and release team and yeah.

A

Thank you and I believe the next release will be a success, one as well. Thank you and just the um I'll move to the updates. From my side, um as previous mentioned, we have rt1 release card and announced yesterday, and we will have the release note completed deadline on thursday and I'll again share the release theme in case anyone missed it earlier. The release name currently said is combiner and um yeah.

A

As everyone knows, we want to honor the collaboration and open spirit of our community and also uh want to emphasize that kubernetes is a joint effort by not only many components but also many many, like contributors around the world. So thank you so much for your effort, especially the release team for um making the release as small as it is now.

A

Thank you so much for everyone here and we get the um scalability update from the current uncle, um which is great, that's nice and we don't have any update on the wall project board um any topic or anything I want to mention before I end the recording.

A

If no I'll go ahead and do the recording, thank you so much. Everyone.