14:53:13 <ttx> #startmeeting incub_sync
14:53:14 <openstack> Meeting started Thu Apr  2 14:53:13 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:53:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:53:16 <ttx> #topic Manila
14:53:18 <openstack> The meeting name has been set to 'incub_sync'
14:53:20 <bswartz> I have a hard stop at 1500UTC
14:53:27 <ttx> bswartz: yes, let's do it quick
14:53:39 <ttx> https://launchpad.net/manila/+milestone/kilo-rc1
14:53:48 <ttx> Still have one feature freeze exception running ?
14:54:03 <ttx> Would be good to close it asap so that you can focus on RC bugfixing
14:54:03 <bswartz> yes, we granted 2 actually
14:54:16 <ttx> oh, would be nice to add the other one to the LP page
14:54:18 <bswartz> one of the bugs looked like a feature so we put it through the FFE process
14:54:26 <ttx> ok
14:54:28 <bswartz> it's a bug in LP
14:54:45 <bswartz> https://bugs.launchpad.net/bugs/1437176
14:54:46 <openstack> Launchpad bug 1437176 in Manila "glusterfs_native: Unable to create shares using newly available GlusterFS volumes without restarting manila share service" [Medium,In progress] - Assigned to Csaba Henk (chenk)
14:54:52 <bswartz> so what you see there is accurate
14:55:05 <ttx> #info second FFE for https://bugs.launchpad.net/bugs/1437176
14:55:16 <bswartz> everything is ready to merge today with the exception of 2 bugs
14:55:17 <ttx> bswartz: feel like both are close to final merging ?
14:55:22 <ttx> ok
14:55:35 <ttx> So you might just be able to issue a RC1 at the end of next week
14:55:45 <bswartz> I'm going to try to figure out if we can push the RC a few days to get those bugs in too
14:55:54 <ttx> then you can work on Liberty and if you spot a critical issue we can backport it (and a few others) and do a RC2, etc
14:56:02 <bswartz> if something is going to take more than a few days we may go ahead with RC1
14:56:06 <ttx> I don't have a set date for RC1
14:56:22 <bswartz> yeah -- I was hoping for today but we didn't meet that goal
14:56:40 <ttx> basically you need to be hhappy enough with it to stamp it as "releasable for all I know"
14:57:04 <ttx> no point in tagging RC1 if you know you have bugs you don't want to final-release with and ask for a RC2 the minute after
14:57:14 <bswartz> okay
14:57:26 <bswartz> in that case the RC will definitely be delayed a few more days
14:57:27 <ttx> you have to believe (at the moment of tagging) that this is good enough
14:57:40 <bswartz> so do you tag RCs or do I?
14:57:49 <ttx> the trick is more to lower your standards of "good enough" based on time :)
14:58:00 <ttx> I do them because you need to create branches at the same time
14:58:19 <ttx> although I can walk you through the scripts if you want to run them yourself
14:58:20 <bswartz> should I just come grab you when the last critical bug merges?
14:58:29 <ttx> yes, when the RC1 page is all green, ping me
14:58:40 <bswartz> it will most likely be Monday-Wednesday
14:58:53 <ttx> won't be around on Monday. Tuesady+ is fine
14:58:59 <bswartz> ok
14:59:02 <bswartz> extra time for us then
14:59:03 <ttx> i'll let you jump on your next meeting
14:59:04 <bswartz> :-)
14:59:15 <ttx> don't hesitate to reach out to me if you have questions
14:59:19 <bswartz> thanks
14:59:23 <ttx> bswartz: have a good day!
14:59:35 <ttx> redrobot: ready when you are
14:59:39 <redrobot> ttx o/
14:59:51 <ttx> #topic Barbican
15:00:08 <ttx> https://launchpad.net/barbican/+milestone/kilo-rc1
15:00:10 <ttx> I see one FFE left
15:00:14 <ttx> is that the last one ?
15:00:26 <redrobot> yeah, that's the only outstanding one
15:00:29 <ttx> Also the bug list is suspiciously empty
15:00:45 <redrobot> indeed.  I have to triage some bugs to see what is needed for RC1
15:00:45 <ttx> I suspect you didn't run through all the bug list and target release-critical stuff yet ?
15:00:49 <redrobot> i'll be doing that today
15:00:57 <ttx> awesome
15:01:35 <ttx> ideally we would tag RC1 sometime next week, although I don't mind if you can't meet that date
15:01:59 <ttx> How far is that last FFE from merging ?
15:02:05 <redrobot> awesome... I was thinking Thursday next week, but I do want to beat up on the FFE once it lands
15:02:15 <ttx> ack
15:02:20 <redrobot> we had a google hangout yesterday to iron out the last of the issues
15:02:30 <redrobot> just waiting on a new patch from the feedback
15:02:32 <ttx> we kind of need to issue the RC1, if only to trigger testing from an array of people
15:02:48 <ttx> but that should be done when you're reasonably confident it's not utterly broken
15:03:00 <ttx> otherwise it's counterproductive
15:03:14 <redrobot> agreed.  I'll aim for Thursday and let you know if anything comes up in our next 1:1
15:04:12 <ttx> ok, that is all I had
15:04:29 <redrobot> ttx cool, see you next week
15:04:47 <ttx> cheers!
15:05:00 <ttx> flaper87: ready when you are
15:05:08 <flaper87> ttx: ready
15:05:34 <ttx> #topic Zaqar
15:05:48 <ttx> https://launchpad.net/zaqar/+milestone/kilo-rc1
15:05:56 <ttx> Same as Barbican...
15:06:08 <ttx> One FFE up and bug list suspiciously empty
15:06:18 <ttx> Is taht the last FFE for Zqar ?
15:06:29 <flaper87> The FFE is on review and it's ready. Some nits to address before it can land
15:06:44 <flaper87> Re the bug list, the remaining bugs were not high prio so I moved them
15:06:55 <ttx> ok, once that's done it would be great to scrub trhe bug list and see what you must fix before tagging
15:06:57 <flaper87> to focus on reviews and that outstanding FFE
15:07:06 <flaper87> ttx: yes sir, consider it done!
15:07:15 <ttx> if you're bug-free then we could just tag once that FFE is in :)
15:07:33 <flaper87> ttx: roger, I'll work on getting that patch in and scrub the bug list
15:07:34 <ttx> alright, don't have much to add
15:07:39 * flaper87 neither
15:07:41 <flaper87> :D
15:07:46 <ttx> you know where I am if you need me
15:07:47 <flaper87> quickest meeting ever
15:07:49 <flaper87> :D
15:08:11 <ttx> Kiall: ping me when around
15:08:14 <nikhil_k> ttx: hi
15:08:22 <nikhil_k> (was in glance meeting)
15:08:27 <nikhil_k> (weekly one)
15:08:40 <ttx> nikhil_k: ohai
15:08:55 <nikhil_k> o/
15:09:00 <ttx> so CIS merged
15:09:15 <ttx> and I guess we should defer Artifact repo (it's still on the list)
15:09:56 <ttx> trying to see if those patches he stil asked for are in now
15:10:06 <nikhil_k> ttx: I think they are
15:10:21 <nikhil_k> ttx: I asked him to create a new spec with more details of what merged and what did not
15:10:58 <ttx> yes, all merged
15:11:00 <ttx> ok, deferring
15:11:34 <ttx> nikhil_k: so now you need to come up with a clean list of blockers for RC1 (if any)
15:12:00 <ttx> then we'll burn down that list (either by fixing the bugs, or removing them from the critical path)
15:12:14 <ttx> and when we're empty, tag
15:12:28 <ttx> nikhil_k: but all that process relies on a clean buglist
15:12:36 <Kiall> ttx: on my way back from lunch - will be 8 (or more likely 10 mins)
15:12:43 <ttx> Kiall: perfect
15:13:09 <ttx> nikhil_k: did you go through the bug list yet ?
15:13:30 <nikhil_k> ttx: yes, I did
15:13:58 <ttx> oh, cool. So the list is actually up to date. Sounds like you could hit the RC1 tag sometimes next week
15:14:02 <nikhil_k> https://launchpad.net/glance/+milestone/kilo-rc1
15:14:22 <nikhil_k> yes, I think we need to remove this from RC1
15:14:23 <nikhil_k> https://bugs.launchpad.net/bugs/1417304
15:14:23 <openstack> Launchpad bug 1417304 in Glance "Upload/Import image continues consuming glance host cpu/memory/network/disk resources even after the image is deleted" [Undecided,Incomplete]
15:14:27 <nikhil_k> and this one is merge:
15:14:31 <nikhil_k> https://bugs.launchpad.net/bugs/1276694
15:14:31 <openstack> Launchpad bug 1276694 in neutron "Openstack services should support SIGHUP signal" [Wishlist,In progress] - Assigned to Elena Ezhova (eezhova)
15:14:40 <nikhil_k> another related is in kilo-rc-potential
15:14:48 <nikhil_k> basically, we're on track
15:14:57 <ttx> ok, you can clean them up
15:15:09 <ttx> agree that "incomplete" bugs should not be targeted to RC1
15:15:11 <nikhil_k> I asked the authors to, if they dont' today I will
15:15:15 <ttx> alright
15:15:20 <ttx> sounds like you have stuff under control
15:15:23 <ttx> questions ?
15:15:37 <nikhil_k> ttx: do we have a wiki for RC restrictions?
15:15:58 <ttx> what do you mean by RC restrictions ? Feature freeze ?
15:16:18 <ttx> Usually the whole dance is explained at https://wiki.openstack.org/wiki/ReleaseCycle
15:17:20 <ttx> let me know if it's missing something
15:17:36 <nikhil_k> ah, I was looking for more control on reviews
15:17:48 <nikhil_k> and to let everyone know where to stop giving +2A
15:18:21 <nikhil_k> That seems okay and I think people will have to use their common sense
15:18:51 <ttx> yeah, we don't really prevent them from shoting themselves in the foot
15:19:37 <nikhil_k> gotcha
15:20:10 <ttx> nikhil_k: that's all I had. Questions on your side ?
15:20:19 <nikhil_k> Nothing from me
15:20:21 <nikhil_k> Thanks!
15:20:30 <ttx> alright then, have a great end of week, talk to you Tuesday
15:20:45 <nikhil_k> Have a nice one, yourself!
15:20:47 <nikhil_k> ttyl
15:20:57 <Kiall> hey ttx - back at my desk...
15:21:01 <ttx> #topic Designate
15:21:06 <Kiall> (and only 13 seconds late ;))
15:21:14 <ttx> https://launchpad.net/designate/+milestone/kilo-rc1
15:21:21 <ttx> Perfect timing, had to talk to Nikhil anyway
15:21:50 <ttx> I see one unprioritized BP left
15:21:58 <Kiall> Okay - 3 the in-progress bugs have reviews up, 1 in gate, 2 just got some minor reviews.
15:22:25 * ttx removes the invalid one
15:22:42 <ttx> How far is stable-v2 from merging ?
15:22:53 <ttx> (if that's something you want to merge)
15:23:17 <Kiall> The last BP - Mark V2 stable - is waiting on a decision as to if we can call V2 stable - The actual change is a 1 liner, we're reviewing the API and thinking through future use cases to make sure we don't shoot ourselves in the foot
15:23:42 <Kiall> I'm hopeing we can have a go/no go before the weekend is out.
15:23:45 <ttx> ok, so it's a last minute thing
15:23:57 <ttx> #info stable-v2 is a placeholder for the decision on marking v2 stable or not
15:24:07 <Kiall> Yea, exactly..
15:24:18 <ttx> ok, you seem to have stuff under control
15:24:28 <ttx> and to be on track to hit RC1 in a reasonable timeframe
15:24:43 <ttx> I don't think I have questions. Do you ?
15:24:54 <Kiall> Yea, things are shaping up nicely :) I'll likely give you a sha1 for rc1 early next week
15:26:00 <ttx> cool, thx!
15:26:03 <Kiall> 1 - we'll probably have an rc2.. we just don't know what specific issues yet
15:26:20 <ttx> right -- it's fine to have a RC2 over a new unknown issue
15:26:21 <Kiall> HP designate folks getting into a room the week of the 12th to try break things..
15:26:32 <Kiall> and I'm confident we'll find a bunch ;)
15:26:45 <ttx> that's the goal, rc1 usually triggers testing
15:26:52 <Kiall> Cool, that's it so :)
15:26:56 <ttx> it's the "will be the release unless you can find a critical bug in it"
15:27:15 <ttx> alrightn have a great end of week!
15:27:20 <Kiall> Same to you
15:27:22 <ttx> #endmeeting