22:01:09 #startmeeting neutron_drivers 22:01:10 Meeting started Thu Aug 10 22:01:09 2017 UTC and is due to finish in 60 minutes. The chair is kevinbenton. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:01:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:01:14 The meeting name has been set to 'neutron_drivers' 22:01:30 so I'd like to keep this meeting somewhat short since we are dealing with the initial pike branch cut today 22:01:39 armax: can you give us a timeline for releases? 22:01:49 cool 22:02:00 yes sir 22:02:04 https://releases.openstack.org/pike/schedule.html 22:02:12 we’re in R-3 22:02:29 today I think we should unlock 22:02:32 #link https://review.openstack.org/#/c/491560/ 22:02:44 most likely after this meeting 22:03:01 and thus tomorrow rc1 will be tagged and the pike branch will be cut 22:03:06 for those repos 22:03:09 at that point 22:03:26 we have about another 2 weeks to stabilize 22:03:36 and cut further rcX 22:04:13 any patch in the tree should be blocked and only those targeting bug reports with pike-rc-potential should be evaluated 22:04:20 s/tree/gerrit/ 22:04:37 armax: due to the instability of the gate it looks like we are going to have trouble landing the things that are in flight, will we be allowed to back-port them into the new pike branch? 22:04:50 landing them in time for today 22:05:05 kevinbenton: the gate is always unstable during crunch time 22:05:05 :) 22:05:32 do you have a list of things that are on track for landing in the next few hours? 22:05:55 armax: this and its children are mlavalle's dns work https://review.openstack.org/#/c/491873/ 22:06:06 armax: it just hit a rally timeout so it's restarting now 22:06:12 anything that has a DB migration or API facing change is gonna be though to backport 22:06:30 OK 22:06:48 the queue is not too long 22:06:53 armax: in that case this one is pretty important 22:06:55 armax: https://review.openstack.org/#/c/483518/ 22:07:03 armax: that has the MTU db addition 22:07:04 and nothin in that series has db migration 22:07:15 but each patch takes at least 3-4 hours to go all the way through 22:07:16 armax: and it just failed because of a keystone password update test 22:08:01 henryG had a query that would look up patches with alembic changes 22:08:06 can’t recall on the top of my head 22:08:29 I can find out what are those outstanding and see what the status is 22:08:58 the other one i'd like to back-port even though it isn't feature related is this one 22:08:59 https://review.openstack.org/#/c/453355/ 22:09:17 if we get that in Pike it's going to make future back-ports much less conflict heavy 22:09:32 we should be able to backport this 22:09:34 armax: would that be allowed? 22:09:35 armax: ok 22:10:13 armax: also this one that just deprecates that web_framework option https://review.openstack.org/#/c/490613/ 22:10:16 I just love how we do and undo stuff 22:10:45 OK 22:11:10 it’s unlikely any of these merge by today 22:11:14 I have some logging reduction patches that need to be fixed up but we can decide to backport those much later 22:11:14 I reckon 22:11:39 anything that trims logs is welcome 22:12:19 kevinbenton: probably wise to send an email about this 22:12:41 to remind the team of the process 22:12:48 armax: i'll wait to see where the cards fall when you cut the branch and send a list of patches we'd like to get in 22:13:17 then once things settle a bit, we can continue feature development on master at that point, right? 22:13:53 once stable/pike is open 22:14:02 anything can flood the gate on maste 22:14:02 r 22:14:25 ok, cool 22:16:25 does anyone have anything else release related? 22:16:35 arno 22:16:38 not me 22:16:46 nop 22:16:50 if not, i'd like to end the meeting early so we can shepard these patches in 22:16:55 ok 22:16:58 ++ 22:17:00 thanks 22:17:06 o/ 22:17:06 OK then 22:17:10 #endmeeting