20:00:22 #startmeeting HorizonDrivers 20:00:23 Meeting started Wed Feb 3 20:00:22 2016 UTC and is due to finish in 60 minutes. The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:26 The meeting name has been set to 'horizondrivers' 20:00:30 o/ 20:01:19 o/ 20:02:15 General stuff 20:02:26 Mitaka-3 is in 1 month 20:02:29 March 3 20:03:11 what dpes the Mitaka-3 line mean to us? 20:03:28 (I meant to ask last night, got distracted) 20:03:35 I should probably cover that 20:04:03 Most projects in OpenStack observe a couple of freezes prior to M-3 20:05:10 The is a Feature Proposal Freeze (FPF) and a Feature Freeze (FF) 20:05:42 FPF would be the last point you could get a blueprint/spec accepted for the release 20:05:53 for most projects that was long ago 20:06:11 0/ 20:06:20 Horizon tends to be a little more reactive based on late coming features in other services 20:06:27 yep 20:06:30 Next is FF 20:07:32 for most projects that is around the 3 milestone, maybe a a week before 20:07:48 that is last chance to land new features 20:08:02 to to really panic about actually getting those new interfaces in then :-) 20:08:07 time to 20:08:39 we tend to have a couple of FFEs (Feature Freeze Exceptions) where we land some remaining items between M-3 and RC1 20:08:46 we try to keep that list short 20:08:52 to stabilize 20:09:14 Then after M-3 we should really be in bug fix mode 20:09:19 and get to RC-1 20:09:36 once there only high or greater bugs should be addressed 20:09:50 but with RC-1 master will become Newton 20:10:12 but between M-3 and RC-1 master is essentially locked to new features 20:10:23 david-lyle, do new integration tests qualify as new features? 20:10:40 tsufiev: I'll take tests anytime 20:10:44 up to RC-1 20:10:46 okay 20:10:53 tests and bugfixes are in the same boat 20:10:59 nice :) 20:12:03 so that's what all those things mean 20:12:14 thanks david-lyle 20:12:32 in the spirit of things constantly in flux, the release schedule is now posted here http://docs.openstack.org/releases/mitaka/schedule.html 20:13:13 the other two interesting points for the release are translation and library release freeze 20:13:38 for horizon we accept new strings until RC-1 and then have an RC-2 to merge translations 20:14:36 For library freeze, we shouldn't be releasing d-o-a or the xstatic libraries past the week of Feb 22 20:15:18 but yes, for priority features they should be landing soon 20:15:34 knowing the gate will be a total mess close to the milestone 20:15:59 especially given the reduced capacity 20:16:11 ok, release questions ? 20:17:10 I think I'm good 20:17:22 er, no questions, that is ;-) 20:17:45 Other general item is Midcycle Sprint in Feb 23-24 20:18:08 no other prodding will be applied :) 20:18:27 There are no items on the agenda 20:19:23 Is anyone here to advocate for a blueprint? otherwise I would rather wait on reviewing others given we're in the throws of M-3 20:20:09 does docs have a deadline? or is that accepted as it comes? 20:20:27 tqtran: ah, docs, tests and bugs all RC-1 20:20:34 ok 20:21:02 #topic Open Discussion 20:21:25 did anyone have any items for discussion? 20:22:02 only that i just realized that we'll be doing end of cycle reviews / etc at "mid-cycle" and the gate will be smashed. 20:22:05 oh well 20:22:44 same fun as last time, we'll manage 20:22:47 we'll prioritize and if things are approved and not landed, we can open FFEs if we think they are warranted 20:23:01 sounds good. 20:24:18 with the meeting this morning, seems like we've covered most items. 20:24:32 I propose cutting this short and letting people do real work :) 20:24:46 I'll second that 20:24:52 +1 20:25:26 additionally I wonder if suspending this second meeting until RC-1 wouldn't be a bad idea 20:25:51 will be useful for planning Newton, but less value now 20:25:57 not likely to be many additional blueprints accepted :-) 20:26:21 ok, I'll send an email. 20:26:36 Thanks everyone. Happy reviewing :) 20:26:41 thx! 20:26:42 #endmeeting