Kubernetes SIG Release, 13 May 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: k8s 1.15 Release Team Meeting 20190513

Description

Info: http://bit.ly/k8s115 Calendar: http://bit.ly/k8s115cal Team: http://bit.ly/115-releaseteam Enhancements: http://bit.ly/k8s115-enhancements Retro: http://bit.ly/115-retro Handbooks: https://git.k8s.io/sig-release/releas... Slack: #sig-release on kubernetes.slack.com Mailing List: kubernetes-release-team@ (the team) kubernetes-sig-release@ (the sig) Youtube Playlist: https://bit.ly/k8s-sig-release-videos

A

Alpha beta and stable feature sets from last week, so I figured. This is probably gonna, be one of the final weeks. Actually probably next week, probably won't move you much happening with what cute con, but when we get back from Q Khan, it's gonna be the next push, starting.

A

That Monday is actually starting to seeing a lot of these issue, honors, making sure that we have some cake, a PRS, that we can start tracking and that's when we're gonna know if things are really gonna start slipping past the code freeze date, but for now this is that's what we got.

B

Great thanks Kendrick any questions for enhancements.

B

All right, if not, we can move on to CI signal.

C

Lower one hope everyone had a fantastic weekend now see a signal. A kubernetes is healthy, it must have a mustard walk in. There is, as far as I know, there's nothing bad on it. There are a couple jobs. Joseph, like you know, master blocking with nothing too serious. Some previous is some previous failures and our are clearing a clear enough now master in forming a it hasn't changed much since it is since the last couple of weeks. Some of the persistent failures are due to conformance tests from a base, fear and OpenStack.

C

As far as I know, people are looking at, a people are looking at them. Some work is getting beaned under besides that six color well, lady, has a couple. A has had a couple issues and that's that's causing, but that's custom, one of the one of the jobs to fail put there. They are looking at it a little work, the other.

C

The only couple things that we need to look at is the GC GC, a new master grade cluster, a lot of a lot of the sick storage jobs have been failing and we so we just need to look into them and see if they've been for what recently been fairly a see which ones need to be labeled as flakes for system failures. They only persistent failure that we've found so far is ciq, Marysville and we'll investigate.

C

We investigate that further now, a that one that one just appear a couple that one just appear a couple days ago and only how much of a story there, but other than that. Any questions comments that you all have.

B

Doesn't sound like there any questions for CI signal, so then we can move on to bug triage.

B

If I don't think, I seem that close, but if anyone on his team is on to give an update for bug, triage I can.

D

Do a quick update, hey to the car one of the shadows, so Nicholas built out a spreadsheet tracking, pertinent issues that are related to this release related to enhancements, we're just tracking and following those issues as we go through the week here, no real new reports for our team at this point still kind of in the waiting pace. That's it.

B

We can move on to a test. Infra, hey.

E

We had a nice week, we had about 149 peers merged this week and total number of pr's worse from the beginning of the release. It's 650. We had no major issues. Brow is running fine, except for a glitch and get from the github site, but everything is fine from thanks.

E

Many questions.

E

Okay, thank you. Well,.

B

We can move over to Docs hi.

F

So on the side of dogs, we don't have nothing much. The only thing we're doing right now is to in people who own those issue own those investment to start I mean to know if they they need dogs and update the sheets.

F

So we basically doing that right now and for those who have those those enhancement that need looks, we invited them to start opening here that draft PR. So that again is just talking there.

B

Any questions for dogs.

B

Okay, we can go over to release notes, idea.

G

So let say, updated the release notes draft for this week, which is available in the agenda. Then we move the release, notes repository to kubernetes, 6 /, release notes and we will continue our development there and we talked at version 1 for kubernetes 1.15, and I just have to remind you that you can fill out our survey, which is also linked in the agenda. It's the same from the last week and we will evaluate the results soon and that's it from our side.

B

Any questions for release notes.

B

Okay, we can go into cons.

B

There are no questions for comms. We can go over to release branch management.

H

So sure it's busy with finals I will speak for her tomorrow we are going to cut the beta zero this time it it will be done by me. So if you are, you have any brokers, any comments feel free to wisdom.

H

It will be a few hours earlier than before. I think because I'm going to do it in my afternoon, yeah, that's all.

B

Yeah yeah, if you have any problems or need any help with that branch, cut, feel free to ping me on slack. My hours should have much earlier than normal since I'm in England. Right now, oh.

H

Okay, thank you.

B

Any other questions for release branch management.

B

All right um for em, right, asleep Josh is not able to be with us, but has no news to report. So if you have any questions for Josh, hang him on slack and then going into release lead update. So the next upcoming milestones that we have. As already mentioned, we have the 150 note branch cut tomorrow and the beta0 release tomorrow and then on. Thursday we'll have the 115 jobs created in the 111 jobs will be removed.

B

Next week is cube con. We have no major milestones during coop con, just because I assumed everyone is gonna want to everyone. Who's there is gonna want to enjoy their week and not have to worry about doing any major work. So everyone enjoy week, seven and then week eight we're gonna start burning down um supposed to start on Monday May 27th, but given Monday May 27th is Memorial Day in the US I'm kind of guessing attendance might be slim.

B

So if we were to cancel the Monday its first day of burn down and start burned down that Tuesday on the 28th, I guess I would actually be the 29th because we're doing the Monday Wednesday Friday burn down. Does anyone see any major concerns with that.

