08:04:11 <ttx> #startmeeting ptl_sync
08:04:12 <openstack> Meeting started Tue Mar 31 08:04:11 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:04:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:04:15 <openstack> The meeting name has been set to 'ptl_sync'
08:04:18 <ttx> #topic Heat
08:04:32 <ttx> #link https://launchpad.net/heat/+milestone/kilo-rc1
08:04:32 <asalkeld> hi ttx
08:04:43 <ttx> asalkeld: o/
08:05:17 <ttx> so let's see where thoise two FFEs stand
08:05:37 <asalkeld> dam that one bp was approved, but failed on merge
08:05:44 <ttx> convergence-push-data was supposed to be completed before end of last week
08:05:44 <asalkeld> https://review.openstack.org/#/c/161306/
08:05:58 * ttx looks
08:05:59 <asalkeld> yeah, needs rebase i think
08:06:23 <asalkeld> ttx it's not super important - if you need to cut a release we can push it
08:06:57 <ttx> needs rebase ? Or just recheck ?
08:07:09 <asalkeld> ttx: i just noticed, i'll check up on it
08:07:20 <asalkeld> ttx i just pushed the mistral resources out
08:07:24 <ttx> If it's in pipe, it's fine
08:07:31 <ttx> (the convergence stuff)
08:07:34 <asalkeld> ok
08:07:50 <asalkeld> so most of those bugs are close
08:07:51 <ttx> if more work is needed (than just rechecks) then we would push it out
08:08:10 <asalkeld> i am fine with that
08:08:27 <asalkeld> ttx: when do you want to do the rc1?
08:08:27 <ttx> so please have a look after the sync
08:08:36 <asalkeld> (will do)
08:08:42 <ttx> as soon as your critical bug list is empty
08:09:03 <ttx> Could be at the end of the week, could be next week
08:09:11 <asalkeld> ok
08:09:50 <ttx> Looks like you parsed the bug list, so your RC1 list should be pretty complete
08:10:23 <asalkeld> yeah not a big deal, most look ok
08:10:25 <ttx> #info convergence-push-data is in the pipe, so FFE extended. If more work needed, will be deferred
08:10:37 <asalkeld> i'll chase up the really important ones
08:10:46 <ttx> #info 6 bugs left
08:11:54 <ttx> Anything else on your side ? Red flags ?
08:12:11 <asalkeld> no, all looks ok to me
08:12:18 <ttx> We'll discuss PTL election season and the design summit scheduling at the cross-poject meeting
08:12:19 <asalkeld> (note 5 bugs now)
08:12:23 <ttx> in case you can join
08:12:33 <asalkeld> ok
08:12:50 <asalkeld> ttx: note i'll take a week off and get stevebaker to cover
08:12:57 <asalkeld> i'll email you the exact time
08:13:03 <ttx> asalkeld: basically, RC1 is cut when you're satisfied enough with the known state of the code that you would not be ashamed if we called it "the release"
08:13:20 <asalkeld> ok ttx
08:13:32 <asalkeld> i'd say even now it's fine
08:13:35 <ttx> then you discover new embarassing bugs and you reboot the process for a RC2 :)
08:13:46 <asalkeld> yeah
08:13:56 <ttx> too early and you miss the late bug reports
08:14:07 <asalkeld> good point
08:14:27 <ttx> so you don't want to cut too early (that's a recipe for an early RC2 round :)
08:14:44 <asalkeld> so maybe the end of the week?
08:14:54 <ttx> but yeah, end of this week/start of next week is probably fine. Early is not a bad thing
08:15:22 <asalkeld> cool, i am easy with those 2 options
08:15:36 <asalkeld> ttx: there is project meeting this week?
08:15:40 <ttx> asalkeld: starting with RC2 you fix in master and backport to the release branch, so it's more work fixing issues
08:16:02 <ttx> asalkeld: yes, see above
08:16:08 <asalkeld> cool
08:16:14 <ttx> "We'll discuss PTL election season and the design summit scheduling at the cross-project meeting"
08:16:27 <asalkeld> (i have to wake up at 5:45am to make it)
08:16:35 <asalkeld> just making sure
08:17:09 <ttx> you can catch up with the log
08:17:20 <asalkeld> yeah, bad form to miss it
08:17:35 <ttx> I have to stay awake at 11pm to run it :)
08:17:42 <asalkeld> happy to be there, but not fun waking up and it's not on
08:18:05 <ttx> sure
08:18:11 <ttx> johnthetubaguy: around?
08:18:15 <asalkeld> ok, that's all i have
08:18:21 <asalkeld> thanks ttx
08:18:22 <johnthetubaguy> ttx: good morning
08:18:31 <ttx> asalkeld: looks like you're in good shape. Just get me that last feature patch in
08:18:35 <ttx> #topic Nova
08:18:56 <ttx> https://launchpad.net/nova/+milestone/kilo-rc1
08:19:12 <ttx> johnthetubaguy: all done with FFEs ?
08:19:28 <johnthetubaguy> yes, I pushed out the online migration stuff on friday monring
08:19:32 <ttx> #info No more FFEs
08:20:12 <ttx> How much final is the list of RC1 bugs ?
08:20:17 <johnthetubaguy> I haven't looked closely at the bug list, honestly, in the casting the net out wide part of the process (is my current excuse)
08:20:54 <johnthetubaguy> I guess a few of those can get bumped though
08:21:00 <ttx> I know a few nova people are staying on top of bugs
08:21:12 <johnthetubaguy> and I could add the kilo-rc-potential tag for the big ones
08:21:38 <johnthetubaguy> yes, sdague is doing his excellent work there, so I don't want to stop that happening at this point
08:21:58 <johnthetubaguy> I am hoping on thursday in the nova meeting we can sync up and see how we are looking
08:22:03 <ttx> johnthetubaguy: Did someone go through the "Critical/High" list to spot release-critical material yet ?
08:22:46 <ttx> (no idea if the current list is the result of a triaging work or just a random list)
08:22:54 <johnthetubaguy> ttx: I am not sure anyone has done it systematically yet, mostly as the list is so small
08:23:08 <johnthetubaguy> I think its the result of random triage work, if that makes sense
08:23:30 <ttx> OK, so this week we need to come up with a clearer list of RC1 blockers
08:23:34 <ttx> so that we know how far we are
08:23:42 <johnthetubaguy> +1
08:24:10 <ttx> Then make sure all targets have assignees
08:24:24 <ttx> https://bugs.launchpad.net/nova/+bug/1431291 is unassigned right now
08:24:27 <openstack> Launchpad bug 1431291 in OpenStack Compute (nova) "Scheduler Failures are no longer logged with enough detail for a site admin to do problem determination" [High,Confirmed]
08:24:50 <ttx> Sylvain was workign on it but removed himself
08:24:55 <johnthetubaguy> I thought sdague was going to do that, I must reach out and see where its at
08:24:56 <johnthetubaguy> ah...
08:25:20 <ttx> #info 11 bugs on list, but list is likely incomplete
08:25:59 <ttx> johnthetubaguy: ok, any red flag I should know about ?
08:26:09 <johnthetubaguy> I think you spotted the big one
08:26:27 <johnthetubaguy> the rc1 bug list not really being known at this point
08:26:50 <ttx> Once it's done, you just need to watch incoming new bugs, which makes the job easier
08:27:03 <ttx> but the initial scrub is a lot of work :)
08:27:35 <johnthetubaguy> yeah, we have failed to keep a long term bug czar, and its showing a bit I guess
08:28:00 <ttx> johnthetubaguy: ok, if you don't have anythig else, I'll be talking to you later
08:28:03 <johnthetubaguy> we went for a trivial patch list, which has had some success, but we need to deal with the harder list soon
08:28:10 <johnthetubaguy> ttx: thanks, thats all for now
08:28:17 <ttx> cheers
08:28:19 <johnthetubaguy> have a good day
12:00:12 <ttx> eglynn: o/
12:00:30 <eglynn> ttx: hey
12:00:33 <ttx> #topic Ceilometer
12:00:35 <eglynn> #link https://launchpad.net/ceilometer/+milestone/kilo-rc1
12:00:45 <eglynn> looking good so far
12:00:49 <ttx> It is bug-free!
12:01:07 <eglynn> let's not jump on the tag yet though
12:01:17 <ttx> eglynn: did you go through reported bugs and see if there would be anything else blocking ?
12:01:18 <eglynn> in case something arises in the distro level testing of kilo3
12:01:38 <ttx> right, I wouldn't tag before EOW at the minimum
12:01:47 <eglynn> yep, nothing absolutely critical as yet
12:01:48 <ttx> so that distro testing catches up
12:01:48 <eglynn> cool
12:01:58 <eglynn> yep, that sounds reasonable
12:02:15 <ttx> But good to see you're in such a good shape
12:02:27 <eglynn> cool
12:02:52 <ttx> #info No FFEs, buglist empty, candidate for early tagging (end of week / start of next)
12:03:22 <ttx> eglynn: We'll talk elections and design summit scheduling at the Cross-project meeting today
12:03:28 <ttx> That is all I have for you.
12:03:33 <eglynn> ttx: coolness
12:03:41 <eglynn> thanks for your time
12:03:44 <ttx> no warning / red flag on your side ?
12:03:56 <eglynn> nope
12:03:59 <ttx> alright then
12:04:05 <ttx> SergeyLukjanov: ready when you are
12:10:16 <SergeyLukjanov> ttx, hey, I'm here
12:10:22 <ttx> #topic Sahara
12:10:31 <ttx> #link https://launchpad.net/sahara/+milestone/kilo-rc1
12:10:33 <SergeyLukjanov> #link http://launchpad.net/sahara/+milestone/kilo-rc1
12:10:55 <SergeyLukjanov> so, we have 2/3 blueprints merged and the last one is stuck on the one base CR
12:10:57 <ttx> We are left with default-templates
12:11:34 <SergeyLukjanov> yeah, IMO if it'll be not merged till the end of week - defer to liberty
12:11:48 <SergeyLukjanov> regarding issues - mostly all of them are docs
12:12:07 <SergeyLukjanov> btw is it ok to merge docs / tests after rc1 or better to avoid it?
12:12:12 <ttx> So it is stuck on https://review.openstack.org/#/c/163649/ ?
12:12:25 <SergeyLukjanov> ttx, yup
12:12:39 <ttx> #info default-templates blocked on https://review.openstack.org/#/c/163649/
12:13:03 <ttx> SergeyLukjanov: how about we defer it to liberty if it's still not approved by Thursday ?
12:13:17 <SergeyLukjanov> ttx, ack
12:13:20 <SergeyLukjanov> ttx, I'm ok with it
12:13:23 <ttx> That gives one extra day to pass gate in case of problems
12:13:42 <ttx> #info default-templates FFE extended to Thursday (for patch approval) and Friday (for patch merging)
12:14:10 <ttx> On the bugs side...
12:14:31 <SergeyLukjanov> btw is it ok to merge docs after rc1 or better to avoid it?
12:14:32 <ttx> Is it the blockers list, or do you still have work to do to parse Launchpad bugs ?
12:14:40 <ttx> better avoid it
12:14:48 <ttx> RC1 is in theory releasable
12:15:04 <SergeyLukjanov> I've cleaned up the lp bugs, only important stuff is in the list
12:15:05 <ttx> So if docs are missing and are release-critical, we need to wait until they land to tag
12:15:12 <ttx> ok
12:15:15 <SergeyLukjanov> and kilo-rc-potential is only on three bugs
12:15:22 <ttx> #info 7 bugs on the RC list
12:15:27 <SergeyLukjanov> I'm now evaluating their real importance
12:15:37 <SergeyLukjanov> ttx, ack
12:15:57 <ttx> OK, any red flag, or issue I should be aware of ?
12:16:24 <SergeyLukjanov> ttx, nope
12:16:37 <ttx> We'll discuss PTL elections and design summit scheduling at the cross-project meeting tonight
12:16:42 <SergeyLukjanov> ttx, it looks like everything is working ok atm
12:16:49 <ttx> Though it's late for you, so you can read the logs after
12:16:49 <SergeyLukjanov> ttx, okay, I'll be their
12:17:13 <ttx> OK, talk to you later then
12:17:56 <SergeyLukjanov> ttx, thank you!
12:18:04 <ttx> There won't be an Oslo update today for those following at home
12:18:08 <ttx> as Doug is travelling
12:18:25 <ttx> next up, mestery at 13:45 utc
12:59:27 <sdague> ttx: so, I just noticed the following patch - https://review.openstack.org/169289 - which means that there has been 0 full stack testing on the glance artifacts service up until this point
12:59:37 <sdague> does that still have an FFE?
12:59:58 <ttx> sdague: was about to kill ittoday in my sync with Nikhil
13:00:09 <sdague> ok, good to know
13:01:22 <ttx> sdague: whil you're around -- anything we need to do in requirements now that we are in HardDepFreeze ? Apart from ignorning requests ?
13:01:39 <ttx> Time to get the requirements sync merged I guess
13:03:36 <sdague> honestly, I think just making sure projects merge stuff
13:03:51 <ttx> rigth, that was my conclusion too, just doublechecking
13:03:56 <sdague> as far as I know we just need to reject except for bug fixes
13:05:22 <sdague> https://review.openstack.org/#/c/168187 - o_O ?
13:05:37 <sdague> you'd think folks would know better than pushing bumps now
13:06:18 <sdague> ttx: https://review.openstack.org/#/c/169132 does need to land, someone typoed a thing because of a bad font
13:07:00 <ttx> auth-token-use-client is probably liberty material
13:07:23 <ttx> ok approving now
13:07:53 <ttx> done
13:09:08 <sdague> https://review.openstack.org/#/c/166664/ is also probably safe, it's a remove
13:09:11 <sdague> of a test tool
13:12:44 <ttx> agreed
13:45:24 <ttx> mestery: around?
13:45:29 <mestery> ttx: o/
13:45:48 <ttx> #topic Neutron
13:45:52 <ttx> #link https://launchpad.net/neutron/+milestone/kilo-rc1
13:46:02 <ttx> I see 2 FFEs still up
13:46:16 <mestery> Yes
13:46:19 <mestery> Let me explain :)
13:46:25 <ttx> We said "subnet-allocation -- should land before next 1:1, reconsider if not"
13:46:45 <mestery> ttx: A problem came up in that we need to implement subnet as an extension, so it's being reworked now
13:46:49 <mestery> I expect that to land by Friday
13:46:55 <ttx> "multiple-ipv6-prefixes -- related to ipv6-router, needs to fully land by next Tuesday"
13:46:57 <mestery> at the latest
13:47:13 <mestery> That one is likely to be marked as implemented, I need to sync with the folks working on it
13:47:27 <mestery> They had an action to fill in the workpage on LP but didn't yet
13:47:27 <mestery> So, subnet is the last one
13:48:12 <mestery> I think we can safely land subnet pools by this week yet
13:48:17 <ttx> OK, if that is the only one, I guess we can give it a few more days
13:48:44 <mestery> Yes, that's it.
13:48:48 <mestery> The team worked hard to get the rest in!
13:48:58 <ttx> the earlier the better, we won't be able to stretch that past this week
13:48:59 <mestery> Honestly, I'm super proud of all the work around testing and stability we've done.
13:49:03 <mestery> Ack
13:49:28 <ttx> #info subnet-allocation slightly delayed, needs to fully land before Friday
13:49:39 <ttx> Looking at the bugs side now
13:49:53 <ttx> #info 14 targeted RC1 bugs
13:50:03 <mestery> Yes, today I will start removing the bottom of those
13:50:04 <ttx> One of them is missing an assignee
13:50:19 <mestery> Yes, the one without an assignee is because the person on it said they could no longer allocate time for it
13:50:20 <ttx> Did you go through the neutron bug list to build this ?
13:50:27 <mestery> I'm trying to ifind someone for it
13:50:30 <ttx> or is there some bug scrubbing to do ?
13:50:41 <mestery> I have to do some slight bug scrubbing, but for the most part this is it.
13:50:48 <mestery> Some new things have been appearing as they always do :)
13:50:48 <ttx> to make sure nothing flies below radar
13:51:21 <ttx> ok, keep it updated then
13:51:30 <mestery> Is the plan to try and tag early next week?
13:51:56 <ttx> I'd say "next week" is good enough
13:52:01 <mestery> Ack
13:52:25 <ttx> early risers are expected end of this week, normal people newt week, late people the week after :)
13:52:32 <mestery> lol
13:52:37 * mestery targets being normal
13:52:51 <ttx> yes, norpmal is good
13:52:58 <ttx> normal is good too
13:53:01 <mestery> lol
13:53:12 <ttx> what else...
13:53:27 <ttx> we'll be discussing pTl election and design summit scheduling at the cross-project meeting today
13:53:45 <mestery> Yes, I saw the email!
13:54:01 <mestery> Next week at the Neutron meeting I plan to open up the design summit melee for folks :)
13:54:04 <ttx> any red flag or problem potentially impacting release, that wI should be aware of ?
13:54:14 <mestery> Nothing at this point
13:54:27 <ttx> Alright, I'll be talking to you soon. Hurry to next meeting :)
13:54:32 <mestery> lol :)
13:54:39 <mestery> Thanks sir! HAve a great day and talk soon.
14:19:42 <ttx> nikhil_k: ready when you are
14:20:20 <nikhil_k> ttx: hi
14:20:23 <ttx> #topic Glance
14:20:31 <ttx> #link https://launchpad.net/glance/+milestone/kilo-rc1
14:20:40 <ttx> So... our 2 FFEs live
14:20:56 <ttx> Last week we said we'd defer both if they failed to make it by now
14:21:26 <ttx> So unless they are already in the pipe... not sure waiting more would actually help
14:21:48 <nikhil_k> ttx: hmm, double checking if CIS got some traction
14:21:52 <nikhil_k> Artifacts is stuck
14:22:13 <ttx> I could grant 1-2 more days to CIS if it's close
14:22:31 <nikhil_k> ttx: seems like, this one is pending https://review.openstack.org/#/c/161621/
14:22:36 <ttx> artifacts looks further away, and also as I wrote, not sure of the benefit to land it in-release rather than early in liberty
14:22:36 <nikhil_k> and some documentation patches
14:22:57 <nikhil_k> ttx: Yeah, I mentioned the same thing to the developers working on it
14:23:14 <nikhil_k> and made them aware about your stance on the same
14:23:33 <ttx> Looking into CIS
14:23:51 <nikhil_k> so, whatever you decide on Artifacts should work. I'm tentative too after reading the testing messge earlier
14:24:39 <ttx> If CIS is only missing https://review.openstack.org/#/c/161621/, I'd grant it until Thursday to fully merge
14:24:53 <ttx> Artifacts I'd axe at this point
14:24:56 <nikhil_k> ttx: hmm, there seem to be some outside of Glance. Please see this too https://review.openstack.org/#/q/topic:bp/catalog-index-service,n,z (if you haven't already)
14:25:47 <ttx> So the issue with the client fix is that it will trigger a requirements update, and we are at HardDepFreeze
14:25:54 <nikhil_k> ttx: ok, sure about Artifacts. Can you please educate me some on the different announcements that need to be made in the public? Like specs to L, BP to L and ...?
14:26:18 <ttx> You can already open specs to L
14:26:32 <ttx> master branch will switch to L as soon as we tag RC1
14:27:10 <nikhil_k> ok, sounds good. I will send a note that the rest of the development can happen in L and mark the patches with -2 then
14:27:32 <ttx> sdague: an opinion on https://review.openstack.org/#/c/146074/ wrt. new client release and the cortresponding requirements mess ?
14:27:42 <nikhil_k> and indicate this info to the necessary people (about RC1, specs etc)
14:27:50 <ttx> Looks like that FFE would trigger a new client release
14:28:24 <ttx> which we'd had to give a HDF exception to
14:29:22 <ttx> and then which other projects would have to sync requirements for
14:29:31 <nikhil_k> eh
14:29:33 <ttx> so that one impacts beyond Glance
14:29:37 <nikhil_k> ok
14:29:51 <nikhil_k> That's messy for sure
14:30:06 <ttx> maybe better to consider it a L feature too, after all
14:30:20 <nikhil_k> ttx: ok, I think we can create a new spec for client and see it in L
14:30:29 <nikhil_k> Will send out the info
14:30:41 <ttx> sounds good. Split the client part, land the server part
14:31:15 <nikhil_k> cool
14:31:25 <ttx> #info catalog-index-service gets until Thursday to merge the last serverside bits. Client work should be split and done in Liberty
14:31:26 <nikhil_k> and the rest of the devstack ones?
14:31:47 <ttx> That can land without requiring an exception. Tests are good
14:32:00 <nikhil_k> ttx: cool. one more https://review.openstack.org/157209
14:32:07 <nikhil_k> Thought that isn't really WIP
14:32:28 <nikhil_k> ttx: can we get that one in?
14:32:33 <ttx> Test addition is not considered a feature
14:32:43 <nikhil_k> ok, sounds good
14:32:44 <ttx> so yes, it can land until RC1
14:33:15 <nikhil_k> Thanks for letting me know, I would request removal of the bp tag from the commit message and ask for a bug instead
14:33:16 <ttx> nikhil_k: Did you have some time to triage the bugs and find release blockers ?
14:33:28 <nikhil_k> ttx: yes, please let's do that
14:33:34 <nikhil_k> sorry couldn't get to it earlier
14:34:00 <ttx> Would be good to work on it soon, so that we know how far we are from RC1
14:34:20 <ttx> Maybe something you could delegate
14:34:47 <ttx> #info only 10 bugs in RC buglist but that one is still incomplete
14:34:56 <nikhil_k> ttx: oh, I read that you wanted to do it now. Sorry context switched from the use of language my team does ..
14:35:00 <ttx> I need to jump to my next customer
14:35:06 <ttx> otherwise we could have ;)
14:35:19 <nikhil_k> ttx: sure :)
14:35:34 <ttx> nikhil_k: Let's talk again on Thursday, hopefully FFE will be done and buglist built
14:35:52 <nikhil_k> yeah, catch ya then
14:35:55 <nikhil_k> Thanks!
14:35:56 <ttx> cheers
14:36:00 <ttx> thingee: around?
14:36:11 <thingee> ttx: hi
14:36:15 <ttx> #topic Cinder
14:36:22 <ttx> Sorry for running late
14:36:29 <ttx> #link https://launchpad.net/cinder/+milestone/kilo-rc1
14:36:30 <thingee> no problem
14:36:50 <ttx> So.. what date did you finally give for driver readdition ?
14:37:06 <thingee> april 6th http://lists.openstack.org/pipermail/openstack-dev/2015-March/059990.html
14:37:36 <ttx> Looks good. Correspnds to the end of the "normal" RC1s (the week after that is kept for stragglers)
14:38:17 <ttx> #info Some drivers may be reintroduced, deadline Apr 6
14:38:23 <ttx> Looking at the bug list
14:38:31 <ttx> #info 7 targeted RC bugs
14:38:34 <thingee> I've been happy with the progress drivers are making for being readded.
14:38:48 <ttx> Did you triage most bugs to find those 7 ?
14:39:07 <sdague> ttx: I think - https://review.openstack.org/#/c/146074/ is too late
14:39:20 <thingee> I am actively triaging yes.
14:40:05 <ttx> sdague: right, nikhil_k and I decided to defer it
14:40:19 <ttx> thingee: ok, good, looks like you have stuff under control
14:40:32 <ttx> Any red flag, besides the late driver readdition ?
14:42:20 <thingee> nope. we have some nice bad bugs but patches are posted.
14:42:27 <thingee> glad they're being found now.
14:42:30 <ttx> ok, great! ttyl
14:42:37 <ttx> david-lyle: around?
14:42:41 <thingee> thanks
14:51:10 <ttx> david-lyle might have missed the European DST memo
14:52:43 <david-lyle> ttx: o/
14:52:49 <ttx> #topic Horizon
14:52:58 <ttx> #link https://launchpad.net/horizon/+milestone/kilo-rc1
14:53:11 <ttx> I see two FFEs still in there, unfortunately assigned to the same person
14:53:19 <ttx> Last week we said:
14:53:44 <ttx> federated-identity -- late feature catch-up, ideally would merge before Tuesday next week
14:53:51 <ttx> angularize-identity-tables -- needs to be finalized before next week
14:54:02 <ttx> How far are those from landing ?
14:54:21 <ttx> angularize-identity-tables seems to have plenty of patches left
14:54:36 <david-lyle> identity tables is farther
14:54:55 <ttx> Federated identity seems to hinge on https://review.openstack.org/#/c/151842/
14:55:31 <ttx> in which case we could give it a couple more days to go through the CI pipe
14:55:54 <david-lyle> I think Federated Identity can land
14:55:55 <ttx> How about we defer angularize-identity-tables and give federated-identity until Friday ?
14:56:02 <ttx> does that make sense ?
14:56:20 <david-lyle> Yes, that seems appropriate given the timeframe
14:56:33 <ttx> OK, I'll let you defer the table stuff
14:56:37 <david-lyle> will do
14:56:53 <ttx> #info federated-identity is really close, FFE extended until Friday
14:57:13 <ttx> #info 11 targeted bugs on the RC buglist
14:57:29 <ttx> Is tahht all the known blockers, or the triage work is still a todo ?
14:57:41 <ttx> that*
14:58:03 <david-lyle> some of those will clean out with removing the tables bp
14:58:29 <david-lyle> that's all I am aware of
14:58:52 <ttx> ok, good
14:58:58 <ttx> Looks like we should be on time here too
14:59:11 <david-lyle> Yes, I think so
14:59:12 <ttx> Any red flag I should know of ?
14:59:25 <david-lyle> other than the gate fiasco, no
14:59:31 <ttx> heh, that happens
14:59:38 <ttx> alright, have a good week then
14:59:44 <david-lyle> thanks, you too
15:00:11 <david-lyle> ttx: did want to ask about horizon decomposition
15:00:30 <david-lyle> but you may not have enough time right now
15:00:47 <ttx> Hmm, could you ping me tomorrow ? About to jump on a call right now
15:00:58 <david-lyle> yes, sure
15:01:01 <ttx> and today is meeting-crazy day
15:01:06 <ttx> ok, great
15:01:14 <david-lyle> ack
15:01:18 <david-lyle> will ping tomorrow
15:09:44 <devananda> ttx: o/
15:14:47 <ttx> devananda: moved our sync one hour later
15:14:54 <ttx> devananda: on a call right now
15:15:00 <devananda> oh. darn time changes. I thought it was now ... thanks
15:21:37 <Kiall> ttx: heya - can you settle a Q for me? At what point do we branch stable/kilo and move master -> icehouse? I seem to remember some changes recently on this..
15:37:59 <ttx> Kiall: when we tag RC1 we cut the kilo release branch from it and let master evolve in liberty
15:38:25 <ttx> devananda: I'm of the call now, we can sync now if you want
15:38:29 <ttx> off*
15:45:29 <Kiall> ttx: perfect, for some reason I thought it had changed to cut stable/kilo after kilo final was released
15:46:42 <ttx> Kiall: it's also true
15:47:02 <ttx> We cut proposed/kilo for release candidates, and switch to stable/kilo once it's stable/released
15:47:32 <Kiall> hah - i thought proposed/foo was dropped?
15:47:32 * Kiall needs to re-read the branching wiki page
15:48:01 <ttx> Kiall: no.. "milestone-proposed" was dropped.
15:48:11 <ttx> proposed/foo is still alive
15:48:39 <ttx> https://wiki.openstack.org/wiki/ReleaseTeam/How_To_Release#proposed.2F.24SERIES_branch_cut_.28switch_master_to_next_version.29
15:48:52 <ttx> morganfainberg: ready when you are
15:49:14 * morganfainberg wakes up.
15:49:18 <morganfainberg> Hi :)
15:49:30 * ttx violently shakes morganfainberg
15:49:45 <morganfainberg> Lol.
15:49:46 <ttx> #topic Keystone
15:49:52 * ttx dcc sends coffee
15:49:58 <morganfainberg> Yessssssss
15:50:11 <ttx> #link https://launchpad.net/keystone/+milestone/kilo-rc1
15:50:18 <morganfainberg> Coffee will happen right after this sync up
15:50:19 <ttx> I see one FFE still standing there
15:50:37 <morganfainberg> Yes. There is one outstanding review and a new bug / issue to address.
15:50:46 <ttx> interestingly we didn't mention that one last week
15:50:50 <morganfainberg> That will be discussed today w/ henrynash
15:51:00 <morganfainberg> We did, domain-sql?
15:51:34 <morganfainberg> It was on the list of cleanup/final patches for a feature to land.
15:51:36 <ttx> I failed to #info it correctly
15:51:40 <morganfainberg> Ahh
15:51:43 <ttx> "should not take more than a week"
15:52:10 <ttx> Ah no, here it is: domain-config-ext -- to be fully merged before Tuesday next week
15:52:36 <morganfainberg> Yeah. It should land today/tomorrow. Just need to address some comments.
15:52:43 <morganfainberg> And add some more sql logic
15:52:48 <ttx> OK, let's give it until Thursday
15:52:53 <morganfainberg> ++
15:52:58 <morganfainberg> It's close.
15:53:02 <ttx> #info domain-config-ext - FFE extended to Thursday
15:53:21 <ttx> #info 13 bugs on the RC buglist
15:53:26 <morganfainberg> Bugs are mostly in shape. Might see one more removed from the list.
15:54:00 <morganfainberg> The rest I'm hoping to see in/progress by shortly  and/or committed for those in progress.
15:54:06 <ttx> Did you run through keystone bugs to find the rc stuff ?
15:54:20 <ttx> i.e. is that list considered the known RC issues ?
15:54:33 <morganfainberg> Yes. There might be one less bug.
15:54:41 <morganfainberg> By the end of he day
15:54:44 <ttx> Alright, looks like you're on track
15:54:56 <ttx> Goal for "normal" projects is to tag RC1 sometimes next week
15:55:20 <morganfainberg> Yep. I hope we are on track for that
15:55:30 <ttx> Alright. I'll talk to you next week, then
15:55:38 <morganfainberg> Have a good day!
15:55:44 <ttx> have a GREAT day!
15:55:53 * morganfainberg scurries off for caffeine so the day can be great :)
15:55:56 <ttx> notmyname: ready when you are
16:06:08 <notmyname> ttx: here
16:06:09 <notmyname> ttx: sorry for the delay. was biking in
16:07:24 <ttx> #topic Swift
16:07:39 <ttx> notmyname: I created the branch, hopefully you wanted it on HEAD
16:07:48 <notmyname> thank you. yes. off of master
16:07:57 <ttx> cool, guessed right
16:08:07 <ttx> so it should be all set
16:08:14 <notmyname> so ya, that's what we're doing :-)
16:08:24 <ttx> Did you settle on a version number ? I'd like to create the milestone page
16:08:47 <notmyname> 2.3.0
16:09:43 <notmyname> this week (ie today, probably) we'll freeze master until the feature/ec_review lands
16:09:43 <ttx> ok, created https://launchpad.net/swift/+milestone/2.3.0-rc1
16:10:01 <ttx> you can target RC bugs to it if you want to track those
16:10:12 <ttx> ok, sounds good
16:10:22 <notmyname> I'll let you know asap when master is ready for the RC
16:10:32 <notmyname> right now, we're targeting the end of next week (4/10)
16:10:47 <notmyname> but it depends on the integration work this week and next
16:11:01 * notmyname may not get much sleep
16:11:04 <ttx> sounds good
16:11:36 <notmyname> when do you expect to have the summit schedule assignments done?
16:11:49 <ttx> notmyname: I plan to discuss this at the cross-project meeting today
16:12:15 <ttx> I expect to have the final list of projects around April 7, so to finalize assignments ~April 10
16:12:16 <notmyname> oh the suspense ;-)
16:12:23 <notmyname> ok
16:12:54 <ttx> But we likely have less than expected, so projects should get what they asked for
16:13:01 <notmyname> yay
16:13:29 <ttx> more on the discussion at the meeting
16:13:32 <notmyname> ok
16:13:36 <notmyname> anything else?
16:13:53 <ttx> nope, I'll let you go back to work, much to do :)
16:13:57 <notmyname> indeed
16:14:00 <notmyname> have good evening
16:14:10 <ttx> thx!
16:14:15 <ttx> devananda: around?
16:20:14 <ttx> SlickNik: want to jump ahead ?
16:20:40 <SlickNik> ttx: sure thing
16:20:46 <ttx> #topic Trove
16:20:56 <ttx> #link https://launchpad.net/trove/+milestone/kilo-rc1
16:21:04 <ttx> #info All FFEs set
16:21:17 <SlickNik> Yup, all done by end of last week.
16:21:17 <ttx> #info 8 bugs on the RC list
16:21:23 <SlickNik> Hurray for deadlines :)
16:21:36 <ttx> nothing like a good deadline!
16:21:53 <SlickNik> Yup, we're pretty much locked down, and doing testing / bugfixes at this point.
16:22:02 <ttx> Do you think that list represents all the known issues ? Did you go on a trigaiung rampage ?
16:22:14 <ttx> triaging*
16:22:46 <SlickNik> I did triage of the recent issues opened. I'm planning on doing a more in-depth one today.
16:23:02 <ttx> ok great
16:23:03 <ttx> Looks like we could hit the RC1 sweet spot in the middle of next week for you
16:23:27 <SlickNik> ++
16:23:32 <ttx> We'll discuss PTl election and summit scheduling at the cross-project meeting today
16:23:42 <ttx> in case you want to join
16:23:45 <SlickNik> Will keep a vigilant eye out for new issues that may crop up.
16:24:02 <ttx> Anything I should be aware of ?
16:24:04 <SlickNik> Will definitely be there.
16:24:31 <SlickNik> We're marching ahead pretty well at this point — nothing more from my side.
16:24:43 <ttx> alright! Thanks!
16:24:49 <ttx> devananda: around now?
16:25:28 <SlickNik> Thanks ttx. See you in the afternoon!
16:27:37 <devananda> ttx: hi!
16:27:41 <ttx> #topic Ironic
16:27:50 <ttx> #info https://launchpad.net/ironic/+milestone/kilo-rc1
16:27:50 <devananda> was in a taxi
16:27:55 <ttx> devananda: still traveling?
16:28:00 <devananda> yarr :(
16:28:20 <devananda> so that list is overly aggressive - i've been targeting things to get the team to take notice
16:28:28 <devananda> we'll likely untarget some of that, and fix some of that
16:28:41 <devananda> still aiming for one week from today as our first RC1
16:28:50 <devananda> have a question on translations ...
16:28:57 <ttx> Right, refine it as you go so that it contains all release blockers
16:29:09 <devananda> #link https://www.transifex.com/projects/p/ironic/
16:29:12 <ttx> also make sure you have people assigned to each, otherwise it tends not to get done
16:29:17 <devananda> indeed
16:29:34 * ttx curls in foetal position screaming Translations! Translations!
16:29:41 <devananda> :-/
16:29:55 <ttx> someone in a white uniform comes and carries ttx away
16:30:06 <devananda> right. let's not talk about that :)
16:30:18 <ttx> 14% French! Not me
16:30:38 <ttx> 26% Australian english. That must not be too hard
16:31:03 <devananda> given the 75% translated bar for inclusion
16:31:12 <devananda> i'm inclined to not worry about it at all
16:31:28 <devananda> unless someone jumps up and down saying they really want to translate ironic
16:31:32 <devananda> it == string freeze
16:31:57 <ttx> You could publish a call for translations, but at this stage I'd say you're a bit far from the bar
16:32:16 <ttx> so arguably yes, the pain of a string change is probably limited
16:32:27 <ttx> Should still avoid gratuitous changes, but I'd say exceptions shall be granted
16:32:42 <ttx> since those are unlikely to affect the end result
16:32:49 <devananda> yea, avoiding gratutios changes +1
16:32:55 <devananda> cool
16:33:31 <ttx> devananda: I'd still comunicate changes if you push some. That could raise awareness on ironic needing help to be translated
16:33:47 <ttx> i.e. "we changed that string, in case anyone cares"
16:33:59 <devananda> gotcha. what's the maailing list / tag for that?
16:34:18 <ttx> I'd say openstack-dev, with [stringfreeze] in the subject
16:34:51 <devananda> k k
16:34:57 <ttx> That is all. We'll discuss summit scheduling and PTL elections at the cross-project meeting today
16:35:19 <ttx> anything else I should worry about?
16:35:35 <devananda> nope. not unless you want to :)
16:35:45 * ttx happily stays unaware
16:36:07 <ttx> devananda: keep on refining that buglist, talk to you later
16:36:17 * devananda tries to find time to takes a nap before the TC meeting
16:36:22 <devananda> ciao!
16:36:23 <ttx> #endmeeting