15:03:08 #startmeeting releaseteam 15:03:08 Meeting started Fri Dec 16 15:03:08 2016 UTC and is due to finish in 60 minutes. The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:11 The meeting name has been set to 'releaseteam' 15:03:12 sorry for being late, folks 15:03:31 we're in the Ocata-2 milestone week, R-10 15:03:37 our agenda is in the etherpad, as usual 15:03:41 #link https://etherpad.openstack.org/p/ocata-relmgt-tracking 15:03:46 #topic milestone 2 status check 15:04:07 we had quite a few late ones, it looks like, but not so late that ttx couldn't process them earlier today 15:04:19 o/ 15:04:28 there seems to have been some confusion about who needed to handle the networking-ovn release, but that's done now 15:04:42 as far as I can tell, all of our milestone projects that are releasing this cycle have now tagged ocata-2 15:04:46 sorry. 15:05:02 o/ sorry for being late 15:05:04 russellb : np, this is why we have release liaisons 15:05:13 oh, and I was late, and forgot to 15:05:13 courtesy ping: ttx, dims, sigmavirus, tonyb, fungi, stevemar 15:05:23 o/ 15:06:00 does anyone have anything else to raise about the milestone? 15:06:24 alright, moving on 15:06:24 #topic reno / eol branch issue retrospective 15:06:44 we had some unfortunate fallout this week from deleting the stable/liberty branches 15:07:02 in retrospect it was an obvious issue, but I didn't give it any thought in advance 15:07:37 the "fix" in 1.9.0 wasn't quite as compatible with the work-around as I had hoped, but afaik everyone is now back to using the branch specifier and that's working 15:08:08 dhellmann : in terms of guidance to projects, what do we tell them to do going forward? (use -eol or not?) 15:08:17 that is, I had suggested that folks change "origin/stable/liberty" to "liberty-eol" in their sphinx files, which worked for reno 1.8.0 but did not work when we put the fix in 1.9.0 to automatically detect the eol 15:08:34 going forward they should not need to change anything, and origin/stable/liberty should work fine 15:08:44 ++ dhellmann 15:08:51 we have some good tests in the dulwich-based version on master to ensure that 15:09:34 I'll be working to get reno into shape for a 2.0.0 release early next week 15:09:59 are there any other comments for the retrospective? 15:10:44 nope 15:10:51 #topic meeting schedule for the rest of the year 15:11:16 with our meetings on fridays, I'm expecting some folks to be away on the 23rd and 30th 15:11:26 i've updated availability in etherpad dhellmann 15:11:29 should we meet? should we move to a different time? 15:11:40 (catching up in channel less formally) 15:11:45 dims: ack, thanks 15:11:53 +1 to catch up in channel 15:12:19 ok, and it looks like we'll all be away the week of 26-30 so I'll announce a release freeze during that period, too 15:12:28 i likely won't be available on the 23rd, but my presence is noncritical 15:12:47 +1 to informal catchup on channel 15:13:00 and next meeting Jan 6 15:13:11 ok, so we'll cancel meetings for the next 2 weeks, suggest that folks catch us in channel, and we'll communicate between ourselves there and on the ML 15:13:51 #topic code reviews for tools 15:14:07 we have a handful of reviews up for changes to the tools 15:14:19 now that the milestone and reno push are done, please give those some attention next week 15:14:34 does anyone have anything in particular they would like to highlight for a review? 15:15:09 dhellmann : release-tools? 15:15:39 dims : I was thinking of things like https://review.openstack.org/411530 and https://review.openstack.org/411439 15:15:58 ack. was afraid i was missing another bucket 15:16:01 I also have some early changes up to infra to move our constraints update step to its own job in https://review.openstack.org/411495 15:16:44 #topic open discussion 15:16:57 that's all I had on the agenda, does anyone want to raise any other points before we call the meeting? 15:17:06 sort of tool related, but the infra documentation for how/where to document signing keys on the release site merged, and i've (finally) marked our artifact signing spec implemented 15:17:27 yay fungi 15:17:45 dhellmann: fungi: can we ask the liaisons to sign the key? 15:17:47 great! 15:18:04 dims: anyone who wants can sign the signing keys 15:18:06 dims : good idea. do you want to write an email suggesting that they do? 15:18:29 #action dims to write email to folks to sign the keys 15:18:46 i mostly wanted to make sure we have infra root admins signing them because we're the only ones with direct access to the private key to be able to absolutely attest that it's correct 15:19:00 but anyone else who trusts it enough to add a signature is most welcome 15:19:06 makes sense 15:19:30 fungi : let me draft something and you can check verbiage before i send? 15:19:35 gladly 15:19:42 give me a heads up when you have something 15:19:44 great 15:19:56 cool, thanks to both of you 15:20:16 if there's nothing else, we can close and get ~40 minutes back 15:20:50 yes! 15:20:53 :) 15:20:59 alrighty 15:21:00 nothing on my end 15:21:00 happy weekend, everyone! 15:21:05 #endmeeting