15:00:12 #startmeeting gantt 15:00:13 Meeting started Tue Dec 23 15:00:12 2014 UTC and is due to finish in 60 minutes. The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:17 The meeting name has been set to 'gantt' 15:00:22 anyone here to talk about the scheduler? 15:00:35 aloha 15:00:42 o/ 15:00:50 * bauzas in the starting-blocks before going on vacation 15:01:09 bauzas, was that an indicator of where your vacation is :-) 15:01:51 n0ano: eh, I won't spoil it 15:02:04 enjoy no matter what 15:02:10 :) 15:02:16 anyway, I think we can keep it short today 15:02:21 #topic opens 15:02:25 lol 15:02:34 heh 15:03:12 I really don't have anything, the specs are doing well except we'll have to get an exception for Jay's object stuff which should be easy 15:03:14 so I guess we can lazily provide the link to the wikipage and leave the lurkers check it ? 15:03:28 you mean: 15:03:33 #link https://wiki.openstack.org/wiki/Gantt/kilo#Tasks 15:03:39 yeah ! 15:04:05 so indeed, there *are* 2 specs that could need an exception 15:04:24 how do you see 2, I only see 1 15:04:34 https://review.openstack.org/#/c/127609/ and https://review.openstack.org/#/c/138444/ 15:04:53 I still need to review edleafe's spec, but I have hard time for it 15:04:58 o/ 15:05:13 sorry, dragging a little this morning 15:05:37 ahh, I need to re-jigger the table, there's only one approved line for 2 items 15:05:39 bauzas: I proposed a different approach after we chatted 15:05:45 anyway, it seems most of the cores are on vacation, so that should be tight to get 2x +2s from nova-drivers during that non-official freeze period 15:06:37 edleafe: be sure your spec will be my bedside book 15:06:57 edleafe's spec seems pretty obvious, I would hope it wouldn't be hard to get an exception 15:07:00 bauzas: :) 15:07:29 I'm a little worried about jaypipes's one but that sounds also feasible for getting an exception 15:07:30 n0ano: yeah, it was held back waiting for bauzas spec to get approved 15:07:38 are we in Spec freeze now, aren't we ? 15:07:59 I guess it should be done soon in Januaru 15:08:07 bauzas, theoretically but the whole spec freeze & exception process is very opaque to me 15:08:41 n0ano: yeah, not sure either 15:08:53 n0ano: figured that we should add it to the next nova meeting agenda 15:09:14 edleafe: the next one is on Jan 9th 15:09:19 1400 UTC 15:09:28 edleafe, I'm thinking a lot of people will be in the same position, it's just unfortunate that we have to wait for so long 15:09:40 so I guess spec freeze should be announced there 15:10:27 we'll ask for clarity on the freeze & exception rules at that time 15:10:28 I think there is a really good improvement since Juno 15:10:39 n0ano: we can bring it up on IRC after Jan 1, and if not resolved, add it to the meeting 15:11:06 edleafe, +1 15:11:08 edleafe: are you really wanting to enjoy the New Year in the IRC channel ? 15:11:24 :) 15:11:37 I interpret `after` as a loose definition :-) 15:11:49 * bauzas seriously envisaging to write a bot to say "Happy New Year" for any people pinging him 15:12:07 n0ano: the stress was on the *after* part :) 15:12:53 hmm, xchat messed up my snarky comment, oh well 15:13:04 anyway, anything else we want to discuss 15:14:13 I think it's time to let bauzas start his vacation 15:14:19 OK, I think I will offically cancel next weeks meeting and we can pick up again on 1/6 15:14:34 have a great holiday everyone and we'll talk agin next year 15:14:46 sure thing 15:14:57 #endmeeting