15:01:43 #startmeeting releaseteam 15:01:44 Meeting started Fri Aug 4 15:01:43 2017 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:47 The meeting name has been set to 'releaseteam' 15:02:01 Meeting agenda on R-4 week at: 15:02:10 #link https://etherpad.openstack.org/p/pike-relmgt-tracking 15:02:26 #topic Open library freeze exceptions 15:02:38 * ttx loads the release reviews list 15:02:46 that list seems to finally be down to 0 15:02:49 yay 15:02:53 o/ 15:03:04 maybe time to abandon the last 4 15:03:07 y shipped glance_store last night 9 pm 15:03:12 then it will REALLY be clean 15:03:33 #topic Requirements FFE (to be completed before RC1s can roll) 15:03:33 last 4? 15:03:57 dhellmann: ah sorry, the four that still appear on my dash 15:04:06 which are against reno and tooling 15:04:13 ah 15:04:28 stalled changes 15:04:31 anyway 15:04:52 I noted two open reqs changes earlier 15:04:57 * ttx refreshes 15:05:37 appears that paunch got in and glance-store on its way 15:05:52 https://review.openstack.org/#/c/490870/ was just added 15:07:14 * smcginnis rushes in late 15:07:27 OK -2ed and commented 15:07:57 feels like once the glance-store one merges we can start accepting RC1, so it's good timing 15:08:21 ++ 15:08:37 #topic Other fires 15:08:47 Anything else on the release status front ? 15:08:54 None that I'm aware of. 15:09:22 tonyb mentioned that there are lots of requirements updates not landed, and we still have lots of doc patches in progress, so I updated list-changes to show those for us so we can talk about any open ones when rc1 patches come in 15:09:25 dhellmann : was there something about monasca? 15:09:27 not really a fire, but a status 15:09:39 they wanted a requirements bump for the client, let me find that 15:10:01 that landed already: https://review.openstack.org/489173 15:10:27 ok 15:10:35 cool 15:10:39 So let's look at next week 15:10:45 #topic Assign tasks for next week 15:10:59 Please see the list of tasks under R-3 15:11:18 1- ask questions if you don't understand them 15:11:32 2- if you'd like to volunteer to cover (some) of them that would be great 15:12:32 we usually wait for the 6-7 older projects to branch and count that as the "minimum" set 15:12:37 the stuff installed by default, I guess? 15:13:07 damn silly etherpad 15:13:24 what, 0 is a perfectly cromulent number 15:13:43 same person should probably take the whole devstack/grenade taskset 15:13:53 i can help with the devstack branch and grenade one 15:15:08 I can take whichever ones need attention after that. 15:15:24 0 is, however, not very embiggened 15:16:01 It's tricky to split since it's sequential 15:16:17 Oh well 15:16:33 we can stage a bunch of these changes and use depends-on though 15:16:40 ++ 15:18:14 Do we need to contact someone on the translations team for the Zanata piece? 15:18:30 Or just trust that they will take care of that? 15:18:41 OK, maybe we should not assign those, just make sure to strike out stuff you did and add link to corresponding review/work 15:18:53 Works for me. 15:19:09 It's not /a lot/ of work, but it will have to be done in a short period of time 15:19:22 smcginnis : in the past AJaeger just took care of it, but we may want to notify the PTL 15:19:30 ack 15:19:33 once things are ready, hopefully by end of week 15:19:36 yeah, this is basically all stuff to do next thursday and friday 15:19:41 more likely start of next 15:19:47 yeah 15:19:56 * dhellmann notes that he is on PTO 14-18 AUg 15:20:11 Probably poor timing, but I'm travelling next week with the ops midcycle. I expect to be online most of the time though. 15:20:26 I'll set aside some extra time on Thu/Fri to cover those tasks, but it will likely be more of a hot decision who does what based on who is around on channel 15:20:49 smcginnis : this is some of the more complicated parts of the cycle process, so it would be good to include you, at least as an observer, as much as possible 15:21:03 ttx: that sounds like a good approach 15:21:04 i'll be around all week 15:21:09 smcginnis: well, given that dhellmann and I are taking days/weeks the next weeks, consider yourself free to miss 15:21:11 dhellmann: Yeah, this seems like the important bits I would want some time with. 15:21:16 we might want to give infra a heads up that we'll have some patches we need them to approve 15:21:29 I mean, we'll need you and dims up on R-2 and R-1 weeks 15:21:32 ttx: I'll be here as much as possible. 15:21:45 Yep, no worries. 15:21:51 it won't be a surprise, but coordinating will be good in case some of them are planning to be out, too 15:21:52 so I'm fine being extra-present on R-3 to compensate for such a bad vacation timing 15:22:01 yep ttx 15:22:43 #topic Open discussion 15:22:46 Anything else ? 15:22:50 Oh, PTG 15:22:55 Any infra changes in the next 2 weeks? 15:23:14 we'll likely want to start preparing 15:23:21 Re: PTG - what is our room situation for that? 15:23:31 no huge infra stuff in the next two weeks 15:23:33 We have a "stable/Release management / requirements" helproom 15:23:39 on Monday / Tuesday 15:23:56 Good, thought it would be Mon-Tue but wanted to confirm that. 15:23:57 for people to drop and ask questions / propose process changes / whatever 15:24:02 though we are preparing for the zuul v3 cut-over at the ptg and a gerrit upgrade immediately after which will require a lengthy outage 15:24:15 announcements have been sent to the -dev ml about both 15:24:25 thanks fungi 15:24:33 ttx: I will likely bounce back and forth between our room and the docs room those days. 15:24:36 * dhellmann hopes they are near each other 15:24:38 The "release team" itself will meet in some room corner some day between Wed/Thu/Fri to go over the Queens work plan 15:25:04 dhellmann: yes, I think we'll want to have always at least one team member present, but no need for everyone 15:25:12 since i plan to _not_ be the infra ptl as of a couple weeks from now, i can more easily float into release automation discussions if you need 15:25:27 =2 15:25:33 * ttx will bounce between that room and the TC room 15:25:51 I hope these rooms aren't too spread out. :) 15:26:14 yeah, i expect to be floating between infra, tc and security team discussions probably but can also be pulled into release discussions if i get a heads up and a few minutes to shift gears 15:26:39 The trick will be to make good use of the ptgbot to signal discussions in progress 15:27:02 ttx: For the "Queens work plan", is that just a matter of going through the tasks like in the pike-relmgt-trackingn and making sure the tasks and dates still line up? 15:27:43 smcginnis: no, it's actually building the list of things we want to change / develop during the cycle. Like https://etherpad.openstack.org/p/pike-relmgt-plan 15:27:51 We have two documents basically 15:27:55 the plan and the tracking 15:28:06 Plan is more a list of tasks we sign up to do 15:28:16 Tracking is more the release management itself 15:28:25 Got it, thanks 15:28:40 We have a number of tasks that spilled over 15:28:44 and a healthy backlog 15:28:55 We need to review both and see what we should try to achieve in Queens 15:29:00 (if anothing) 15:29:13 Usually by end of release we realize a number of things were not working 15:29:29 and so it's a good time to consider the changes 15:30:24 By end of release cycle it's too late to durably fix things, so we take notes, tracking the issues we need to solve next time at the end of the tracking document 15:30:50 then copy that in a queens-plan, move leftovers from the pike-plan 15:30:59 then go over the list at PTG 15:31:24 dhellmann: I see item 9 can be removed from the backlog. 15:31:27 remove things we won't do, add assignees for things we should do, mark HIGH TODO things we really need to do 15:31:45 smcginnis : which section? 15:31:55 backlog I suspect 15:31:59 oh, backlog 15:32:05 dhellmann: In the backlog - Fix new-release YAML spacing 15:32:14 yay! 15:32:20 sorry, yeah, I read "backlog" as "planning doc" 15:32:23 One down. ;) 15:32:34 smcginnis: you're already making a big difference! 15:32:38 Hah! 15:32:52 alright, I guess we can close the meeting 15:33:01 unless anyone has anything ? 15:33:11 No I 15:33:13 alright then 15:33:14 have a good weekend 15:33:14 *not 15:33:15 #endmeeting