15:02:32 <dhellmann> #startmeeting releaseteam
15:02:33 <openstack> Meeting started Fri Jun  9 15:02:32 2017 UTC and is due to finish in 60 minutes.  The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:36 <openstack> The meeting name has been set to 'releaseteam'
15:02:45 <dhellmann> courtesy ping: ttx, dims, fungi
15:03:15 <dhellmann> courtesy ping: tonyb, stevemar, lbragstad
15:03:21 <fungi> mmmeetings
15:03:32 <dhellmann> #link agenda https://etherpad.openstack.org/p/pike-relmgt-tracking
15:03:46 <dhellmann> this is week R-12
15:04:12 <dhellmann> and yesterday was the pike-2 deadline
15:04:40 <dhellmann> #topic follow-up actions for teams missing the milestone
15:04:57 <dhellmann> we had quite a few teams miss this time
15:05:03 <dhellmann> I sent email with the details
15:05:08 <dhellmann> #link http://lists.openstack.org/pipermail/openstack-dev/2017-June/118140.html
15:05:29 <dhellmann> congress has a review up, but they're missing a release job in project-config
15:06:15 <dhellmann> I don't see any response about the others yet, but it hasn't been long today since that email
15:06:47 <dhellmann> the main teams seem to be barbican, designate, neutron, and zaqar
15:07:03 <fungi> do you exclude any which haven't had any changes on master since the last release?
15:07:08 <dhellmann> I guess I can follow up with them after this meeting
15:07:28 <dhellmann> no, that would be good to check
15:07:43 <fungi> i thought that might be the situation with requestsexceptions, but there are a couple (minor) changes to it since the last tag including one requirements update
15:08:24 <dhellmann> oh, right, there's a separate list for the libraries
15:08:25 <dhellmann> #link http://lists.openstack.org/pipermail/openstack-dev/2017-June/118146.html
15:08:28 <fungi> just wondering whether it makes sense to insist on new releases for a tool or lib which hasn't actually needed any updating over the course of the cycle, though i guess that's an unusual corner case
15:08:41 <dhellmann> those have had no pike releases at all (the other list were service projects with no b2 release)
15:08:50 <dims> dhellmann : stuck with something else, if there's things i can do, please let me know (will check back later)
15:08:55 <dhellmann> dims : ack, thanks
15:09:17 <dhellmann> fungi : at this point I think it's mostly about making sure needed releases are done. If the feedback is that there were no changes, that's ok
15:09:37 <dhellmann> I do know some of those libraries have requirements updates and the ocata versions are causing trouble for packagers in at least one case
15:09:59 <dhellmann> #link unreleased changes in libraries http://paste.openstack.org/show/612133/
15:10:22 <fungi> dhellmann: yep, i agree it's probably uncommon enough to just handle as an exception when it comes up
15:10:56 <dhellmann> this was the only topic we had on the agenda to cover today
15:11:18 <dhellmann> it seems like the next action is just to follow up with those PTLs
15:11:30 <dhellmann> I'll do that today
15:11:46 <dhellmann> and then maybe ttx wants to remind folks that if they miss 2 milestones we don't generally want to include them in the release
15:12:26 <dhellmann> #topic open discussion
15:12:44 <dhellmann> does anyone else have anything that needs to be raised today?
15:13:37 <fungi> hopefully the unanticipated infra hiccups (especially misconfigured third-party ci systems beating gerrit to a pulp) didn't negatively impact the release activities around the milestone
15:13:50 * lbragstad walks in late
15:14:22 <dhellmann> fungi : I wonder if that contributed to some teams being late? We try to remind them at this point they shouldn't wait unless something is completely broken. This isn't an RC.
15:14:55 <fungi> i was mostly worried it might result in broken tarballs/tags
15:15:15 <dhellmann> fungi : if you could work with the congress team on that release job, that would unblock them. https://review.openstack.org/472467
15:15:35 <dhellmann> ah, good point. I haven't heard any complaints, or noticed any job failures
15:15:57 <fungi> dhellmann: thanks for pointing out 472467, i'll get them a link to the explicit instructions
15:16:18 <dhellmann> great, thanks
15:16:28 <dhellmann> ok, I think that covers everything for today
15:16:46 <dhellmann> I'll be in #openstack-release if anything else does come up
15:16:52 <dhellmann> thanks, everyone!
15:17:01 <dhellmann> #endmeeting