Kubernetes SIG Release, 5 Feb 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes 1.10 Release Burndown Meeting 20180205

Description

http://bit.ly/k8s110-burndown

A

All right everybody welcome. It is Monday February 5th 2018. This is the kubernetes 1.10 release team, burndown meeting and I'm your host chase singer DeMars. If you want to follow along with this meeting after the fact, there are notes and minutes available at bit, dot ly slash, Cates, 1, 1 0 burned down. So let's go ahead and get started with the scheduling.

B

A

We do this is week number 6 of the 12 week release cycle so today, and actually this week marks the 50% mark of the release, the the things that are going to start happening now, if you haven't been part of the release, team prior, are going to be focused a lot more on trying to ascertain the quality of the base and the branch and making sure that the what we're going to deliver to the communities community is as defect-free as possible and as well-documented and transparent as possible.

A

So those those two things have a lot of implications in terms of what the release team will be doing from here forward.

A

In terms of the branch health, we're going to be paying a lot closer attention to CI signal and part of what we'll be doing there is, we will cut the branch that we will basically fast forward to every I'm, not sure how often we fest forward right away, but I think it'll be daily um Caleb. How? How often do we run the fast forward? Is it nailing once the branches cut.

C

Things as needed.

A

C

Read a couple days, certainly: okay,.

A

So yeah, and basically once that branch is cut and we're watching it we're going to be setting up the testing infrastructure so that we have signal on how that branch is doing and being in close eye on the intent of the issues that come in and making sure that you know we're catching things as early in the process as we can, 1.8 was held up sort of at the last minute by issues that should have been known earlier and weren't so in trying to continuously improve the release process, I want to try and keep a really close eye on any Black Swan issues that might be out there.

A

So if you hear of anything or if you're in a cig meeting- and somebody raises an issue that seems like it might be really simply's for sure surface it to this group, because that'd be tremendously helpful in terms of the schedule itself, we are, we basically talked about doing a blog post about this time.

A

Sort of a forward-looking thing. I, don't think you are- is not on so Natasha.

D

Okay yeah, so we we are going to do one. We are going to do one, but it's actually going to be a little bit later in the process and it is going to be right around next week. Actually we're gonna position it as a hey, there's, betas out there. You know please help test them great.

A

Fantastic and that'll be a nice alignment because we're gonna have a beta release week, seven so betas, typically when people can get a little more serious about building and testing against the new version. So that's that's good.

A

So, just as a reminder again in the schedule, we want to keep looking at issues signal. We also want to start looking more deeply at release notes just because in the past this has been something that we almost cannot start early enough on, and so, let's just figure out what we need to do there. If there's anything that isn't being done and just could make sure that those things start getting attention.

D

I guess that's in my ballpark too, oh yeah, so I have been working on, remember who I spoke to, but we're getting that new label and we're working on the automation process. I've been speaking to Noah and we're going to start working with the intermediate release notes or for like the Alpha and the beta releases and start trying to work on getting those things so that.

A

D

A more sound foundation by the time things really going to swing in terms of deadlines.

D

We are going to start pestering the SIG's for their overall themes around around, but on March, 2nd and we're gonna really start nagging them around the night and if you don't have it in by the 14th you're going to be stuck with whatever we think.

B

Those are lines.

B

A

Great that is, and so one other thing I'm going to do- is I'm gonna send out the weekly update this week. I didn't send one out last week because there wasn't really much to say and I don't want people to basically stop paying attention anymore than they already do, but it will I'll, try and radiate some of these deadlines.

A

So I won't hit the docks deadlines yet, but I will talk about code, slash code freeze because that's coming up I think a lot faster than people actually realized. So.

A

So that's it for this week and in terms of the milestones in place, is there anything from a marketing perspective? You wanna talk about Natasha quickly,.

A

Okay, I'll sing that I don't.

E

Know sorry, Osamu, okay, I'm just gonna say we had a really great meeting with your last week, we've flushed out what some of the top line features are going to be I sent that around.

E

So if you and Caleb can give that a look, and just let us know like if there's any issues with with the outline of the blog with the five-day blog series, that would be great we're going to start doing a first draft, so everybody can start contributing and reviewing, but we just want to take a stab at a first draft and then I also created a separate document.

E

This is questions that reporters have that we want to answer because we want to be the source of truth, but it doesn't make sense for this information to be put in the actual blog, so I started that document as well. If you guys can also take a look at that and start answering any questions that you're able to I know some of these may be a little bit early, but that way we could use those to send over to reporters to include in their stories.

E

But again it doesn't make sense for it to be in the actual blog itself. Okay and.

A

Could you possibly what could you possibly put a link to that in the many minutes or send that to me just so, I have it again: I'm I was off-site last week. So no.

E

Yes, yeah happy to do that and then just in terms of the overall marketing timeline, we are right on track. So that's good great.

A

Okay, so moving along next week, we'll be cutting one of 10 beta betas. Don't follow the same release, number numerology or number Tech's on me. They start at zero, so we'll be doing beta. Zero will also be creating the release 110 bridge, which is exciting, and we begin the daily fest board and we're going to be creating the branch CI jobs. So we'll get some update on that once once that's in play, so metrics review looks good. It doesn't look like anything is spiraling out of control.

A

There was an uptick in important issues that doesn't necessarily mean anything this phase of release, but it's something that we do want to keep an eye on. Overall count was up which is pretty pretty reasonable, probably starting about week. Nine. We want to see these start trimming down so we'll be curating, those a little more closely a cig testing dashboard.

A

This looks fine that'll become important later I, unfortunately, Josh could not be with us, but he updated the list here of interesting things that he qualified as a list of issues which looks suspiciously like untracked features, so we're gonna have to figure out what that's all about. This is one of the risks of this.

B

Process and the.

A

Features process in general is that there is no strong referential integrity between the features process and what actually gets put into the release. That is improving, but it's definitely not there. So, as I have said in the past, whatever's.

B

In the release.

A

Is what's in the release, so we may have designs in of being one thing or another, but in essence, because we commit to master day what's in, there is in there. So we need to basically trying to unearth as much information about it as we can, because we don't have control over it.

A

Moving along, there are various update segments here for folks in the team. I do have a preference, it's not.

B

As important right.

A

Now, but probably starting about week, nine when we start doing three times a week, I definitely would love to have this. The owners of each part of your part of the release, updating this document ahead of time, with even just a quick blurb about where things are at. So we have something to go on so right. Now, branch health is not really there's not much to say there is there anything more to add Caleb about the stuff you're doing.

C

Nothing in Eau Claire dead right now.

A

Okay, thanks testing send anything you want to add.

F

Really think we fix our jobs so now they should be all green. mmm Nothing is broken, I think right now, yeah.

A

A

Good, that's great I got an update for marketing. Already ten bucks release notes, we got an update on okay, that is the scheduled portion of the meeting I'd like to open the floor. If anybody has anything that you'd like to bring them up or talk about before, we adjourn.

A

All right, if you think of anything that could be going better or you would like to see done differently in 1.11 or beyond, there's a link at the bottom of the release. Burndown meeting agenda that has some link to the retro doc, so store your ideas in there as they come up, and that will help make the next release even better. So with that I leave you all to have the rest of your day and have a great Monday and I will talk to you in a week or sooner thanks. Everybody thanks Jase.