Tuesday, 2015-03-31

ttxasalkeld: grabbing coffee, I'll be there in a minute08:00
asalkeldhi08:01
asalkeldok08:01
ttx#startmeeting08:04
openstackttx: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'08:04
ttx#startmeeting ptl_sync08:04
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:04
openstackThe meeting name has been set to 'ptl_sync'08:04
ttx#topic Heat08:04
ttx#link https://launchpad.net/heat/+milestone/kilo-rc108:04
asalkeldhi ttx08:04
*** zz_johnthetubagu is now known as johnthetubaguy08:04
ttxasalkeld: o/08:04
ttxso let's see where thoise two FFEs stand08:05
asalkelddam that one bp was approved, but failed on merge08:05
ttxconvergence-push-data was supposed to be completed before end of last week08:05
asalkeldhttps://review.openstack.org/#/c/161306/08:05
* ttx looks08:05
asalkeldyeah, needs rebase i think08:05
asalkeldttx it's not super important - if you need to cut a release we can push it08:06
ttxneeds rebase ? Or just recheck ?08:06
asalkeldttx: i just noticed, i'll check up on it08:07
asalkeldttx i just pushed the mistral resources out08:07
ttxIf it's in pipe, it's fine08:07
ttx(the convergence stuff)08:07
asalkeldok08:07
asalkeld so most of those bugs are close08:07
ttxif more work is needed (than just rechecks) then we would push it out08:07
asalkeldi am fine with that08:08
asalkeldttx: when do you want to do the rc1?08:08
ttxso please have a look after the sync08:08
asalkeld(will do)08:08
ttxas soon as your critical bug list is empty08:08
ttxCould be at the end of the week, could be next week08:09
asalkeldok08:09
ttxLooks like you parsed the bug list, so your RC1 list should be pretty complete08:09
asalkeldyeah not a big deal, most look ok08:10
ttx#info convergence-push-data is in the pipe, so FFE extended. If more work needed, will be deferred08:10
asalkeldi'll chase up the really important ones08:10
ttx#info 6 bugs left08:10
ttxAnything else on your side ? Red flags ?08:11
asalkeldno, all looks ok to me08:12
ttxWe'll discuss PTL election season and the design summit scheduling at the cross-poject meeting08:12
asalkeld(note 5 bugs now)08:12
ttxin case you can join08:12
asalkeldok08:12
asalkeldttx: note i'll take a week off and get stevebaker to cover08:12
asalkeldi'll email you the exact time08:12
ttxasalkeld: 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
asalkeldok ttx08:13
asalkeldi'd say even now it's fine08:13
ttxthen you discover new embarassing bugs and you reboot the process for a RC2 :)08:13
asalkeldyeah08:13
ttxtoo early and you miss the late bug reports08:13
asalkeldgood point08:14
ttxso you don't want to cut too early (that's a recipe for an early RC2 round :)08:14
asalkeldso maybe the end of the week?08:14
ttxbut yeah, end of this week/start of next week is probably fine. Early is not a bad thing08:14
asalkeldcool, i am easy with those 2 options08:15
asalkeldttx: there is project meeting this week?08:15
ttxasalkeld: starting with RC2 you fix in master and backport to the release branch, so it's more work fixing issues08:15
ttxasalkeld: yes, see above08:16
asalkeldcool08:16
ttx"We'll discuss PTL election season and the design summit scheduling at the cross-project meeting"08:16
asalkeld(i have to wake up at 5:45am to make it)08:16
asalkeldjust making sure08:16
ttxyou can catch up with the log08:17
asalkeldyeah, bad form to miss it08:17
ttxI have to stay awake at 11pm to run it :)08:17
asalkeldhappy to be there, but not fun waking up and it's not on08:17
ttxsure08:18
ttxjohnthetubaguy: around?08:18
asalkeldok, that's all i have08:18
asalkeldthanks ttx08:18
johnthetubaguyttx: good morning08:18
ttxasalkeld: looks like you're in good shape. Just get me that last feature patch in08:18
ttx#topic Nova08:18
ttxhttps://launchpad.net/nova/+milestone/kilo-rc108:18
ttxjohnthetubaguy: all done with FFEs ?08:19
johnthetubaguyyes, I pushed out the online migration stuff on friday monring08:19
ttx#info No more FFEs08:19
ttxHow much final is the list of RC1 bugs ?08:20
johnthetubaguyI 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
johnthetubaguyI guess a few of those can get bumped though08:20
ttxI know a few nova people are staying on top of bugs08:21
johnthetubaguyand I could add the kilo-rc-potential tag for the big ones08:21
johnthetubaguyyes, sdague is doing his excellent work there, so I don't want to stop that happening at this point08:21
johnthetubaguyI am hoping on thursday in the nova meeting we can sync up and see how we are looking08:21
ttxjohnthetubaguy: Did someone go through the "Critical/High" list to spot release-critical material yet ?08:22
ttx(no idea if the current list is the result of a triaging work or just a random list)08:22
johnthetubaguyttx: I am not sure anyone has done it systematically yet, mostly as the list is so small08:22
johnthetubaguyI think its the result of random triage work, if that makes sense08:23
ttxOK, so this week we need to come up with a clearer list of RC1 blockers08:23
ttxso that we know how far we are08:23
johnthetubaguy+108:23
ttxThen make sure all targets have assignees08:24
ttxhttps://bugs.launchpad.net/nova/+bug/1431291 is unassigned right now08:24
openstackLaunchpad 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
ttxSylvain was workign on it but removed himself08:24
johnthetubaguyI thought sdague was going to do that, I must reach out and see where its at08:24
johnthetubaguyah...08:24
ttx#info 11 bugs on list, but list is likely incomplete08:25
ttxjohnthetubaguy: ok, any red flag I should know about ?08:25
johnthetubaguyI think you spotted the big one08:26
johnthetubaguythe rc1 bug list not really being known at this point08:26
ttxOnce it's done, you just need to watch incoming new bugs, which makes the job easier08:26
ttxbut the initial scrub is a lot of work :)08:27
johnthetubaguyyeah, we have failed to keep a long term bug czar, and its showing a bit I guess08:27
ttxjohnthetubaguy: ok, if you don't have anythig else, I'll be talking to you later08:28
johnthetubaguywe went for a trivial patch list, which has had some success, but we need to deal with the harder list soon08:28
johnthetubaguyttx: thanks, thats all for now08:28
ttxcheers08:28
johnthetubaguyhave a good day08:28
*** asalkeld has left #openstack-relmgr-office08:36
-openstackstatus- NOTICE: CI Check/Gate pipelines currently stuck due to a bad dependency creeping in the system. No need to recheck your patches at the moment.08:54
*** ChanServ changes topic to "CI Check/Gate pipelines currently stuck due to a bad dependency creeping in the system. No need to recheck your patches at the moment."08:55
*** flaper87 has quit IRC11:10
*** flaper87 has joined #openstack-relmgr-office11:22
*** flaper87 has quit IRC11:26
*** flaper87 has joined #openstack-relmgr-office11:26
*** ChanServ changes topic to "OpenStack Release Managers office - Where weekly 1:1 sync points between release manager and PTLs happen - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-relmgr-office/"11:50
-openstackstatus- NOTICE: Check/Gate unstuck, feel free to recheck your abusively-failed changes.11:50
*** eglynn has joined #openstack-relmgr-office11:58
ttxeglynn: o/12:00
eglynnttx: hey12:00
ttx#topic Ceilometer12:00
eglynn#link https://launchpad.net/ceilometer/+milestone/kilo-rc112:00
eglynnlooking good so far12:00
ttxIt is bug-free!12:00
eglynnlet's not jump on the tag yet though12:01
ttxeglynn: did you go through reported bugs and see if there would be anything else blocking ?12:01
eglynnin case something arises in the distro level testing of kilo312:01
ttxright, I wouldn't tag before EOW at the minimum12:01
eglynnyep, nothing absolutely critical as yet12:01
ttxso that distro testing catches up12:01
eglynncool12:01
eglynnyep, that sounds reasonable12:01
ttxBut good to see you're in such a good shape12:02
eglynncool12:02
ttx#info No FFEs, buglist empty, candidate for early tagging (end of week / start of next)12:02
ttxeglynn: We'll talk elections and design summit scheduling at the Cross-project meeting today12:03
ttxThat is all I have for you.12:03
eglynnttx: coolness12:03
eglynnthanks for your time12:03
ttxno warning / red flag on your side ?12:03
eglynnnope12:03
ttxalright then12:03
ttxSergeyLukjanov: ready when you are12:04
SergeyLukjanovttx, hey, I'm here12:10
ttx#topic Sahara12:10
ttx#link https://launchpad.net/sahara/+milestone/kilo-rc112:10
SergeyLukjanov#link http://launchpad.net/sahara/+milestone/kilo-rc112:10
SergeyLukjanovso, we have 2/3 blueprints merged and the last one is stuck on the one base CR12:10
ttxWe are left with default-templates12:10
SergeyLukjanovyeah, IMO if it'll be not merged till the end of week - defer to liberty12:11
SergeyLukjanovregarding issues - mostly all of them are docs12:11
SergeyLukjanovbtw is it ok to merge docs / tests after rc1 or better to avoid it?12:12
ttxSo it is stuck on https://review.openstack.org/#/c/163649/ ?12:12
SergeyLukjanovttx, yup12:12
ttx#info default-templates blocked on https://review.openstack.org/#/c/163649/12:12
ttxSergeyLukjanov: how about we defer it to liberty if it's still not approved by Thursday ?12:13
SergeyLukjanovttx, ack12:13
SergeyLukjanovttx, I'm ok with it12:13
ttxThat gives one extra day to pass gate in case of problems12:13
ttx#info default-templates FFE extended to Thursday (for patch approval) and Friday (for patch merging)12:13
ttxOn the bugs side...12:14
SergeyLukjanovbtw is it ok to merge docs after rc1 or better to avoid it?12:14
ttxIs it the blockers list, or do you still have work to do to parse Launchpad bugs ?12:14
ttxbetter avoid it12:14
ttxRC1 is in theory releasable12:14
SergeyLukjanovI've cleaned up the lp bugs, only important stuff is in the list12:15
ttxSo if docs are missing and are release-critical, we need to wait until they land to tag12:15
ttxok12:15
SergeyLukjanovand kilo-rc-potential is only on three bugs12:15
ttx#info 7 bugs on the RC list12:15
SergeyLukjanovI'm now evaluating their real importance12:15
SergeyLukjanovttx, ack12:15
ttxOK, any red flag, or issue I should be aware of ?12:15
SergeyLukjanovttx, nope12:16
ttxWe'll discuss PTL elections and design summit scheduling at the cross-project meeting tonight12:16
SergeyLukjanovttx, it looks like everything is working ok atm12:16
ttxThough it's late for you, so you can read the logs after12:16
SergeyLukjanovttx, okay, I'll be their12:16
ttxOK, talk to you later then12:17
SergeyLukjanovttx, thank you!12:17
ttxThere won't be an Oslo update today for those following at home12:18
ttxas Doug is travelling12:18
ttxnext up, mestery at 13:45 utc12:18
*** eglynn has quit IRC12:54
sdaguettx: 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 point12:59
sdaguedoes that still have an FFE?12:59
ttxsdague: was about to kill ittoday in my sync with Nikhil12:59
sdagueok, good to know13:00
ttxsdague: whil you're around -- anything we need to do in requirements now that we are in HardDepFreeze ? Apart from ignorning requests ?13:01
ttxTime to get the requirements sync merged I guess13:01
sdaguehonestly, I think just making sure projects merge stuff13:03
ttxrigth, that was my conclusion too, just doublechecking13:03
sdagueas far as I know we just need to reject except for bug fixes13:03
sdaguehttps://review.openstack.org/#/c/168187 - o_O ?13:05
sdagueyou'd think folks would know better than pushing bumps now13:05
sdaguettx: https://review.openstack.org/#/c/169132 does need to land, someone typoed a thing because of a bad font13:06
ttxauth-token-use-client is probably liberty material13:07
ttxok approving now13:07
ttxdone13:07
sdaguehttps://review.openstack.org/#/c/166664/ is also probably safe, it's a remove13:09
sdagueof a test tool13:09
ttxagreed13:12
*** eglynn has joined #openstack-relmgr-office13:24
ttxmestery: around?13:45
mesteryttx: o/13:45
ttx#topic Neutron13:45
ttx#link https://launchpad.net/neutron/+milestone/kilo-rc113:45
ttxI see 2 FFEs still up13:46
mesteryYes13:46
mesteryLet me explain :)13:46
ttxWe said "subnet-allocation -- should land before next 1:1, reconsider if not"13:46
mesteryttx: A problem came up in that we need to implement subnet as an extension, so it's being reworked now13:46
mesteryI expect that to land by Friday13:46
ttx"multiple-ipv6-prefixes -- related to ipv6-router, needs to fully land by next Tuesday"13:46
mesteryat the latest13:46
mesteryThat one is likely to be marked as implemented, I need to sync with the folks working on it13:47
mesteryThey had an action to fill in the workpage on LP but didn't yet13:47
mesterySo, subnet is the last one13:47
mesteryI think we can safely land subnet pools by this week yet13:48
ttxOK, if that is the only one, I guess we can give it a few more days13:48
mesteryYes, that's it.13:48
mesteryThe team worked hard to get the rest in!13:48
ttxthe earlier the better, we won't be able to stretch that past this week13:48
mesteryHonestly, I'm super proud of all the work around testing and stability we've done.13:48
mesteryAck13:49
ttx#info subnet-allocation slightly delayed, needs to fully land before Friday13:49
ttxLooking at the bugs side now13:49
ttx#info 14 targeted RC1 bugs13:49
mesteryYes, today I will start removing the bottom of those13:50
ttxOne of them is missing an assignee13:50
mesteryYes, the one without an assignee is because the person on it said they could no longer allocate time for it13:50
ttxDid you go through the neutron bug list to build this ?13:50
mesteryI'm trying to ifind someone for it13:50
ttxor is there some bug scrubbing to do ?13:50
mesteryI have to do some slight bug scrubbing, but for the most part this is it.13:50
mesterySome new things have been appearing as they always do :)13:50
ttxto make sure nothing flies below radar13:50
ttxok, keep it updated then13:51
mesteryIs the plan to try and tag early next week?13:51
ttxI'd say "next week" is good enough13:51
mesteryAck13:52
ttxearly risers are expected end of this week, normal people newt week, late people the week after :)13:52
mesterylol13:52
* mestery targets being normal13:52
ttxyes, norpmal is good13:52
ttxnormal is good too13:52
mesterylol13:53
ttxwhat else...13:53
ttxwe'll be discussing pTl election and design summit scheduling at the cross-project meeting today13:53
mesteryYes, I saw the email!13:53
mesteryNext week at the Neutron meeting I plan to open up the design summit melee for folks :)13:54
ttxany red flag or problem potentially impacting release, that wI should be aware of ?13:54
mesteryNothing at this point13:54
ttxAlright, I'll be talking to you soon. Hurry to next meeting :)13:54
mesterylol :)13:54
mesteryThanks sir! HAve a great day and talk soon.13:54
ttxnikhil_k: ready when you are14:19
nikhil_kttx: hi14:20
ttx#topic Glance14:20
ttx#link https://launchpad.net/glance/+milestone/kilo-rc114:20
ttxSo... our 2 FFEs live14:20
ttxLast week we said we'd defer both if they failed to make it by now14:20
*** thingee has joined #openstack-relmgr-office14:21
ttxSo unless they are already in the pipe... not sure waiting more would actually help14:21
nikhil_kttx: hmm, double checking if CIS got some traction14:21
nikhil_kArtifacts is stuck14:21
ttxI could grant 1-2 more days to CIS if it's close14:22
nikhil_kttx: seems like, this one is pending https://review.openstack.org/#/c/161621/14:22
ttxartifacts looks further away, and also as I wrote, not sure of the benefit to land it in-release rather than early in liberty14:22
nikhil_kand some documentation patches14:22
nikhil_kttx: Yeah, I mentioned the same thing to the developers working on it14:22
nikhil_kand made them aware about your stance on the same14:23
ttxLooking into CIS14:23
nikhil_kso, whatever you decide on Artifacts should work. I'm tentative too after reading the testing messge earlier14:23
ttxIf CIS is only missing https://review.openstack.org/#/c/161621/, I'd grant it until Thursday to fully merge14:24
ttxArtifacts I'd axe at this point14:24
nikhil_kttx: 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:24
ttxSo the issue with the client fix is that it will trigger a requirements update, and we are at HardDepFreeze14:25
nikhil_kttx: 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:25
ttxYou can already open specs to L14:26
ttxmaster branch will switch to L as soon as we tag RC114:26
nikhil_kok, sounds good. I will send a note that the rest of the development can happen in L and mark the patches with -2 then14:27
ttxsdague: an opinion on https://review.openstack.org/#/c/146074/ wrt. new client release and the cortresponding requirements mess ?14:27
nikhil_kand indicate this info to the necessary people (about RC1, specs etc)14:27
ttxLooks like that FFE would trigger a new client release14:27
ttxwhich we'd had to give a HDF exception to14:28
ttxand then which other projects would have to sync requirements for14:29
nikhil_keh14:29
ttxso that one impacts beyond Glance14:29
nikhil_kok14:29
nikhil_kThat's messy for sure14:29
ttxmaybe better to consider it a L feature too, after all14:30
nikhil_kttx: ok, I think we can create a new spec for client and see it in L14:30
nikhil_kWill send out the info14:30
ttxsounds good. Split the client part, land the server part14:30
nikhil_kcool14:31
ttx#info catalog-index-service gets until Thursday to merge the last serverside bits. Client work should be split and done in Liberty14:31
nikhil_kand the rest of the devstack ones?14:31
ttxThat can land without requiring an exception. Tests are good14:31
nikhil_kttx: cool. one more https://review.openstack.org/15720914:32
nikhil_kThought that isn't really WIP14:32
nikhil_kttx: can we get that one in?14:32
ttxTest addition is not considered a feature14:32
nikhil_kok, sounds good14:32
ttxso yes, it can land until RC114:32
nikhil_kThanks for letting me know, I would request removal of the bp tag from the commit message and ask for a bug instead14:33
ttxnikhil_k: Did you have some time to triage the bugs and find release blockers ?14:33
nikhil_kttx: yes, please let's do that14:33
nikhil_ksorry couldn't get to it earlier14:33
ttxWould be good to work on it soon, so that we know how far we are from RC114:34
ttxMaybe something you could delegate14:34
ttx#info only 10 bugs in RC buglist but that one is still incomplete14:34
nikhil_kttx: oh, I read that you wanted to do it now. Sorry context switched from the use of language my team does ..14:34
ttxI need to jump to my next customer14:35
ttxotherwise we could have ;)14:35
nikhil_kttx: sure :)14:35
ttxnikhil_k: Let's talk again on Thursday, hopefully FFE will be done and buglist built14:35
nikhil_kyeah, catch ya then14:35
nikhil_kThanks!14:35
ttxcheers14:35
ttxthingee: around?14:36
thingeettx: hi14:36
ttx#topic Cinder14:36
ttxSorry for running late14:36
ttx#link https://launchpad.net/cinder/+milestone/kilo-rc114:36
thingeeno problem14:36
ttxSo.. what date did you finally give for driver readdition ?14:36
thingeeapril 6th http://lists.openstack.org/pipermail/openstack-dev/2015-March/059990.html14:37
ttxLooks good. Correspnds to the end of the "normal" RC1s (the week after that is kept for stragglers)14:37
ttx#info Some drivers may be reintroduced, deadline Apr 614:38
ttxLooking at the bug list14:38
ttx#info 7 targeted RC bugs14:38
thingeeI've been happy with the progress drivers are making for being readded.14:38
ttxDid you triage most bugs to find those 7 ?14:38
sdaguettx: I think - https://review.openstack.org/#/c/146074/ is too late14:39
thingeeI am actively triaging yes.14:39
ttxsdague: right, nikhil_k and I decided to defer it14:40
ttxthingee: ok, good, looks like you have stuff under control14:40
ttxAny red flag, besides the late driver readdition ?14:40
thingeenope. we have some nice bad bugs but patches are posted.14:42
thingeeglad they're being found now.14:42
ttxok, great! ttyl14:42
ttxdavid-lyle: around?14:42
thingeethanks14:42
ttxdavid-lyle might have missed the European DST memo14:51
david-lylettx: o/14:52
ttx#topic Horizon14:52
ttx#link https://launchpad.net/horizon/+milestone/kilo-rc114:52
ttxI see two FFEs still in there, unfortunately assigned to the same person14:53
ttxLast week we said:14:53
ttxfederated-identity -- late feature catch-up, ideally would merge before Tuesday next week14:53
ttxangularize-identity-tables -- needs to be finalized before next week14:53
ttxHow far are those from landing ?14:54
ttxangularize-identity-tables seems to have plenty of patches left14:54
david-lyleidentity tables is farther14:54
ttxFederated identity seems to hinge on https://review.openstack.org/#/c/151842/14:54
ttxin which case we could give it a couple more days to go through the CI pipe14:55
david-lyleI think Federated Identity can land14:55
ttxHow about we defer angularize-identity-tables and give federated-identity until Friday ?14:55
ttxdoes that make sense ?14:56
david-lyleYes, that seems appropriate given the timeframe14:56
ttxOK, I'll let you defer the table stuff14:56
david-lylewill do14:56
ttx#info federated-identity is really close, FFE extended until Friday14:56
ttx#info 11 targeted bugs on the RC buglist14:57
ttxIs tahht all the known blockers, or the triage work is still a todo ?14:57
ttxthat*14:57
david-lylesome of those will clean out with removing the tables bp14:58
david-lylethat's all I am aware of14:58
ttxok, good14:58
ttxLooks like we should be on time here too14:58
david-lyleYes, I think so14:59
ttxAny red flag I should know of ?14:59
david-lyleother than the gate fiasco, no14:59
ttxheh, that happens14:59
ttxalright, have a good week then14:59
david-lylethanks, you too14:59
david-lylettx: did want to ask about horizon decomposition15:00
david-lylebut you may not have enough time right now15:00
ttxHmm, could you ping me tomorrow ? About to jump on a call right now15:00
david-lyleyes, sure15:00
ttxand today is meeting-crazy day15:01
ttxok, great15:01
david-lyleack15:01
david-lylewill ping tomorrow15:01
devanandattx: o/15:09
ttxdevananda: moved our sync one hour later15:14
ttxdevananda: on a call right now15:14
devanandaoh. darn time changes. I thought it was now ... thanks15:15
Kiallttx: 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:21
*** thingee has quit IRC15:36
ttxKiall: when we tag RC1 we cut the kilo release branch from it and let master evolve in liberty15:37
ttxdevananda: I'm of the call now, we can sync now if you want15:38
ttxoff*15:38
Kiallttx: perfect, for some reason I thought it had changed to cut stable/kilo after kilo final was released15:45
*** mestery has quit IRC15:45
ttxKiall: it's also true15:46
ttxWe cut proposed/kilo for release candidates, and switch to stable/kilo once it's stable/released15:47
Kiallhah - i thought proposed/foo was dropped?15:47
* Kiall needs to re-read the branching wiki page15:47
ttxKiall: no.. "milestone-proposed" was dropped.15:48
ttxproposed/foo is still alive15:48
ttxhttps://wiki.openstack.org/wiki/ReleaseTeam/How_To_Release#proposed.2F.24SERIES_branch_cut_.28switch_master_to_next_version.2915:48
ttxmorganfainberg: ready when you are15:48
* morganfainberg wakes up.15:49
morganfainbergHi :)15:49
* ttx violently shakes morganfainberg 15:49
morganfainbergLol.15:49
ttx#topic Keystone15:49
* ttx dcc sends coffee15:49
morganfainbergYessssssss15:49
ttx#link https://launchpad.net/keystone/+milestone/kilo-rc115:50
morganfainbergCoffee will happen right after this sync up15:50
ttxI see one FFE still standing there15:50
morganfainbergYes. There is one outstanding review and a new bug / issue to address.15:50
ttxinterestingly we didn't mention that one last week15:50
morganfainbergThat will be discussed today w/ henrynash15:50
morganfainbergWe did, domain-sql?15:51
morganfainbergIt was on the list of cleanup/final patches for a feature to land.15:51
ttxI failed to #info it correctly15:51
morganfainbergAhh15:51
ttx"should not take more than a week"15:51
ttxAh no, here it is: domain-config-ext -- to be fully merged before Tuesday next week15:52
morganfainbergYeah. It should land today/tomorrow. Just need to address some comments.15:52
morganfainbergAnd add some more sql logic15:52
ttxOK, let's give it until Thursday15:52
morganfainberg++15:52
morganfainbergIt's close.15:52
ttx#info domain-config-ext - FFE extended to Thursday15:53
ttx#info 13 bugs on the RC buglist15:53
morganfainbergBugs are mostly in shape. Might see one more removed from the list.15:53
morganfainbergThe rest I'm hoping to see in/progress by shortly  and/or committed for those in progress.15:54
ttxDid you run through keystone bugs to find the rc stuff ?15:54
ttxi.e. is that list considered the known RC issues ?15:54
morganfainbergYes. There might be one less bug.15:54
morganfainbergBy the end of he day15:54
ttxAlright, looks like you're on track15:54
ttxGoal for "normal" projects is to tag RC1 sometimes next week15:54
morganfainbergYep. I hope we are on track for that15:55
ttxAlright. I'll talk to you next week, then15:55
morganfainbergHave a good day!15:55
ttxhave a GREAT day!15:55
* morganfainberg scurries off for caffeine so the day can be great :)15:55
ttxnotmyname: ready when you are15:55
*** mestery has joined #openstack-relmgr-office16:03
notmynamettx: here16:06
notmynamettx: sorry for the delay. was biking in16:06
ttx#topic Swift16:07
ttxnotmyname: I created the branch, hopefully you wanted it on HEAD16:07
notmynamethank you. yes. off of master16:07
ttxcool, guessed right16:07
ttxso it should be all set16:08
notmynameso ya, that's what we're doing :-)16:08
ttxDid you settle on a version number ? I'd like to create the milestone page16:08
notmyname2.3.016:08
notmynamethis week (ie today, probably) we'll freeze master until the feature/ec_review lands16:09
ttxok, created https://launchpad.net/swift/+milestone/2.3.0-rc116:09
ttxyou can target RC bugs to it if you want to track those16:10
ttxok, sounds good16:10
notmynameI'll let you know asap when master is ready for the RC16:10
notmynameright now, we're targeting the end of next week (4/10)16:10
notmynamebut it depends on the integration work this week and next16:10
* notmyname may not get much sleep16:11
ttxsounds good16:11
notmynamewhen do you expect to have the summit schedule assignments done?16:11
ttxnotmyname: I plan to discuss this at the cross-project meeting today16:11
ttxI expect to have the final list of projects around April 7, so to finalize assignments ~April 1016:12
notmynameoh the suspense ;-)16:12
notmynameok16:12
ttxBut we likely have less than expected, so projects should get what they asked for16:12
notmynameyay16:13
ttxmore on the discussion at the meeting16:13
notmynameok16:13
notmynameanything else?16:13
ttxnope, I'll let you go back to work, much to do :)16:13
notmynameindeed16:13
notmynamehave good evening16:14
ttxthx!16:14
ttxdevananda: around?16:14
ttxSlickNik: want to jump ahead ?16:20
SlickNikttx: sure thing16:20
ttx#topic Trove16:20
ttx#link https://launchpad.net/trove/+milestone/kilo-rc116:20
ttx#info All FFEs set16:21
SlickNikYup, all done by end of last week.16:21
ttx#info 8 bugs on the RC list16:21
SlickNikHurray for deadlines :)16:21
ttxnothing like a good deadline!16:21
SlickNikYup, we're pretty much locked down, and doing testing / bugfixes at this point.16:21
ttxDo you think that list represents all the known issues ? Did you go on a trigaiung rampage ?16:22
ttxtriaging*16:22
SlickNikI did triage of the recent issues opened. I'm planning on doing a more in-depth one today.16:22
ttxok great16:23
ttxLooks like we could hit the RC1 sweet spot in the middle of next week for you16:23
SlickNik++16:23
ttxWe'll discuss PTl election and summit scheduling at the cross-project meeting today16:23
ttxin case you want to join16:23
SlickNikWill keep a vigilant eye out for new issues that may crop up.16:23
ttxAnything I should be aware of ?16:24
SlickNikWill definitely be there.16:24
SlickNikWe're marching ahead pretty well at this point — nothing more from my side.16:24
ttxalright! Thanks!16:24
ttxdevananda: around now?16:24
SlickNikThanks ttx. See you in the afternoon!16:25
devanandattx: hi!16:27
ttx#topic Ironic16:27
ttx#info https://launchpad.net/ironic/+milestone/kilo-rc116:27
devanandawas in a taxi16:27
ttxdevananda: still traveling?16:27
devanandayarr :(16:28
devanandaso that list is overly aggressive - i've been targeting things to get the team to take notice16:28
devanandawe'll likely untarget some of that, and fix some of that16:28
devanandastill aiming for one week from today as our first RC116:28
devanandahave a question on translations ...16:28
ttxRight, refine it as you go so that it contains all release blockers16:28
devananda#link https://www.transifex.com/projects/p/ironic/16:29
ttxalso make sure you have people assigned to each, otherwise it tends not to get done16:29
devanandaindeed16:29
* ttx curls in foetal position screaming Translations! Translations!16:29
devananda:-/16:29
ttxsomeone in a white uniform comes and carries ttx away16:29
devanandaright. let's not talk about that :)16:30
ttx14% French! Not me16:30
ttx26% Australian english. That must not be too hard16:30
devanandagiven the 75% translated bar for inclusion16:31
devanandai'm inclined to not worry about it at all16:31
devanandaunless someone jumps up and down saying they really want to translate ironic16:31
devanandait == string freeze16:31
ttxYou could publish a call for translations, but at this stage I'd say you're a bit far from the bar16:31
ttxso arguably yes, the pain of a string change is probably limited16:32
ttxShould still avoid gratuitous changes, but I'd say exceptions shall be granted16:32
ttxsince those are unlikely to affect the end result16:32
devanandayea, avoiding gratutios changes +116:32
devanandacool16:32
ttxdevananda: I'd still comunicate changes if you push some. That could raise awareness on ironic needing help to be translated16:33
ttxi.e. "we changed that string, in case anyone cares"16:33
devanandagotcha. what's the maailing list / tag for that?16:33
ttxI'd say openstack-dev, with [stringfreeze] in the subject16:34
devanandak k16:34
ttxThat is all. We'll discuss summit scheduling and PTL elections at the cross-project meeting today16:34
ttxanything else I should worry about?16:35
devanandanope. not unless you want to :)16:35
* ttx happily stays unaware16:35
ttxdevananda: keep on refining that buglist, talk to you later16:36
* devananda tries to find time to takes a nap before the TC meeting16:36
devanandaciao!16:36
ttx#endmeeting16:36
openstackMeeting ended Tue Mar 31 16:36:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-31-08.04.html16:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-31-08.04.txt16:36
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-31-08.04.log.html16:36
ttxThx everyone16:36
*** johnthetubaguy is now known as zz_johnthetubagu17:18
*** thingee has joined #openstack-relmgr-office18:17
*** eglynn has quit IRC20:11
*** david-lyle has quit IRC20:40
*** eglynn has joined #openstack-relmgr-office20:53
*** asalkeld has joined #openstack-relmgr-office20:54
*** david-lyle_ has joined #openstack-relmgr-office21:19
*** david-lyle_ is now known as david-lyle21:43
*** eglynn has quit IRC21:55
*** david-lyle has quit IRC22:02

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!