B

Yeah I'm hearing nothing so I'll probably also send an email to get lazy consent, consensus from the release team, but I figure. The change from Monday to wednesday is not going to be much and most the us folks probably do not want to hop on a call either early morning or midday late day if they're on holiday.

B

So next week for coop Connie you we have a face-to-face session if you're gonna be there Monday morning at 10:00 a.m. if you're gonna be at the contributor summit. Please stop by. If you have the time, we're also likely going to do a team lunch one day, I think from the survey that Tuesday was the winner. Well, technically, Wednesday was the winner, but it would flicked with the diversity plunge that I'm not sure if folks would rather attend the diversity lunch, so I'm gonna try to punt it to Tuesday.

B

I know that the conference provides food. So my suggestion for the lunch is, we can get the conference provided food and then try to find a room. I have never been to a coop con. So someone tell me if that's an absolutely crazy idea, we should try to go off-site I.

E

Think we used conference food in the last meetings so.

B

All right, then, I might try to figure out. If there's anyone around you can help help me secure a meeting space for us so TBD on where this lunch will be but plan for it to be somewhere in the conference area.

D

So confirming that meeting stuff really quick, is that correct that Monday, the 27th, we're going to cancel and burn down we'll resume on the 29th? Is that right? Yes,.

B

Well, let me let me update this.

B

B

Cool Thank, You Jorge I'd be awesome, so.

B

Yeah everyone get excited for kubb Khan, also, if you're from the US be really excited, because the exchange rate is particularly great, two euros right now, I think it's like one. U.S. dollar equals one point two euros.

B

So if you are like me and like to go shopping in Europe, this is the prime time.

B

Next item the release- retro dock I- haven't been talking about it too much in these meetings, um but realize I should probably do just like it's like shout that if you have any feedback on this release process so far make sure to drop that in the release retro dock that we have so we can make sure to talk about it at the end of the cycle, good or bad. Any changes you might want to propose for an exercycle feel free to capture them.

B

There rotors are a super important process of any release, so we can all reflect on what's going well and what's not gone well and what we might want to change for 116. So, please feel free to add things as they come up. um Yeah and.

B

Lastly, an FYI I'm gonna, be in a man for the next two weeks. I posted this in slack as well, should be reachable, but just be mindful that, like GMT evenings are usually midday PST. So if you notice me being slower to respond or responding the following day, that's probably why we'll be back in New York after Memorial weekend, so but on the flip side of your Annamayya and need to reach me feel free to bother me at a normal working hour for yourself and.

B

Yeah, that's all for my update. So if there's no questions for me, we can go into the release project board.

B

All right so last week when Stephen joined us he'd mentioned he wants to Wow I, put the wrong Lincoln. Sorry, everyone ignore that actual link. Let me dig up the right project for link. From last week, um yeah Stephen had mentioned. He wanted the release team to start looking through the team project board to see what different items from this we could start checking off or people could start helping to pick up so.

B

It would be helpful. I can share my screen, but that'd be helpful for everyone.

B

C

B

Just see a silences that you've started screen tearing, but there's nothing.

B

B

Yeah, so looking through the project board in the backlog, are there any items that folks on of this group are already looking at or working on, that they'd like to give updates time.

B

um I think I see something in the backlog area around we'll revisit release tracking issues that has Hannes tagged on it.

I

Wait: what is this something that you're breaking out, which one now sorry.

B

Revisit release tracking issues number four to five.

I

See why is that? I.

B

Can drop a link to it and shot.

I

Let me see if tracking.

I

Well, let me think what happened here. Parts of the thing have been done.

I

Yeah parts of this have been implemented. Other parts have not been implemented, I'm, currently not actively working on that, but I think Jarrell is handling at least a couple of things specifically about the mail. Sending I will check with her and and give an update on this on this issue.

B

Sounds good if you know, if any of this before the 115 release, let me know yeah.

I

Well, it's the the old story that part of the release stuff is still owned by Google kinda and we need to make or push everything into C and C F stuff, and by doing so we can also think about the mail sending and all that business. So it long story short. If it does not happen for 115, it's not a big deal. We will just rely on the Googler still and on the infrastructure there, but we should of course fix that.

B

B

See one of these is my name on it that says all RT role. Handbooks should have participation info, but I think Josh opened. So through all the leads who are on this call, let's make sure all of the rural handbooks have information for what your role means. If it doesn't already I think I've seen a couple PRS going in to update some of them so as needed to keep those coming.

E

So what difference between two two and background?

E

B

A great question for possibly Steven that I can he's not on today, so I can try to forward that to him and get a better understanding of when these items can move through the little board. Here.

B

Okay, any other updates on any of these items in this release project board.

B

Anyone is actively working on so.

E

We're working on the testing for a handbook but as the progress is made, I'll modem across columns.

B

Yeah, if there are no other updates for people on this board, as a note, maybe possibly next week during coop con, we'll also look at it again.

B

So a note to e be prepared to possibly be asked about some of these cards, and if you have any questions around using this board, we can try to talk about it in this. Had the hashtag sig release lock channel, maybe get some information from Stephen who I think created a ton using it.

B

And if you see items on this board, that particularly interest will feel free to jump in and help where you have time or interest.

B

Any questions from anyone on the call or anything else anyone wants to talk about today.

B

All right, then, I think I can give everyone almost 30 minutes of their Monday back. Everyone.