12:31:52 <ttx> #startmeeting incub_sync
12:31:52 <openstack> Meeting started Thu Sep 25 12:31:52 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:31:53 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:31:56 <openstack> The meeting name has been set to 'incub_sync'
12:32:00 <ttx> #topic Designate
12:32:15 <ttx> https://launchpad.net/designate/+milestone/juno-rc1
12:32:17 <Kiall> So - We talked last week about pushing that last BP out, it's not merged, so we pushed it to Kilo.
12:32:29 <ttx> 2 RC bugs left before we can cut RC1
12:32:45 <ttx> Just let me know when you're done, and we'll tag and open kilo
12:33:03 <ttx> then if some new release-critical thing is detected we'll open a RC2 window to fix it
12:33:04 <Kiall> Yes, both have reviews up, one has a mistake or two, the other needs review.
12:33:32 <Kiall> Since neither are "it's totally broke" bugs - should we cut an rc1 and expect to do an rc2, or better to wait?
12:33:35 <ttx> You seem in good shape
12:33:48 <ttx> no, we should wait
12:34:08 <ttx> RCs need to be release candidates
12:34:21 <ttx> i.e. at that point in time, you're fine with it being released as final
12:34:34 <Kiall> Okay - Hopefully we can get them both merged today. I'll takeover Endre's and get the other cores to re-review both today.
12:34:43 <Kiall> (Endre is on holidays now..)
12:34:54 <ttx> you can discover new things... and respin the RC... but there is no point in doing a RC1 when you already have bugs piled up for a RC2
12:35:07 <Kiall> Sure, makes sense.
12:35:16 <ttx> so better wait a few days to be sure, rather than open a RC2 window just after RC1 iscooked
12:35:34 <ttx> The rationale is.. people only test RCs if they believe it may be the final
12:35:46 <ttx> if a RC2 is queued, then they wait
12:35:58 <ttx> Releasing is a psychology exercise
12:36:23 <Kiall> Hah - OK - Makes sense.. I'll ping you once both have landed then?
12:36:30 <ttx> Kiall: yes -- other questions ?
12:36:42 <Kiall> Yep - But all can wait till we open kilo ;)
12:37:02 <Kiall> Actually.. 1
12:37:04 <ttx> Looking at design summit space -- nothing final, but current estimate:
12:37:22 <Kiall> Oo - I didn't know you were involved in that! Then I have questions ;)
12:37:25 <ttx> You would get 3 scheduled slots on the Tuesday, then a pod for the rest of the week
12:37:32 <ttx> (dedicated pod)
12:37:57 <Kiall> Okay - That sounds reasonable, I understand space in Paris is somewhat more limited than usual.
12:38:39 <Kiall> The scheduled slots, at what point do we finalize the topics etc?
12:38:42 <ttx> (incubated projects in ATL got about the same fwiw)
12:38:54 <ttx> Kiall: at least one week before summit starts
12:39:04 <ttx> so people can start organizing and we can check conflicts
12:39:19 <ttx> It's the job of the Kilo PTL, but you might be that person
12:39:19 <Kiall> Yep - I was expecting it to be less than ATL, since space is tighter and there's more projects!
12:39:50 <Kiall> Yep - I've nominated myself, and asked the others to nominate themselves if they wish.
12:39:59 <ttx> Kiall: alright then, talk to you later ?
12:40:08 <Kiall> Yep - Enjoy your day :)
13:21:28 <Kiall> ttx: FYI both patches have 2x +2's .. Waiting on the check queue to +1, then I expect they will be approved shortly after..
13:52:47 <ttx> SergeyLukjanov, zaneb: ping re: RC1 buglist when you get a chance
14:55:18 <mestery> ttx: Any idea on when you plan to cut RC1? Trying to see which bugs have a chance at this point.
14:55:49 <ttx> When you're ready and confident it could make a release candidate
14:56:01 <ttx> The goal is to hit that before the end of the month ideally
14:56:12 <ttx> to leave 2 weeks for further testing
14:56:19 <ttx> and potential respins
14:56:55 <ttx> mestery: so as we get closer to the end of the month, we become more picky on what is considered a release blocker
14:57:34 <mestery> ttx: Ack, I've been pairing things down, I think we're down to 10 bugs in RC1 now, with maybe 3-4 of those in the queue and the rest being respun today
14:57:36 <ttx> and then we only reopen a new RC window if a bug is serious enough (like: it's a regression)
14:57:36 <mestery> So we're close
14:57:42 <mestery> Got it
14:58:12 <ttx> the goal being, to trick testers into thinking it might well be the final, so they better test it
15:08:08 <dolphm> ttx: have an RC1 countdown chart running?
15:08:24 <ttx> dolphm: http://old-wiki.openstack.org/rc/
15:09:28 <dolphm> ttx: did i miss something with glance? no PTL candidacies for kilo + no RC blockers?
15:10:33 <ttx> dolphm: the team around it wasn't very active in Juno. So it's not very surprising they are not broken hopelessly at this point
15:11:03 <ttx> we still hope to find candidates before the end of the day though :)
15:12:23 <zaneb> ttx: o/
15:13:05 <ttx> zaneb: hey! Feel like the curve of RC issues is not going in the right direction those last days for Heat: http://old-wiki.openstack.org/rc/
15:13:26 <ttx> it might be time to split between real release blcokers and nice-to-haves-that-could -be-fixed-post-release
15:13:47 <zaneb> yep, that is my task for today
15:14:17 <zaneb> that and triaging the 'new' bugs to make sure none of those are actually release blockers
15:15:19 <ttx> right, ok
15:15:41 <ttx> i want that curve oriented in a way that makes it look like it may hit the floor before the end of the month
15:15:57 <ttx> hint: it never really does :)
15:16:06 <zaneb> lol
15:16:15 <ttx> Although I guess Cinder's curve is a good approximation
15:17:05 <ttx> most of the others have a week or two of "RC1 what?", then a surge as bugs get triaged... then a few steep drops when I ping people about keeping only blockers
15:17:33 <ttx> then they brutally hit the floor one or two days after the symbolic deadline I set
15:23:15 <ttx> david-lyle: got a minute?
15:23:25 <david-lyle> yes
15:23:53 <ttx> david-lyle: same remark, horizon RC bugs not going in the right direction over the last day(s)
15:24:02 <ttx> are they all release blockers?
15:24:50 <ttx> or could you further split blockers from nice-to-haves ?
15:24:56 <david-lyle> several last minute previously untargeted Sahara issues cause the bump in our curve
15:25:02 <ttx> oh, right
15:25:15 <ttx> I guess you can hit RC1 slightly later than the others though
15:25:23 <ttx> like before the end of next week
15:25:58 <ttx> SergeyLukjanov: around?
15:26:05 <david-lyle> yes, I hope so. A few of the in progress are +A and making there way through the gate now
15:26:12 <david-lyle> *their
15:26:14 <SergeyLukjanov> ttx, yup
15:26:26 <SergeyLukjanov> ttx, for sahara https://launchpad.net/sahara/+milestone/juno-rc1 is up to date
15:26:38 <ttx> SergeyLukjanov: same remark, a bit concerned that your RC bug curve is generally not oriented in the right direction
15:26:50 <ttx> oh. 0 ?
15:26:59 <SergeyLukjanov> ttx, yup
15:27:01 <ttx> some would say that's cheating now
15:27:20 <ttx> SergeyLukjanov: how about we let it bake for one day and cut tomorrow when you get up ?
15:27:33 <ttx> I'll run a few checks
15:27:35 <SergeyLukjanov> ttx, +1
15:27:53 <SergeyLukjanov> ttx, we're testing it now too
15:28:19 <SergeyLukjanov> ttx, all other open issues are all about docs
15:29:02 <ttx> alright, good
15:30:27 <SergeyLukjanov> david-lyle, thanks for accepting our last minute patches, and sorry about this...
15:31:19 <david-lyle> SergeyLukjanov: no worries, if we have them on our radar sooner in the future, there should be less scrambling
15:31:31 <david-lyle> but we'll get them in
15:31:42 <ttx> SergeyLukjanov: I cut horizon some slack precisely due to that
15:31:57 <ttx> they are often hit by last-minute things in upstream projects
15:32:10 <ttx> so the are naturally "ready" a bit later
15:32:16 <ttx> jraim: around?
15:32:28 <jraim> ttx: yes
15:32:31 <ttx> #topic Barbican
15:33:04 <ttx> https://launchpad.net/barbican/+milestone/juno-rc1
15:33:32 <ttx> still seem like a lot to do before you can do a RC1
15:34:05 <ttx> Are those 2 features still in progress ?
15:34:11 <jraim> redrobot is working on it. we only have a little bit left from what I understand
15:34:21 <redrobot> hi ttx and jraim!  Yes, I just bumped one of the BPs to Kilo-1.  The other one is just waiting on a single patch, so we should have that merged in the next day or two.
15:34:44 <ttx> OK, then the goal is to come up with a list of release blockers
15:34:48 <redrobot> after that we'll be in bugfix mode.  Not sure if we'll want an RC1 now, and then an RC2 with bugfixes.
15:34:58 <ttx> and keep non-release blockers out of the list, so that we know when we can tag a RC1
15:35:15 <ttx> no, ideally RCs need to truly be potential release candidates
15:35:18 <ttx> so better wait
15:35:28 <redrobot> ok
15:35:38 <ttx> no big deal if you miss the "end of month" target I set for intgrated release
15:36:36 <ttx> so yes, get those features out of the picture so that you can concentrate on identifying release blockers and getting them fixed
15:36:59 <ttx> then when you believe you have a winer, we tag it RC1, which should result in added scrutiny from external testers
15:37:08 <ttx> and potentially regressions being found
15:37:15 <ttx> which would then warrant a RC respin
15:37:23 <ttx> jraim, redrobot: makes sense ?
15:37:59 <redrobot> ttx yes, got it.  Once we're comfortable with RC1, should I just ping you directly?
15:37:59 <ttx> (the perk being when we tag RC1 we also unfreeze master)
15:38:07 <ttx> redrobot: yeah
15:38:14 <redrobot> ok, will do.
15:38:38 <ttx> jraim, redrobot: questions ?
15:38:56 <redrobot> I'm good. How about you jraim?
15:39:35 <jraim> sorry - drive by meeting. Getting caught up
15:39:49 <jraim> this makes sense to me
15:40:49 <ttx> ok then! talk to you guys later
15:40:57 <jraim> thanks!
15:41:01 <ttx> flaper87: arond?
15:41:07 <ttx> around, even?
15:41:17 <flaper87> ttx: o/
15:41:20 <flaper87> sorry
15:41:23 <ttx> #topic Zaqar
15:41:31 <ttx> https://launchpad.net/zaqar/+milestone/juno-rc1
15:41:37 <ttx> 4 RC bugs left
15:41:41 <ttx> which all seem RC to me
15:41:44 <flaper87> zaqar is in a pretty bad shape now, there are some bugs that I'd like to get in but our gate is blocked
15:41:49 <ttx> so nothing to add really
15:42:15 <flaper87> patches for those bugs are up for review
15:42:25 <flaper87> we're waiting for the patch that fixes our gate to land
15:42:28 <flaper87> to get this done
15:42:56 <ttx> ok
15:43:14 <ttx> ping me when you get closer to rc1 and I'll run the scripts for you
15:43:19 <ttx> flaper87: questions?
15:43:42 <flaper87> ttx: nope, all clear
15:46:04 <ttx> flaper87: alright, thx
15:46:10 <ttx> devananda: ready when you are
16:31:23 <ttx> #endmeeting