15:59:49 <ttx> #startmeeting incub_sync
15:59:51 <openstack> Meeting started Thu Jan 29 15:59:49 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:59:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:59:54 <openstack> The meeting name has been set to 'incub_sync'
15:59:58 <ttx> #topic Barbican
16:00:13 <ttx> #link https://launchpad.net/barbican/+milestone/kilo-2
16:00:24 <ttx> I see one incomplete BP on the docket
16:00:32 <ttx> certificate-order-api
16:00:41 <ttx> Is that likely to get completed by the milestone next week ?
16:00:59 <redrobot> yes, it's very close to being done.  I think the last CR is in review right now, so I feel pretty confident it will land
16:01:21 <ttx> ok, moving to "needs code review" then
16:01:45 <ttx> We'll tag sometimes between Tue and Thu next week, ideally
16:01:57 <ttx> Any other thing you'd like to include in the tag ?
16:02:06 <ttx> and that we should track status of ?
16:02:10 <ttx> (feature or bugfix)
16:02:28 <redrobot> I will probably add any fixes that land before next week, but nothing critical that I can think of
16:03:03 <ttx> ok. Ping me when you're happy, worst case scenario we'll tag during the sync next week
16:03:13 <redrobot> sounds good
16:03:16 <ttx> any question on that ?
16:03:59 <redrobot> Yeah, we accidentally introduced some bad dependencies with a new client release
16:04:20 <redrobot> as I understand it the client was pinned to <3.0.2 in stable/juno
16:04:36 <ttx> redrobot: yeah, I saw that thread... not sure I understand the issue exactly
16:04:59 <ttx> what was the nesw release version ? What did it introduce ?
16:05:10 <redrobot> I think it was an oslo.something that pulled in an incompatible dependency.
16:05:42 <redrobot> we have a bot syncing requirements for us, but we didn't have a stable branches job in our gate, so we didn't notice it
16:05:49 <ttx> I thinkn that's the issue with having stable branches before you have stability :)
16:06:09 <redrobot> we have the job now, but I'm still not clear on how to backport fixes so that they can be used in juno?
16:06:39 <redrobot> should I create a stable/juno branch in the client at 3.0.1 (the last juno-compatible release) and then cherrypick for 3.0.1.x releases?
16:07:10 <ttx> well, in theory we don't do that (stable branches for clients) so that the recent client acvtually workd with the supported release
16:07:24 <ttx> but then here we don't really have a "supported release"
16:08:07 <ttx> redrobot: we should discuss that on #openstack-dev and try to get a few others in the discussion
16:08:22 <redrobot> ttx ok, will do.  thanks.
16:08:23 <ttx> would you be around in 23 min once I'm done with the syncs ?
16:08:47 <ttx> I'd like to be around to continue that discussion, but I'm stuck
16:08:54 <redrobot> yeah, I should be.  just ping me to get my attention.
16:09:12 <ttx> ok will do
16:09:30 <ttx> redrobot: was that your only topic ?
16:09:43 <redrobot> ttx yep, I'm good.
16:09:50 <ttx> ok, brb
16:09:51 <ttx> bswartz: around?
16:09:57 <bswartz> ttx: yes!
16:09:59 <ttx> #topic Manila
16:10:07 <bswartz> although I'm in a cinder meetup with 20 people o_O
16:10:10 <ttx> #topic https://launchpad.net/manila/+milestone/kilo-2
16:10:13 <ttx> err
16:10:16 <ttx> #topic Manila
16:10:23 <ttx> #link https://launchpad.net/manila/+milestone/kilo-2
16:10:35 <ttx> bswartz: act natural
16:10:40 <bswartz> yes
16:10:56 <ttx> that page shows 10 more blueprints to complete
16:10:58 <bswartz> so we reviewed the BPs and nearly all of them are in good shape
16:11:06 <ttx> are you confident they can all make it ?
16:11:17 <bswartz> I've made threats to the various developers to get their stuff fixed
16:11:28 <bswartz> honestly I expect 1 or 2 not to make it but I don't know which
16:11:37 <bswartz> so I'm giving them all a chance
16:11:42 <bswartz> it's possible to get them all merged
16:11:50 <ttx> OK -- as we get closer to the milestone window (Tuesday-Thursday next week), it would be good to to push back to kilo-3 what will miss the window
16:11:55 <bswartz> the bugs are a different story
16:12:25 <ttx> yeah, the unassigned ones are unlikely to get fixes in the time we have left
16:12:26 <bswartz> yeah I gave some of them a deadline to at least rebase and patch jenkins by tomorrow
16:12:43 <ttx> the ideal would be to keep only the milestone blockers on the page
16:12:47 <bswartz> anyone than can't do that will get pushed, so we can focus on good reviews
16:12:49 <ttx> starting Tuesday
16:13:00 <bswartz> yes
16:13:03 <ttx> and not be too greedy so that we can actually tag within the window
16:13:06 <ttx> :)
16:13:17 <bswartz> well most of the bugs are netapp related and netapp is going to triage them and see if any need to stay in k2
16:13:17 <ttx> then a quick ping when all is green and I can tag
16:13:31 <ttx> ack
16:13:51 <ttx> but generally, good progress
16:14:01 <bswartz> I think we're on the same page -- by Tuesday anything nonessential should be pushed out
16:14:08 <ttx> I'll let you trim down that buglist
16:14:16 <ttx> any question on the process ?
16:14:45 <bswartz> when is the ideal time to tag the milestone frm your perspective?
16:14:54 <bswartz> Wednesday night? Thursday morning
16:14:55 <bswartz> ?
16:15:01 <ttx> bswartz: wednesday.. morning for you
16:15:11 <ttx> afternoon for me
16:15:18 <bswartz> okay we'll shoot for that and I'll tell you if we're going to be late
16:15:21 <ttx> Tuesday and Thursday are usually busier
16:15:41 <ttx> bswartz: cool, that works
16:15:48 <ttx> that's all I had
16:15:51 <bswartz> thanks ttx
16:15:53 <bswartz> same here
16:16:00 <ttx> cool, have a good week and meetup
16:16:07 <bswartz> I'll get back to this meetup and cracking the whip on manila devs
16:16:08 <ttx> flaper87: ready when you are
16:17:31 <flaper87> ttx: here
16:17:34 <ttx> #topic Zaqar
16:17:40 <ttx> #link https://launchpad.net/zaqar/+milestone/kilo-2
16:17:55 <ttx> That looks still very much work in progress...
16:18:16 <flaper87> yeah, I'm giving some of those a couple of more days before pushing them back to k-3
16:18:18 <ttx> Are any of those open BPs actually just waiting on review on code fully posted ?
16:18:27 <ttx> (i.e. should be Need code review status)
16:18:28 <flaper87> I'm confident few of those bps will be fully implemented
16:18:41 <flaper87> ah damn, why do I always forget there's a Need core review status?
16:18:43 <flaper87> T_T
16:18:55 <flaper87> yeah, most of them are up for review
16:19:03 <flaper87> there're 2 that need follow-up patches
16:19:03 <ttx> We use it to represent "all code posted, wtf are the reviewers doing" state
16:19:22 <ttx> also works for "I gave -1 wtf is the author doing"
16:19:29 <flaper87> hahahaha
16:19:34 <ttx> basically the final stages
16:19:34 <flaper87> yeah, that makes sense
16:19:39 <flaper87> I'll update those bps
16:20:01 <flaper87> ttx: question: Is it "legal" to remove the "Incubated" lable from zaqar in the docs page?
16:20:05 <ttx> We use Good progress / Slo progress more to represent "I'm in the middle of a 12-patch long patchseries"
16:20:07 <flaper87> (and everywhere it's being used)
16:21:09 <ttx> flaper87: it's consistent with https://review.openstack.org/#/c/145740/14/reference/projects.yaml
16:21:28 <ttx> scroll down to line 355
16:21:38 <flaper87> w00000t
16:21:39 <flaper87> :D
16:21:40 <ttx> but that's not approved yet
16:21:54 * flaper87 will throw a zaqar party at FOSDEM
16:22:03 <ttx> I think that's the sense of history though
16:22:04 <flaper87> yeah, I'll wait for that patch to land then
16:22:12 <ttx> direction of history
16:22:17 <ttx> probably better
16:22:48 <ttx> That's the change where we erase "incubation" from the collective history
16:22:48 <flaper87> ok, other than that. I've no further questions
16:23:11 <flaper87> nice, looking forward to the beginning of the tagging craziness
16:23:11 <ttx> alright, update your status, ping me when you have a "won't get much more in anyway" SHA
16:23:22 <flaper87> will do
16:23:27 <ttx> ideally between Tue and Thu next week
16:23:31 <ttx> great, thx
16:24:02 <ttx> flaper87: oh, and push back bugs as well, not just BPs
16:24:11 <ttx> Kiall: ready when you are
16:26:03 <Kiall> ttx: heya
16:26:08 <ttx> #topic Designate
16:26:14 <ttx> #link https://launchpad.net/designate/+milestone/kilo-2
16:26:20 <ttx> 2 open BPs
16:26:35 <ttx> how likely is taht to be completed by the milestoen window next week ?
16:26:36 <Kiall> Yes, Agent has merged - there's a followup commit pending before complete
16:26:53 <Kiall> and the 2nd one has code waiting to me to submit
16:27:02 <Kiall> so - likely to close both out.
16:27:03 <ttx> so still on track
16:27:23 <ttx> On the bugs side, you might want to trim the list to milestone blockers
16:27:38 <Kiall> Yes - many of the still open bugs will likely get pushed to k3
16:27:40 <ttx> and push back most unassigned ones unless you can get someone on them now
16:27:56 <ttx> Then when you're happy and that page is all green, you can send me a SHA
16:28:01 <ttx> hopefully between Tue and Thu
16:28:19 <Kiall> Yea, I asked people to push anything that won't land in our meeting last night, nothings changed yet though ;)
16:28:22 <ttx> same old process
16:28:35 <Kiall> Sounds good
16:28:36 <ttx> yeah, cats!
16:28:50 <Kiall> :D
16:28:58 <ttx> ok, that's about all I had, you look in good shape
16:29:06 <ttx> any question on your side ?
16:29:09 <Kiall> can't help myself..
16:29:09 <Kiall> _,,/|
16:29:09 <Kiall> \o o'
16:29:09 <Kiall> =_~_=
16:29:09 <Kiall> /   \ (\
16:29:10 <Kiall> (////_)//
16:29:11 <Kiall> ~~~
16:29:22 <Kiall> Nope, same old process as you said :)
16:29:31 <ttx> that's a single cat. It's when there are thousands that it gets tricky.
16:29:35 <Kiall> I'll do the bug list myself tonight if nobody else get's to it first
16:29:39 <ttx> alright
16:29:45 <ttx> have a good end of week
16:29:49 <Kiall> Same to you..
16:29:55 <ttx> I'll try to be at Graham's presentation at FOSDEM
16:30:09 <Kiall> I'm technically presenting at that too ;)
16:30:19 <ttx> technically ? Or really ?
16:30:25 <Kiall> But - It's so short, I might leave it to Graham
16:30:34 <ttx> ok, but you'll be around?
16:30:45 <Kiall> Yes - I fly out friday :)
16:30:46 <ttx> ok, see you there then!
16:30:54 <Kiall> I'll keep and eye out for you :)
16:30:57 <ttx> #endmeeting