15:36:10 <ttx> #startmeeting incub_sync
15:36:11 <openstack> Meeting started Thu Aug 28 15:36:10 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:36:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:36:14 <openstack> The meeting name has been set to 'incub_sync'
15:36:16 <ttx> #topic Zaqar
15:36:39 <ttx> #link https://launchpad.net/zaqar/+milestone/juno-3
15:36:42 <ttx> nice, Lp rename
15:36:48 <flaper87> :)
15:37:02 <flaper87> so, there's been progress w.r.t the blueprints there
15:37:21 <ttx> i see you didn't move the "threat model" one yet
15:37:47 <flaper87> ttx: yup, the reason is that it won't require code so, even if Kurt works on it past the feature freeze, that's fine.
15:37:55 <ttx> oh, ok
15:38:18 <ttx> #info threat-model is non-code
15:38:40 <flaper87> The documentation one is almost done
15:38:43 <ttx> would be good to get the essential stuff merged this week if you can
15:38:56 <ttx> this week is bad, but next week will be worse </crystalball>
15:39:01 <flaper87> we approved one patch yday and there's 1 more that will merged today
15:39:27 <flaper87> Yeah, Prashanth is traveling so Kurt took over his patch
15:39:33 <flaper87> to get the redis stuff merged asap
15:40:05 <flaper87> FWIW, the redis patch just had some minor things to address
15:40:15 <flaper87> so, I'm confident it'll be done today/tomorrow
15:40:21 <flaper87> and hopefully merged ruing the weekend
15:40:28 <ttx> Hmm... I should create the RC1 milestones everywhere so that things that are non-code can be safely targeted there
15:40:29 <flaper87> during*
15:40:35 * ttx adds note
15:40:38 <flaper87> ttx: +1 that'd be useful
15:41:05 <ttx> ok, any question wrt process for next week?
15:41:20 <flaper87> nope
15:41:46 <flaper87> I've gone through the process a couple of times with marconi
15:41:52 <flaper87> it should be clear, I hope.
15:41:55 <flaper87> :P
15:42:08 <ttx> heh
15:42:16 <ttx> You answered the tricky question RIGHT
15:42:25 <ttx> ok. Talk to you later ;)
15:42:27 <flaper87> ;)
15:42:31 <flaper87> kk, thanks!
15:42:52 <ttx> jraim__: still not around?
15:42:57 <ttx> lucasagomes: want to go now?
15:43:02 <lucasagomes> ttx, hey sure
15:43:06 <lucasagomes> #link https://launchpad.net/ironic/+milestone/juno-3
15:43:09 <ttx> #topic ironic
15:43:16 <ttx> #link https://launchpad.net/ironic/+milestone/juno-3
15:43:19 <ttx> too fast :)
15:43:24 <lucasagomes> sorry for that heh
15:43:29 <lucasagomes> stats: 7 Implemented, 6 Needs Code Review, 1 Started (no code upstream yet)
15:43:35 <ttx> That looks pretty good
15:43:35 <lucasagomes> compared with last week, we have 1 more blueprint is marked as "Implemented" .  And 1 more is marked as "Need Code Review" (code was submitted yesterday)
15:43:49 <lucasagomes> from the ones marked as Need Code Review 3 of them are super close to get merged
15:44:03 <ttx> although you'll have to increase the rhythm if you want to match the deadline :)
15:44:15 <lucasagomes> yeah
15:44:22 <ttx> devananda should be back to handle the last line
15:44:44 <lucasagomes> yeah some cores in Ironic is going to get in a google hangout as well and try to review things together
15:44:58 <lucasagomes> but it's looking good right now
15:44:58 <ttx> lucasagomes: Sounds good! any question, thing i can help with?
15:45:08 <lucasagomes> ttx, I have one question
15:45:18 <ttx> awesome. i like questions.
15:45:33 <lucasagomes> one of the bps is not marked as Implemented because in the spec it mentioned that it would add some tempest tests
15:45:37 <lucasagomes> everything in Ironic is already merged
15:45:41 <lucasagomes> but not the patch in tempest
15:46:03 <ttx> lucasagomes: ah! yes, a classic limitation of the usage of launchpad blueprints I'm afraid.
15:46:12 <lucasagomes> IMO, I would mark it as Implemented already... but I don't know if I should
15:46:14 <ttx> they can't track tasks across multiple projects
15:46:18 <lucasagomes> yeah
15:46:53 <ttx> I think you should mark it implemented
15:47:03 <lucasagomes> alright
15:47:05 <lucasagomes> will do
15:47:07 <ttx> if you really want to track the tempest work, you carete a blueprint there
15:47:21 <ttx> create*
15:47:23 <lucasagomes> yeah, I was confused about how to do it
15:47:32 <lucasagomes> the tempest test is looking good anyway, has a +2 on it and so on
15:47:45 <ttx> there is no good solution unfortunately. This limitation is a major driver for the development of Storyboard, actually
15:47:51 <lucasagomes> ack
15:47:54 <lucasagomes> that's fine :)
15:48:16 <ttx> ok, then. Talk to you later! And thanks for stepping up in Deva's absence.
15:48:27 <ttx> that was much appreciated
15:48:31 <lucasagomes> so yeah, overall things are looking good... I suspect that we are going to get at least 1 more bp implemented this week (apart from the tempest one that I'm marking as implemted right now)
15:48:32 <lucasagomes> thanks
15:48:36 <lucasagomes> np at all
15:49:04 <ttx> jraim__: ready when you are
15:55:17 <jraim__> I'm ready if you are still around
15:55:36 <jraim__> ttx: ^^
15:55:50 <jraim__> sorry, my bouncer is messed up and not notifying me of mentions right now for some reason
15:56:06 <ttx> #topic Barbican
15:56:45 <ttx> #link https://launchpad.net/barbican/+milestone/juno-3
15:57:00 <ttx> That looks good, any progress recently ?
15:57:17 <jraim__> Been working with the team to clean up the BPs and retartget things that aren't going to land
15:57:39 <jraim__> Was at the ops summit too, so we talked a bit with Nova / Neutron about how to handle approved specs that didn't land
15:57:42 <jraim__> so working through that
15:57:42 <ttx> Still feeling confident for those 2 missing "high" prio ones ?
15:58:24 <jraim__> Yes, mostly. If they don't land, it'll be a shame, but the PCKS work is going now and should hopefully land
15:58:35 <jraim__> the orders resource work is a bunch of CRs
15:58:49 <jraim__> We're trying to track down all the statuses and see what, if anything, is still left to do
15:59:05 <jraim__> So most of it has landed, but there might be some things that aren't done yet and might have to wait
16:00:05 <ttx> ok
16:00:22 <ttx> Questions on the process for nex week?
16:00:32 <ttx> We should have the release tooling up to snuff this time
16:00:44 <jraim__> So it should just require a tag on our part, yes?
16:01:00 <ttx> rigth, but i'll push it as part of the release process
16:01:12 <ttx> reference: https://wiki.openstack.org/wiki/Release_Team/How_To_Release
16:01:18 <jraim__> redrobot will be the release mgr on our side - so we'll be around for whatever we need
16:01:38 <ttx> #info redrobot will be release management monkey for Barbican j3
16:02:02 <ttx> jraim__: i'll probably need you to sort the things that didn't make it
16:02:22 <ttx> between deferred and exception-granted ones
16:02:22 <jraim__> no problem, I'll be around as well
16:02:34 <ttx> i'll have the RC1 milestones created in LP so that we can track that
16:02:57 <ttx> jraim__: ok, thx, and talk to you soon
16:03:05 <jraim__> sounds good. I'm hoping we won't have any, but that is probably in vain
16:03:10 <jraim__> thanks
16:03:34 <ttx> I think in my 4-year career this happened only twice
16:03:48 <ttx> that all targets were met for a project in a FF milestone
16:04:01 <ttx> #endmeeting