Kubernetes SIG Release, 29 Jan 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes 1.10 Release Team Meeting 20180129

Description

http://bit.ly/k8s110-burndown

A

All right everybody: um this is the first ever totally non video release team meeting due to crappy hotel Wi-Fi. It is Monday January 29 to 2018. I am the release team leader, Jay, singer Dumars, and if you want to follow along after the fact the agenda and such is available at bit. Lee / gates, 110 burn down and that won't get you to this document and I'll go ahead and get started and Caleb we're doing a video free today, so it I. Might my crappy hotel Wi-Fi doesn't die.

A

So if you don't mind showing your camera, although you look very sharp today,.

A

Alright, so I'm going to paste burn down document in chat, if you don't have it already, and basically, hopefully would be a real short meeting this week timeline for this week. Looking good the feature freeze against today, a do you want to touch base on that and sort of give a follow-up um we're at.

B

Absolutely so we are in a good progress twist with the features for dis, really some reason: tricking, spritzer discos, the amendment second place, so we have certified features in this release. I I've been grooming into a back. Look during the day to day in and lost will an english-based. The total number features a bit smaller than our comparing to press release in 2017, but it's big natural because we click through some six to try the kneecap process and sore.

B

Also, this is the first release year and so many he seeks don't have commitments for exactly this release, but they have promised that they will continue working on some features in the next releases. So that's that's mostly often me we're going to follow up. Where is the market into you tomorrow, and the most notable features for this release that we are going to highlight your on the marketing are loose, related and feature related activities and are. This is also to call for the documentation team under listener, o team.

B

So the table is yours and feel free to reach me if you have, if you need any support during your documentation or release, notes related activities that are touching features in some way.

A

Okay, thank you. Your any questions really.

B

On that death toll from me yep any questions, I.

C

Didn't have any questions just to Thanks and you know you'll be hearing from me. It's Jennifer, absolutely 24/7 here a question.

D

Who do I ever think who do I have to kill to get a non user-facing tag for commits.

B

In the Cabana, just given edges ripple, you mean it before debase himself or maybe.

D

Well, we we had talked about when you talked about putting into the PRS the PR template the ability for people to mark that a non user facing. So we don't need to pull it into the release label.

E

You should have to kill no one I guess.

E

To be able to help you in either in Trebek's or suggesting which all the accounts are there cuz.

D

I keep asking and I keep getting different answers: okay,.

E

D

E

Get an answer by the end of today, just to put me on the hook for it and I else make you miss Kayla miles. Okay,.

E

Although we do have the release note, none label which.

E

To signal that, but if you want in another label, make sure print rebec's is fine, it's a divine thank.

D

You I appreciate that yeah, because it's what we.

D

Some people, don't what some people consider to be not necessary, is not necessarily what we consider.

A

D

Be not necessary, so just tell us whether or not shoes are facing and we can make a decision. So thank you.

A

All right, thanks Nick any.

B

Any other feature religions great chance to me: I- can move em, Cyril, jeez Nick.

A

Alright and I'm just gonna hand the ball off to Caleb, to talk about the alpha release.

E

Yes, I guess not much to say, cut dot on Friday. There were no hiccups there. Now that I'm fully on that's pretty good.

E

No problems we'll need to get a report from Josh about the CI signal. At the time I cut it looked greenish the Elaine, some that look like this and issues, but I need to I guess confirm who the and joiners are on the GC PGE side. Well, thank you.

A

Okay, great and as you're going.

F

Through this process,.

A

Caleb one thing is to just keep an eye on things: you might wanna improve things you can fix up or.

E

A

G

G

Oh I was like I was maybe talking with scallops. I say the RDP tests are failing due to some internal issue. Probably will ping you, like separately.

A

