15:00:05 <ttx> #startmeeting releaseteam
15:00:06 <openstack> Meeting started Fri Jun 23 15:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:09 <openstack> The meeting name has been set to 'releaseteam'
15:00:11 <ttx> Ping list: dhellmann, dims, fungi, tonyb, stevemar, lbragstad
15:00:20 <ttx> Agenda at:
15:00:25 <lbragstad> o/
15:00:26 <ttx> #link https://etherpad.openstack.org/p/pike-relmgt-tracking
15:00:41 <ttx> Scroll down to R-10
15:00:54 <ttx> Waiting for more people to join
15:01:06 <ttx> know fungi and dims are probably not around
15:01:16 <ttx> Same for tonyb given the hour in Australia
15:01:38 <lbragstad> probably a pretty thin group this week then
15:01:54 <ttx> yes, short agenda too
15:02:05 <ttx> I can probably address the first one
15:02:13 <ttx> #topic Mistral release model change
15:02:36 <ttx> TL;DR: was that mistral is cycle-with-milestones and yet depended upon, due to an incomplete mistral-lib
15:02:56 <ttx> which creates issues as you can't add betas or RCs in requirements.txt
15:03:22 <ttx> Plan A was to finish the work on mistral-lib, but that's a lot of work
15:03:34 <ttx> Plan B was to switch mistral to cycle-with-intermediary
15:03:41 * ttx reads the latest development in the thread
15:04:17 <ttx> Plan B had the lead but Dougal posted this morning that Plan A is probably still diable
15:04:20 <ttx> doiable
15:04:22 <ttx> doable
15:04:53 <dhellmann> o/
15:05:16 <ttx> #info So we'll be trying Plan A, see how that goes in a few weeks, and switch back to plan B in case of failure to deliver
15:05:26 <dhellmann> ++
15:05:31 * ttx adds note in the plan to remember to check for that
15:06:04 <ttx> any question/comment on that ?
15:06:30 <ttx> I'll take that as no
15:06:32 <ttx> #topic oslo.log stable/mitaka release call
15:06:52 <ttx> #link https://review.openstack.org/#/c/476016/
15:07:18 <ttx> Should we process that? If yes, should we do it now on a Friday ?
15:07:34 <dhellmann> are we running any mitaka branch tests?
15:07:45 <dhellmann> usually the reason we don't want to do things on friday is to avoid breaking ourselves
15:07:58 <ttx> I think it likely won't land in requirements
15:08:11 <ttx> if I read tonyb's comment correctly
15:08:18 <dhellmann> true. I think we should do it. I can see waiting for Monday.
15:08:40 <dhellmann> unless we've already declared the branches eol, and just haven't had time to delete them?
15:08:53 <dhellmann> I admit I lost track of that thread
15:09:01 <lbragstad> i think ^ that's the case
15:09:12 <ttx> Yes it's declared eol, hence my hesitation
15:09:15 <dhellmann> ah
15:09:25 <ttx> It's just not destroyed yet for various reasons
15:09:43 <ttx> so on one hand I'm willing to oblige gcb, but on the other that sounds a bit late
15:10:00 <dhellmann> yeah, I wonder if there was a request for this or if he was just doing housekeeping?
15:10:02 <ttx> We'll likely won't even know if we didn't break anything there
15:10:21 <ttx> eh, that sounded weird, let me tryagain
15:10:34 <ttx> We'll likely not even know if we broke something there
15:10:59 <dhellmann> seems safe enough to ask gcb for details and wait to decide, but I agree without any testing and with the branch eol, it also makes sense to say no
15:11:53 <ttx> dhellmann: I feel like he was asked for details of why he wants it already
15:12:22 <ttx> Fixes a couple of bugs, and I suspect some people will use that even if Mitaka is EOL
15:12:42 <ttx> My concern is more that (1) the branch is EOL and (2) that release won't see integration testing
15:13:10 <ttx> so it's a non-tested release, I prefer that it's done by users directly
15:14:55 <dhellmann> sure, that makes sense
15:15:16 <ttx> I'll comment, and we can make the call Monday
15:15:25 <dhellmann> sounds good
15:16:52 <ttx> ok don,e
15:16:56 <ttx> #topic Open discussion
15:17:00 <ttx> Anything else ?
15:17:09 * lbragstad shakes head
15:17:22 <dhellmann> nothing pressing from me
15:17:25 <ttx> ok then, let's get back to our Fridays
15:17:28 <ttx> #endmeeting