15:01:30 <ttx> #startmeeting releaseteam
15:01:31 <openstack> Meeting started Fri Aug 18 15:01:30 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:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:34 <openstack> The meeting name has been set to 'releaseteam'
15:01:40 <ttx> Ping list: dims, fungi, tonyb, stevemar, lbragstad, smcginnis
15:01:48 <lbragstad> o/
15:02:14 <smcginnis> o/
15:02:54 <ttx> #link https://etherpad.openstack.org/p/pike-relmgt-tracking
15:03:01 <ttx> Agenda for the meeting on R-2 week
15:03:09 <ttx> #topic Review stragglers
15:03:50 <ttx> We still have a few projects that didn't do any Pike intermediary release (and therefore no stable/pike branch yet)
15:03:56 <ttx> panko, ceilometer
15:04:01 <ttx> magnum[-ui]
15:04:05 <ttx> tacker
15:04:09 <ttx> senlin-dashboard
15:04:42 <ttx> If we don't have anything next week, we'll have to decide between removing the project from Pike, or cutting a release arbitrarily somewhere
15:04:46 <ttx> Both bad outcomes
15:04:59 <smcginnis> Was just going to ask what our fallback plan was.
15:05:11 <ttx> So would be great to reach out to those teams early next week and get them to do their homework
15:05:20 <ttx> You can point them to the latest release countdown email:
15:05:36 <ttx> http://lists.openstack.org/pipermail/openstack-dev/2017-August/121266.html
15:05:40 <smcginnis> I'll try to ping some folks today.
15:05:43 <ttx> It has instructions from everyone
15:05:50 * dims sorry i am stepping out for "final day of camp event" for the boys
15:06:01 <ttx> We also have a few deliverables missing stable/pike branches
15:06:27 <ttx> i.e. they have a Pike release, but it's a bit old, or they just haven't requested stable/pike from it
15:06:28 <smcginnis> dims: Fun
15:06:31 <ttx> aodh
15:06:35 <ttx> instack-undercloud
15:06:37 <ttx> kuryr-kubernetes
15:06:41 <ttx> manila-ui
15:06:44 <ttx> neutron-fwaas-dashboard
15:06:47 <ttx> swift
15:06:50 <ttx> tacker-horizon
15:07:10 <ttx> Some of those (swift) will likely release next week and ask stable/pike from that
15:07:23 <ttx> Some others are probably oversight (like the dashboard things)
15:07:38 <notmyname> ttx: swift is planning on submitting a tag for a new pike release (final) early next week
15:07:43 <ttx> If you don't get anything next week, we'll cut stable/pike from the last available Pike release
15:08:01 <ttx> notmyname: ack, that's what I was suspecting
15:08:35 <amotoki> ttx: i am taking care of neutron-fwaas-dashboard (with cycle-with-intermediary) and will plan to cut stable/pike next week. I though it is okay when following the release schedule
15:08:45 <amotoki> *thought*
15:09:00 <amotoki> is it better to cut it earlier?
15:09:00 <ttx> amotoki: yes it is, it's just a bit close to the deadline :)
15:09:09 <ttx> Well, you never know what will happen
15:09:23 <ttx> so the sooner you do it, the less stress for everyone
15:09:43 <ttx> Anyway, those are the projects to keep an eye on next week and encourage
15:09:51 <amotoki> ttx: thanks for clarification. i am waiting some feature but will cut it first.
15:10:11 <ttx> We'll have a bunch of RC2s as cycle-with-milestones projects catch the latest translations stuff and refresh their RCs too
15:10:27 <ttx> smcginnis: questions on that ?
15:10:34 <smcginnis> ttx: Think I got it.
15:10:50 <ttx> you and dims will have to process those as on Mon-Tue neither dhellmann nor myself will be around
15:11:02 <smcginnis> ack
15:11:07 <ttx> #topic Priority reviews
15:11:12 <ttx> I have https://review.openstack.org/494556
15:11:22 <ttx> which is a merge conflict generator
15:11:32 <smcginnis> :)
15:11:35 <ttx> so would be great to get it in asap
15:11:43 <smcginnis> ttx: Should I just push it?
15:11:55 <smcginnis> Since we're the only ones around at the moment.
15:12:03 <ttx> fwiw when it resolved the conflict for cinder it did add a second line about release-notes
15:12:15 <ttx> so don't trust it to do the right thing
15:12:28 <smcginnis> Gotta wonder about merge logic some times.
15:12:29 <ttx> smcginnis: yah, I would be fine with that
15:12:35 <smcginnis> ttx: Done
15:12:44 <ttx> git merge logic handles code better than yaml
15:13:02 <ttx> Any other priority review ?
15:13:18 <smcginnis> None that I'm aware of.
15:13:43 <ttx> #topic Assign R-1 week tasks
15:14:05 <ttx> So let's review next week tasks and see if there are questions
15:14:17 <ttx> - cycle-with-milestones projects: when all translations and bug fixes are merged for a project, prepare a new release candidate.
15:14:25 <ttx> That was communicated in the countdown email
15:14:39 <ttx> - Ensure that the final release candidate for each project is prepared at least one week before the final release date.
15:14:46 <ttx> That's also communicated in the email
15:15:14 <ttx> The next one is no longer necessary
15:15:34 <ttx> - On the morning of the deadline...
15:15:43 <ttx> That's mostly catching last-minute stragglers,
15:16:20 <smcginnis> Line 612 should say stable/pike, right?
15:16:34 <ttx> yes
15:16:47 <ttx> The "propose-final-releases" steps are probably early R+0 material anyway
15:17:05 <ttx> Probably a topic for next week meeting
15:17:42 <ttx> The week before final release test I would leave to dhellmann
15:18:11 <ttx> smcginnis: so not that much to cover
15:18:35 <smcginnis> ttx: Yeah, doesn't look too bad.
15:18:47 <ttx> For the countdown email, look at what Doug sent for that week last time, shoudl be a good starting point
15:19:19 <ttx> #topic Volunteers to cover meeting/email next week
15:19:25 <ttx> So I'll be off for all of next week
15:19:26 <smcginnis> I'm happy there are a lot of good existing examples for things with this. ;)
15:19:33 <ttx> smcginnis volunteered to cover for me
15:19:44 <ttx> Thanks!
15:19:50 <ttx> That is all I had on the docket
15:19:53 <ttx> Questions ?
15:20:11 <lbragstad> nothing from me :)
15:20:13 <smcginnis> Nope, I think I've got everything I need.
15:21:10 <ttx> alright then
15:21:13 <smcginnis> lbragstad: There was the one patch for keystone that was in question. Did that get resolved?
15:21:28 <smcginnis> The mutual auth or something like that.
15:21:41 <lbragstad> oh - yeah that was for a kerberos plugin
15:21:54 <lbragstad> https://review.openstack.org/#/c/492529/
15:22:36 <lbragstad> i need to parse tonyb's comment
15:22:55 <smcginnis> lbragstad: OK. Just saw comments on there and I know it's running out of time.
15:23:30 <lbragstad> tonyb's comments are clear - i'll ask the proposer to follow up
15:23:34 <ttx> grey area. But probably better to sneak it in now than after release
15:23:44 <lbragstad> and see if he can address those comments
15:23:51 <ttx> so if lbragstad wants the fix in, the sooner the better
15:24:43 <lbragstad> i'll see if i can get the author to weigh in on tonyb's comments
15:25:15 <ttx> alright, let's close and continue on the channel
15:25:18 <ttx> #endmeeting