14:10:09 <ttx> #startmeeting releaseteam
14:10:10 <openstack> Meeting started Fri Sep 16 14:10:09 2016 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:10:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:10:14 <openstack> The meeting name has been set to 'releaseteam'
14:10:16 <ttx> Should be a short one
14:10:27 <dims> yep
14:10:35 * ttx looks for an agenda
14:10:50 <ttx> no agenda, perfect
14:10:54 <ttx> #topic RC1 status
14:11:05 <ttx> Looking at the tracking dashboard...
14:11:09 <ttx> We are still missing a few RC1s
14:11:27 <ttx> On the milestone-driven side...
14:11:34 <dims> the netaddr and oslo.db situation seems to be resolved as well
14:11:51 <ttx> barbican, congress, designate, neutron, searchlight are missing
14:12:00 <ttx> neutron is expected asap
14:12:08 <dims> right
14:12:24 <ttx> same for designate
14:12:36 <dims> ttx : pending pings to the ptl(s) right? so we just wait
14:12:48 <ttx> I pinged redrobot and TravT
14:13:02 <ttx> thinrichs wans't around this morning
14:13:07 <ttx> so I haven't pinged him
14:13:33 <ttx> We'll likely want to branch requirements early next week, so would be good to have them in
14:13:46 <dims> k i see the notes in dashboard
14:14:03 <ttx> On the intermediary side, we have at least one fallback release for everything now
14:14:04 <dims> +1 to branch requirements early next week
14:14:14 <ttx> which is good
14:14:47 <ttx> TripleO will likely want to do a RC1 too, as do ceilometer
14:15:14 <dims> for those intermediary which are missing RC1 column entries, we need to ping PTL(s)? or are we just going to branch
14:15:19 <ttx> The trailing stuff I don't care that much about for the time being
14:15:27 <dims> right
14:15:32 <ttx> FTR I didn't cut a stable branch for Kolla
14:15:36 <ttx> since I wasn't sure they wanted that
14:15:54 <ttx> (it's RC1 but it's trailing)
14:16:07 <dims> gotcha
14:16:15 <ttx> That is about all I have on the RC1 front
14:16:27 <ttx> I think you should keep processing them today
14:16:35 <dims> k, i'll process whatever comes in today
14:16:37 <ttx> cut stable branches for milestone-driven stuff
14:16:42 <ttx> + announce for milestone-driven stuff
14:16:52 <ttx> (intermediary ones get auto-announced)
14:17:14 <dims> right, thanks for reminding the distinction
14:18:14 <ttx> doug has been using "rc1s" also for "potentially-final intermediary-releases that we can cut stable branches for" which I find a bit confusing
14:18:37 <ttx> I prefer to only call RC1s things that bear that version number
14:18:52 <dims> k we don't have to decide that now anyway
14:18:54 <dims> right
14:19:15 <ttx> nah, just explaining where the confusion between my words and his might come from
14:19:22 <ttx> dims: anything else ?
14:19:26 <ttx> (on that topic)
14:19:29 <dims> that's it ttx
14:19:32 <ttx> #topic Open discussion
14:19:37 <ttx> Anything else, anyone ?
14:19:46 <dims> nope, am all good
14:20:18 <ttx> alright then
14:20:24 <ttx> #endmeeting