15:01:43 <ttx> #startmeeting releaseteam
15:01:44 <openstack> 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 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:47 <openstack> The meeting name has been set to 'releaseteam'
15:02:01 <ttx> Meeting agenda on R-4 week at:
15:02:10 <ttx> #link https://etherpad.openstack.org/p/pike-relmgt-tracking
15:02:26 <ttx> #topic Open library freeze exceptions
15:02:38 * ttx loads the release reviews list
15:02:46 <dhellmann> that list seems to finally be down to 0
15:02:49 <ttx> yay
15:02:53 <dims> o/
15:03:04 <ttx> maybe time to abandon the last 4
15:03:07 <dims> y shipped glance_store last night 9 pm
15:03:12 <ttx> then it will REALLY be clean
15:03:33 <ttx> #topic Requirements FFE (to be completed before RC1s can roll)
15:03:33 <dhellmann> last 4?
15:03:57 <ttx> dhellmann: ah sorry, the four that still appear on my dash
15:04:06 <ttx> which are against reno and tooling
15:04:13 <dhellmann> ah
15:04:28 <ttx> stalled changes
15:04:31 <ttx> anyway
15:04:52 <ttx> I noted two open reqs changes earlier
15:04:57 * ttx refreshes
15:05:37 <ttx> appears that paunch got in and glance-store on its way
15:05:52 <ttx> https://review.openstack.org/#/c/490870/ was just added
15:07:14 * smcginnis rushes in late
15:07:27 <ttx> OK -2ed and commented
15:07:57 <ttx> feels like once the glance-store one merges we can start accepting RC1, so it's good timing
15:08:21 <dhellmann> ++
15:08:37 <ttx> #topic Other fires
15:08:47 <ttx> Anything else on the release status front ?
15:08:54 <smcginnis> None that I'm aware of.
15:09:22 <dhellmann> 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 <dims> dhellmann : was there something about monasca?
15:09:27 <dhellmann> not really a fire, but a status
15:09:39 <dhellmann> they wanted a requirements bump for the client, let me find that
15:10:01 <dhellmann> that landed already: https://review.openstack.org/489173
15:10:27 <ttx> ok
15:10:35 <dims> cool
15:10:39 <ttx> So let's look at next week
15:10:45 <ttx> #topic Assign tasks for next week
15:10:59 <ttx> Please see the list of tasks under R-3
15:11:18 <ttx> 1- ask questions if you don't understand them
15:11:32 <ttx> 2- if you'd like to volunteer to cover (some) of them that would be great
15:12:32 <dhellmann> we usually wait for the 6-7 older projects to branch and count that as the "minimum" set
15:12:37 <dhellmann> the stuff installed by default, I guess?
15:13:07 <ttx> damn silly etherpad
15:13:24 <dhellmann> what, 0 is a perfectly cromulent number
15:13:43 <ttx> same person should probably take the whole devstack/grenade taskset
15:13:53 <dims> i can help with the devstack branch and grenade one
15:15:08 <smcginnis> I can take whichever ones need attention after that.
15:15:24 <fungi> 0 is, however, not very embiggened
15:16:01 <ttx> It's tricky to split since it's sequential
15:16:17 <ttx> Oh well
15:16:33 <dhellmann> we can stage a bunch of these changes and use depends-on though
15:16:40 <smcginnis> ++
15:18:14 <smcginnis> Do we need to contact someone on the translations team for the Zanata piece?
15:18:30 <smcginnis> Or just trust that they will take care of that?
15:18:41 <ttx> 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 <smcginnis> Works for me.
15:19:09 <ttx> It's not /a lot/ of work, but it will have to be done in a short period of time
15:19:22 <dhellmann> smcginnis : in the past AJaeger just took care of it, but we may want to notify the PTL
15:19:30 <smcginnis> ack
15:19:33 <ttx> once things are ready, hopefully by end of week
15:19:36 <dhellmann> yeah, this is basically all stuff to do next thursday and friday
15:19:41 <ttx> more likely start of next
15:19:47 <dhellmann> yeah
15:19:56 * dhellmann notes that he is on PTO 14-18 AUg
15:20:11 <smcginnis> 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 <ttx> 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 <dhellmann> 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 <dhellmann> ttx: that sounds like a good approach
15:21:04 <dims> i'll be around all week
15:21:09 <ttx> smcginnis: well, given that dhellmann and I are taking days/weeks the next weeks, consider yourself free to miss
15:21:11 <smcginnis> dhellmann: Yeah, this seems like the important bits I would want some time with.
15:21:16 <dhellmann> we might want to give infra a heads up that we'll have some patches we need them to approve
15:21:29 <ttx> I mean, we'll need you and dims up on R-2 and R-1 weeks
15:21:32 <smcginnis> ttx: I'll be here as much as possible.
15:21:45 <smcginnis> Yep, no worries.
15:21:51 <dhellmann> 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 <ttx> so I'm fine being extra-present on R-3 to compensate for such a bad vacation timing
15:22:01 <dims> yep ttx
15:22:43 <ttx> #topic Open discussion
15:22:46 <ttx> Anything else ?
15:22:50 <ttx> Oh, PTG
15:22:55 <dims> Any infra changes in the next 2 weeks?
15:23:14 <ttx> we'll likely want to start preparing
15:23:21 <smcginnis> Re: PTG - what is our room situation for that?
15:23:31 <fungi> no huge infra stuff in the next two weeks
15:23:33 <ttx> We have a "stable/Release management / requirements" helproom
15:23:39 <ttx> on Monday / Tuesday
15:23:56 <smcginnis> Good, thought it would be Mon-Tue but wanted to confirm that.
15:23:57 <ttx> for people to drop and ask questions / propose process changes / whatever
15:24:02 <fungi> 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 <fungi> announcements have been sent to the -dev ml about both
15:24:25 <dims> thanks fungi
15:24:33 <dhellmann> 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 <ttx> 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 <ttx> dhellmann: yes, I think we'll want to have always at least one team member present, but no need for everyone
15:25:12 <fungi> 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 <smcginnis> =2
15:25:33 * ttx will bounce between that room and the TC room
15:25:51 <smcginnis> I hope these rooms aren't too spread out. :)
15:26:14 <fungi> 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 <ttx> The trick will be to make good use of the ptgbot to signal discussions in progress
15:27:02 <smcginnis> 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 <ttx> 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 <ttx> We have two documents basically
15:27:55 <ttx> the plan and the tracking
15:28:06 <ttx> Plan is more a list of tasks we sign up to do
15:28:16 <ttx> Tracking is more the release management itself
15:28:25 <smcginnis> Got it, thanks
15:28:40 <ttx> We have a number of tasks that spilled over
15:28:44 <ttx> and a healthy backlog
15:28:55 <ttx> We need to review both and see what we should try to achieve in Queens
15:29:00 <ttx> (if anothing)
15:29:13 <ttx> Usually by end of release we realize a number of things were not working
15:29:29 <ttx> and so it's a good time to consider the changes
15:30:24 <ttx> 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 <ttx> then copy that in a queens-plan, move leftovers from the pike-plan
15:30:59 <ttx> then go over the list at PTG
15:31:24 <smcginnis> dhellmann: I see item 9 can be removed from the backlog.
15:31:27 <ttx> 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 <dhellmann> smcginnis : which section?
15:31:55 <ttx> backlog I suspect
15:31:59 <dhellmann> oh, backlog
15:32:05 <smcginnis> dhellmann: In the backlog - Fix new-release YAML spacing
15:32:14 <ttx> yay!
15:32:20 <dhellmann> sorry, yeah, I read "backlog" as "planning doc"
15:32:23 <smcginnis> One down. ;)
15:32:34 <ttx> smcginnis: you're already making a big difference!
15:32:38 <smcginnis> Hah!
15:32:52 <ttx> alright, I guess we can close the meeting
15:33:01 <ttx> unless anyone has anything ?
15:33:11 <smcginnis> No I
15:33:13 <ttx> alright then
15:33:14 <dims> have a good weekend
15:33:14 <smcginnis> *not
15:33:15 <ttx> #endmeeting