Okay, great thanks, Anna, okay, moving right along in the world. It's crappy us internet time line for next week is we're gonna, start ramping up marketing activities and documentation. We need to start looking more deeply at the issues that are collecting and CI signal and make sure that things that are tagged with release note equal to true are in a good shape to actually be moved to the release. Notes draft. At some point we doesn't mean identify any PRS out there that have suspicious documentation or is incomplete, so we'll be focusing on that.

A

There was some talk about a starting in preview, blog, so basically a forward-looking. Here's. What you might expect from this release thing we talked about it I, don't know, necessarily that it's something we'll do, but I figured it was worth bringing up because it's in the schedule so.

A

And see any since about next week, does anybody not know what they are doing next week.

F

Jay, Z or and I discussed about that a freezie blog, but he did such a great job, putting together that list of all the features that they're working on and what their statuses, but not pretty much served as a great preview, and then pious people had questions specifically about that. They always follow up with a human and ask them black, because there's nobody up I'll top any opinions about that. Specifically.

E

Just that you make we may want want to produce some like bare-bones briefing material based on that snapshot. Just like it I guess he horse. We were saying about the most in portent or I. Guess the features to highlight for the release.

E

B

E

Wasn't a question just a comment that yes, I guess got I didn't about feature stock might might be nice. Oh.

B

Sure yeah I get it.

A

Great yeah, I think some sort of just general documentation or blog or something even if it's short and simple is good because from a marketing perspective, we want to start generating interest in the release, and maybe you know fingers crossed somebody would want to download the one of the alphas and see what they could do with it and experiment. That's functionality, so I know I'm dreaming there, but that's what I would like to see.

A

F

D

Will probably want debriding something like that anyway for my day job, so we could probably do double duty.

A

A

A

All right moving Natasha did you have anything to add, did you did you get that.

F

Ya got that wolf um and and see when to post that we're meeting with some later this week to talk about webinars anyway, and then we're meeting with your tomorrow to really go through the feature. So we can start on the actual release outline so I think this week is good timing for all of that. Okay,.

A

Fantastic all right. Moving along, we have just a quick rundown on the numbers, so our metrics review looks green. Basically, most things are unchanged where things have changed. They're minimally changed no showstopper type, emerging PRS or our issues on the board. Most of the sake issue counts are pretty stable.

A

Does anybody wanna? Does anybody have updates for any of the sections below so starting with branch updates and moving through so Caleb? Anything you want to either nope okay.

A

Send anything on testing for anything like that.

G

Not I'm aware I think best. Color sightseeing is fixed, so that should be good.

G

A

All right documentation, we touched on release, notes not really much there. So that's pretty much it anybody have anything else. They want to discuss or announce.

C

I'll just get bit of ducks update, I am getting I I hadn't done this last week, and only this morning, bits in place for the 1.10 really sucks, so I'll be sending an email to the SIG's. Probably later today, after I've gotten all the bits in place, we changed the PR template. We make sure the branch is available. We make sure that we can stay. Aging's range specific and there's a few fiddly bits there that I am still fiddling with, but that will definitely be done by the end of the day and I'm.

C

Also working with that core dayson, who was there really dead, ducks meister for 1.9 to get the on the docs documentation for the release process, updated I, know you reviewed that VRE and I'm gonna, add I'm gonna fix per your comments and um and update and then get that merged, and then we will iterate through getting it getting keeping it updated. Throughout this release,.

B

Great things transferred to me.

A

Alright anything I.

B

Have a brief update, yeah I have a brief update from my side. I won't be available next Monday during the Macan hours, because I'll be flying back from FOSDEM this same time. If you're going to spend your next weekend in bail for Stan, so I'll be happy to meet. Someone of you I know that most of you are in the United States I'm not planning to make it to Belgium, but the nutrients I'm there.

A

Okay, great thing see or just make sure that any updates are in the document before you, you know before you or when you're able to actually thank you.

A

Okay, any final announcements before we adjourn.

A

Okay, great everybody. Thank you. So much for your time and I will see you next week.