Tuesday, 2014-01-14

*** markwash has quit IRC00:51
*** SergeyLukjanov has joined #openstack-relmgr-office04:52
*** markwash has joined #openstack-relmgr-office05:04
*** markwash has quit IRC05:27
*** markwash has joined #openstack-relmgr-office05:29
*** markwash has quit IRC05:30
*** markwash has joined #openstack-relmgr-office05:42
*** SergeyLukjanov has quit IRC06:12
*** SergeyLukjanov has joined #openstack-relmgr-office07:35
*** markwash has quit IRC09:06
*** SergeyLukjanov has quit IRC12:18
*** SergeyLukjanov has joined #openstack-relmgr-office12:19
*** SergeyLukjanov has quit IRC12:53
*** SergeyLukjanov has joined #openstack-relmgr-office12:54
ttxdhellmann: ok, let's do this13:14
dhellmannhere13:14
ttxhttps://launchpad.net/oslo/+milestone/icehouse-2 first13:14
dhellmannwe're looking good on most of those blueprints13:14
dhellmannneed a few reviews13:14
ttxyeah, looks good13:15
ttxsync-models-with-migration should move forward fast enough to get all code proposed in the next days ?13:15
dhellmannthe i18n item might be done, there's something up for review I think we should not do (add a new config option) so I'm working on convincing the author of that13:15
dhellmannah, no, that one is not going to land13:15
dhellmannI'm going to go ahead and move it to i4313:15
dhellmanner, 313:15
ttxok13:16
dhellmannI do expect the others to land13:16
ttxhttps://launchpad.net/oslo.messaging/+milestone/icehouse-213:16
dhellmannso, I'm going to start by saying this split view thing is not working out as well as I'd hoped13:17
ttxheh, yes13:17
dhellmannfor the other libraries, I've decided to just leave them in the main oslo view until we move to storyboard13:17
ttxit will work once we get proper project groups, yes13:17
dhellmannyeah13:17
ttxotherwise it's just plain painful13:18
dhellmannI'm going to look at the code reviews for the 2 in "needs code review" today, and I'm going to move the others to i313:18
ttxare all those still likely to land ? Not so many days13:18
dhellmannand contact the authors13:18
ttxok13:18
dhellmannif the surprise me, we can move them back, but I don't expect that13:18
dhellmannthe config generator bug item is blocked on me doing some other work, which I'm going to start today13:19
ttxyour i-3 is not completely over-committed yet13:19
dhellmannmark has a WIP patch, I just need to verify that it has the needed data13:19
dhellmannyeah, I think everyone targeted i2 and we've been using i3 for overflow :-)13:19
ttxI'm fine with "less features landing". I just want us to accurately convey what is likely to land13:20
dhellmannright13:20
ttxso the idea is to be a bit more pessimistic13:20
dhellmannI sort of view this as working on the release notes early13:20
ttxyour targeted bugs sound in order too13:21
ttxanything else about icehouse-2 ?13:21
dhellmannno, I just need to ask the team to do some more reviews13:22
ttxguess it's better than have the reviews and be blocked by gate :)13:22
dhellmannwell, we have that to look forward to, right? :-)13:23
*** sdague has joined #openstack-relmgr-office13:23
ttxdhellmann: anything you want to see discussed at the release meeting today ?13:23
dhellmannI would be interested to hear the other PTL's opinions on the log config option question I sent to the list, let me find that link13:23
dhellmannhttp://lists.openstack.org/pipermail/openstack-dev/2014-January/024205.html13:24
ttxok, adding to agenda13:24
dhellmannthanks13:24
dhellmannand that's it for me13:25
ttxok, thx!13:25
jd__o/13:25
ttxjd__: wanna go now ?13:26
* jd__ knocks13:26
jd__yup13:26
ttxok13:26
ttxhttps://launchpad.net/ceilometer/+milestone/icehouse-213:26
ttxdefer time!13:26
ttxMost of those look like they are not going to make it13:26
jd__i'm afraid so13:26
ttxare all the statuses there accurate ?13:27
jd__yeah they started too late or are blocked13:27
jd__yes13:27
ttxSo what's still likely to make it ? The good progress + needs code review ones ?13:28
jd__I would hope13:28
ttxjd__: the problem is, your i-3 is pretty crowded already -- with the same people assigned to stuff13:28
jd__that's not a lot13:28
jd__I know, I blame people13:29
jd__we are also block by oslo.messaging for a couple of high bp13:29
jd__*blocked13:29
ttxso, as a first step I'd defer to i-3 all the not started / started / slow progress13:30
ttxthen as a second step I'd review i-3 and start cutting it into a more likely set13:30
jd__sounds like a plan13:30
ttxthen focus on getting whatever is left in i-2 in before next week :)13:31
ttxif something targeted to i-3 accidentally makes it we can put it back13:31
jd__sure; i'm changing targets13:31
ttxbut I'd rather chase down a narrower set13:31
ttxas it increases the chances of actually shipping features13:31
jd__agreed13:32
jd__though so far our main problem is not review, but code13:32
ttxlet me know when you're done13:32
jd__should be done now, you can refresh13:32
ttxjd__: you kept the "started" in ? Are they lokely to make it ?13:33
ttxlikely*13:33
jd__maybe the complex query as they're already patches, I'll set it to good progress13:34
jd__I'll change the rest13:34
ttxok13:34
ttxBug list looks sane, we can cut it down next week based on progress13:34
jd__updated13:35
ttxso for your next ceilo meeting it would be great to look at the i-3 objectives and start cutting down13:35
ttxespecially where specific devs are overcommitted13:36
jd__agreed13:36
ttx(Eoghan and you)13:36
ttxLook at past velocity rather than what you think you can code in a week :)13:36
jd__hehe13:36
ttxthat's all I had13:37
jd__same for me13:37
jd__nothing to add for tonight13:37
ttxjd__: ok, thx!13:37
ttxjgriffith: want to go now ?13:37
jgriffithttx: sure13:39
*** SergeyLukjanov is now known as _SergeyLukjanov13:40
ttxhttps://launchpad.net/cinder/+milestone/icehouse-213:40
*** _SergeyLukjanov has quit IRC13:40
ttxjgriffith: is deprecate-chance-and-simple-schedulers completed by https://review.openstack.org/#/c/64645/ ?13:40
jgriffithIIRC there's one more step left13:41
jgriffithttx: Oh... no, that's it I think13:41
ttxok, marking implemented then13:41
ttxstill a lot to defer though :)13:41
jgriffithI really was hoping/trusting folks from their updates last week :(13:42
ttxdo you know which (of the Started/Good progress) still stand a chance ?13:42
jgriffithEd, Duncan and Ronen13:42
jgriffithWhat's up with that one for Thierry?13:42
ttxI just marked the cinder-rootwrap one good progress. Blocked on a grenade review but otherwise should be good13:43
jgriffithThe three I just called out, the rest I'l push out13:43
jgriffithKK13:43
jgriffithThe Lows I'll pun on as well13:43
jgriffithand prophet store, if they submit early fine13:43
jgriffithbut I don't see it happening13:43
ttxyou can keep the Low/Needs code review in13:43
jgriffithfor sure13:43
jgriffithI don't want to push out anything that's in review13:44
ttxProiphetstore: should that be "low ?13:44
jgriffithYes13:44
ttxok fixing13:44
ttxjgriffith: could you defer now so that I see how the result looks ?13:44
jgriffithSure.. just a moment13:45
jgriffiththere's the easy ones...13:46
jgriffithdoh13:46
jgriffithttx: ok, try that13:48
ttxso... you puhsed back the Prophetstore one ?13:49
jgriffithI did, with a note that they can certainly submit if they get it done13:49
ttxok13:49
jgriffithIt seems you're the only person they're communicating with13:49
ttxThose 5 "started" at tht top... do they still stand a chance to get merged ?13:50
jgriffithYes13:50
jgriffithDuncans is the only questionable one13:50
jgriffithI'll retarget13:50
jgriffithand I think just reassign it13:50
jgriffithto somebody else13:50
ttxok, sounds like you have a busy week ahead13:50
jgriffithSergey's is actually in review13:50
jgriffithalways13:50
ttxI'll set sergey's needs codereview13:51
jgriffithour other item is in progress but turning in to quite a pain13:51
jgriffiththanks (for setting that one)13:51
jgriffithI may punt his, haven't decided13:51
jgriffithbut it'll happen today if I do13:51
ttxOK, that looks better. Late, but not compltely impossible13:51
jgriffithand it looks like there's no reason to keep Duncan's in place, it's not happening so I'm chaning that13:51
ttxok13:52
ttxOn the bugs side13:52
ttxLots of targeted bugs, we'll refine next week13:53
ttxfeel free to early defer to i-3 (or remove target) the ones that are not that urgent13:53
jgriffithwill do13:53
ttxanythign else affecting i-2 ?13:53
jgriffithNope, just sec issues which you're aware of and are another conversation13:54
ttxright13:54
ttxHave a topic you want to discuss at the cross-project meeting today ?13:54
jgriffithNope, not this week :)  I used up my topics last week13:55
ttxheh13:55
ttxok then, see you there13:55
jgriffithbut interestingly enough folks seemed to say the same thing in the ML Monday13:55
jgriffithso maybe I wasn't full of it13:55
jgriffithyep.. see ya then, and thanks!13:55
ttxyou defeinitely weren't13:55
*** SergeyLukjanov has joined #openstack-relmgr-office14:06
*** hartsocks has joined #openstack-relmgr-office14:47
*** hartsocks has left #openstack-relmgr-office14:49
*** hartsocks has joined #openstack-relmgr-office14:49
ttxdolphm: if you're ready, we can start now - looks like markmcclain's plane has no wifi after all14:51
dolphmttx: ha. i'm free14:52
ttxhttps://launchpad.net/keystone/+milestone/icehouse-214:52
ttxso... are those all still likely to make it in the week ? Or should we already punt the not started / started ?14:53
ttxdolphm: ^14:54
dolphmi'm worried about saml and mapping at this point, but the majority of keystone-core is also getting together this week to knock all this out :)14:54
ttxwhen is that ?14:55
dolphmi also just revised mapping from 'beta available' to 'needs code review' ... the bp simply wasn't mentioned in the commit message properly, so it wasn't getting tracked14:55
dolphmwednesday-friday in san antonio14:55
ttxok14:55
ttxno-check-id is "not started", still short enough to potentially make it ?14:55
ttxalso is revocation-events advanced enough to be considered Good progress, or is most of the work still wip ?14:56
dolphmi need to follow up on that one.. i believe it was a intended to start tracking an effort that was already in review... so there should be a patch out there somewhere14:57
* ttx looks14:57
dolphmthe API for revocation events is fairly settled, and there's a fairly complete-looking patch that's failing jenkins quite miserably14:57
dolphmdefinitely a lot of energy going into that one14:57
ttxok, moving to good progress14:58
dolphmfor which one?14:58
dolphmah revocation events14:59
ttxrevocation events14:59
ttxfor the no-check-id, would that be https://review.openstack.org/#/c/54647/15:00
dolphmyep!15:00
ttxok, is that all there is to it (needs code reveiw) or part of a larger change set (good progress) ?15:00
dolphmthat looks like it'll be it15:00
ttxok, i2 looks good to me now15:01
ttxa bit ambitious, but then if you sprint this week15:01
ttxand the gods of the gate are in your favor15:01
dolphmwooo15:01
ttxmight work out15:01
*** sahid has joined #openstack-relmgr-office15:01
ttxtrick being, not that much free space in your i-3 to defer15:02
ttxtargeted bug list is small enough15:02
ttxI think we are good15:02
dolphmeek, i haven't looked at i3 in a while15:02
ttxdolphm: anything icehouse-2 blocking on your side ?15:02
dolphmyes... it's been discussed, but appears to have a new development... one sec15:03
dolphmhttps://blueprints.launchpad.net/keystone/+spec/user-locale-api is blocked by oslo15:04
dolphmall the patches in https://blueprints.launchpad.net/oslo/+spec/i18n-messages have merged but one, which is -2'd pending further discussion15:04
ttxok we'll discuss it today15:04
ttxanything else you'd like to see discussed at the cross-project meeting later today ?15:05
dolphmi just asked brant to follow up and see if enough has merged for keystone to land our bp in i215:05
dolphmthat's all from me15:05
ttxok thx15:05
ttxtalk to you later15:06
dolphm /salute15:06
ttxrussellb: ready to jump ?15:07
russellbin a sec15:08
ttxsince markmcclain still hasn't got wifi on his plane15:08
russellbwat, 6 more blueprints since yesterday targeted at icehouse15:08
* ttx waits15:08
russellbwe can start now15:08
ttxhttps://launchpad.net/nova/+milestone/icehouse-215:09
russellbso ... our velocity seems way down this cycle15:09
russellbi think a lot of nova folks are less active than usual15:09
russellbeither that or the holidays hurt a lot ...15:10
russellbare you seeing that with any other projects?  or is it just us15:10
ttxI'd have to analyze that15:10
ttxbut yes, that rings a bell15:11
russellbno worries if you're not sure off hand15:11
ttxmore projects too15:11
russellbjust something i was thinking about a lot yesterday15:11
russellbyeah, some people are busy with other projects15:11
russellband others are just ... i don't know, not around as much15:11
russellband holidays15:11
russellbbut, it is what it is.15:11
ttxrussellb: the trick is, you still have heaps of blueprints targeted15:11
russellbyeah, all things someone claimed they would do15:12
russellbreview bandwidth is going to hurt it though15:12
russellball things someone wanted to do and we thought was sane15:12
russellbnot sure what else to do except leave it all there and just see what gets finished15:12
russellband pick the select few that we *must* finish15:13
russellbbtw, i posted to openstack-dev yesterday doing a last call for people to please sponsor blueprints15:13
russellbbefore we give up on this prioritization experiment15:13
ttxrussellb: there is value in deferring stuff that doesn't have all the necessary code posted... and that is focusing review effort on what may just get completed in te milestone15:13
russellbthat's true15:13
russellbi deferred some yesterday15:14
russellbstarted with everything still "not started"15:14
ttxso something like deferring all the Lows that are not "needs code review"15:14
ttx+ the mediums that don't stand a chance15:14
russellbyeah15:14
ttxthen use that to prioritize reviews for this week15:14
russellbi'll go back through and start deferring more that aren't close15:14
russellbtakes freaking forever to get through all these though :(15:14
ttxif by some miracle/accident an i-3 gets in, we can still put it back in i-215:14
ttxI can help for that15:15
russellbsure, if you've got some time15:15
ttxjust tell me the rule and I'll apply it15:15
russellbmaybe I should post something today to the ML saying anything not ready for review by the EOD today is getting deferred15:16
russellbgive one last day for people to get stuff posted15:16
ttxsounds good15:16
russellband then tomorrow we just defer everything not "needs code review"15:16
russellbok it's a plan then15:16
ttxthen early in i-3 we'll do the reality check15:16
russellbcool15:17
ttxbecause those 85 BPs you have targeted to i-3 already are not really getting anywhere imho15:17
russellbyeah, it's madness15:17
ttxwill analyze velocity once we are past i-215:17
ttxbased on i-1 + i-215:17
russellbgood idea15:17
russellbi-2 bugs ... i just left everything marked "in progress"15:17
ttxand get some # of changes merged stats15:17
ttxok, anything particular you'd like to discuss at meeting today ?15:18
russellbgate stability again i suppose15:18
russellbmade some good progress in the last week, and i want to push the issue on getting some things merged15:19
russellbin particular the patch to reduce tempest concurrency15:19
ttxit's your turn ?15:19
russellbnot sure if you read my status email on it ...15:19
ttxI read it15:19
russellbOK15:19
russellbso yeah, majority of failures are just test load too high ...15:19
ttxok will add it15:19
russellbwhich is a pretty easy thing to fix15:19
russellbk15:19
russellbother than that ... the other hot nova / cross-project topic is nova-net vs neutron15:20
russellbthough the neutron folks may be all busy this week15:20
russellbi could give a quick update on things i'd like to do with nova-network though15:20
ttxyeah, we can defer this one to next week15:20
russellbOK that's fine15:20
ttxok then. Post that review deadline to -dev. And once you decide on a defer rule I can help applying it15:21
ttx(tomorrow)15:21
russellbsounds good15:21
ttxthx!15:21
russellbdefer rule will just be ... defer if not in "needs code review"15:21
ttxack15:27
*** hartsocks has left #openstack-relmgr-office15:29
ttxdavid-lyle: ping me when around15:30
david-lylettx: here15:30
ttxdavid-lyle: ok, let's do this15:31
ttxhttps://launchpad.net/horizon/+milestone/icehouse-215:31
ttxdavid-lyle: "Auto login after password changed" has a "Not" priority. Shoudl it be turned into "Low" or removed from milestone ?15:31
david-lyleI'll drop that one, I'm don't think there is agreement on the approach or need15:32
ttxok, please do15:32
ttxwizard-ui-for-workflow is marked implemented but has https://review.openstack.org/#/c/64839/ opened15:32
ttxso what's the real status ?15:33
david-lylettx: that was tacked on by a developer.  It's not necessary for the bp15:33
ttxok15:33
david-lyleI'll separate that as well15:33
david-lylefirst one is removed15:33
ttxno, I can fix the latter15:33
ttxdone15:34
ttxso.. how likely are those the ones that are not yet "needs code review" to make it ?15:35
ttxs/those//15:35
ttxIn particular the two that are just marked "started"15:35
david-lylemost not likely, I will begin bumping them today.  I think one still has a chance.15:35
ttxdavid-lyle: at this point you have so much under review it might make sense to focus review efforts on those likely to be implemented by next week15:35
david-lyleack15:36
david-lyleI had drawn a line as of today to put under review15:36
ttxsounds good15:36
david-lyleso this afternoon I will move them15:36
ttxrussellb is doing the same for nova15:36
ttxthat's useful when you already have so much under review15:36
david-lyleyes, it's nice to be able to focus15:37
ttxbug list is pretty large too, but we can start culling it next week once we see what merges and what not15:37
ttxdavid-lyle: note that your i-" is already a bit overcrowded so not much room for deferral15:38
ttxi-315:38
ttxOK...anything blocking your i-2 efforts ?15:38
david-lyleI think several i-3 may slip.  Changing focus and people coming and going15:38
david-lyleno blockers, just need a new meeting venue =)15:39
ttxwe'll have to revisit i-3 after next week and set reasonable objectives15:39
ttxanything you'd like to see discussed at meeting later ?15:39
david-lyleagree, it started very light, and things have been added.  I'll do some cleanup15:40
david-lyleno, I don't think so15:40
david-lylefor this afternoon15:40
ttxok, talk to you later then15:40
david-lylesounds good15:40
ttxnotmyname: if you're still suffering from jetlag, we can run now15:40
notmynamettx: good morning15:41
ttxnotmyname: hi!15:41
notmynamettx: swift mini hackathon today and tomorrow15:41
notmynamettx: plans still the same as last week: RC late this week and 1.12 next week15:41
ttxOK, I think all stars are aligned so far15:42
ttx"feature-wise" is https://launchpad.net/swift/+milestone/1.12.0 mostly covering what will end up in 1.12.0 at this point ?15:42
ttxor you need to add a few more ?15:43
notmynamettx: no, I'll need to add the sysmeta and check the other things that have added15:43
ttxok, would be good to cover that before the end of the week15:43
ttx(can do when you push release notes in swift repo15:44
ttx)15:44
notmynameya15:44
ttxanything you'd like us to discuss at meeting today ? FWIW russellb already added discussion of gate stability so we'll review progress there15:45
notmynamettx: no I don't have anything15:45
ttxwe were in good shape yesterday but the nodepool fell down and buidt a new backlog15:45
ttxnotmyname: ok then, talk to you later15:46
*** markmcclain has joined #openstack-relmgr-office15:48
markmcclainttx: ping15:48
ttxmarkmcclain: oh hai15:48
ttxmarkmcclain: we can try quickly now15:49
markmcclainsorry had trouble connecting remotely15:49
ttxor in 40 minutes if you prefer. notmyname just took an early slot15:49
ttxhave a call in 1015:49
markmcclainok.. let's go in 40 then15:49
ttxawesome15:49
markmcclaintalk to you later15:49
*** SergeyLukjanov has quit IRC15:53
*** markmcclain has quit IRC15:54
*** markwash has joined #openstack-relmgr-office16:17
*** markmcclain has joined #openstack-relmgr-office16:24
*** markmcclain has quit IRC16:25
*** markmcclain has joined #openstack-relmgr-office16:28
ttxmarkmcclain: still on my call, but I can multiplex16:30
markmcclainttx: ok16:31
ttxmarkmcclain: https://launchpad.net/neutron/+milestone/icehouse-216:31
ttxconfig-plugin-by-name needs triage16:31
ttxif code prposed, maybe low ?16:31
markmcclaincode is proposed16:32
ttxdid you just defer the not started ?16:32
markmcclainyes16:32
ttxok16:32
ttxhow likely are the "started" and "slow progress" to make it ?16:33
markmcclainI'm going to defer the one convergence ctlr16:33
markmcclainthey have not activated 3rd party testing and are new16:33
ttxack16:33
markmcclainfor the ML2 drivers I expect them to straight forward16:34
markmcclainso I'm ok holding onto them for until Thurs/Fri16:34
ttxok, just keep on refining16:34
ttxwill help in narrowing review focus16:34
markmcclainagreed… most of our focus the next 4 days will be on tempest/neutron/parity changes16:35
markmcclainso there are even items in review that might get bumped16:35
ttxok16:35
ttxso neutron-tempest-parallel will be worked on during sprint ?16:35
markmcclainyes… salvatore has several patches in flight16:35
markmcclainthat should land16:36
ttxthe challenge will be to get some reviews done :)16:36
markmcclainthere will be many of us in Montreal this week16:36
ttxshould I set config-plugin-by-name to low ? or drop it from i-2 ?16:36
markmcclainlow is ok16:37
ttxok16:37
ttxyour buglist is pretty deep, you might want to refine it over week too16:37
markmcclainwill do16:37
ttxotherwise it will be useless as a prioritization tool16:37
markmcclaingood point16:38
ttxyour i-3 is pretty congested too, so deferring won't be that easy without removing other stuff16:38
ttxwe'll review that in following weeks16:38
markmcclainI plan on removing some stuff from Icehouse and deferring until Juno16:39
ttxanything blocking your i-2 efforts ?16:39
markmcclainright now no16:39
ttxanything you'd like to see discussed at meeting today ?16:39
markmcclainno16:39
markmcclainI'll be joining as soon as I clear customs16:39
ttxok then, I think we are done16:39
ttxtalk to you later16:39
markmcclainlater16:40
*** SergeyLukjanov has joined #openstack-relmgr-office16:41
*** markmcclain has quit IRC16:41
ttxmarkwash: hi!16:45
markwashttx greetings16:46
ttxhttps://launchpad.net/glance/+milestone/icehouse-216:46
ttxmarkwash: are those all still likely to make it this week ?16:46
ttxor can we already defer the not started / slow progress ones16:46
markwashI just deferred one "not started" and updated one that was actually started16:47
markwashI think the "slow progress" one will be deferred but it usually ends up being demotivating for folks when I push it back rather than just letting it slide16:47
markwashI don't understand why, but it happens16:47
ttxwell, if they still think it can make it, sure16:48
markwash:-)16:48
*** hub_cap has joined #openstack-relmgr-office16:48
ttxyou have room in your i-3 for deferrals, so not too bad16:48
ttxjust focus review efforts on those that are almost there16:49
markwashyes indeed16:49
ttxrather than on those which will need two more weeks min16:49
markwashthe gate queue got incredibly better over the weekend, which is nice16:49
ttxand defer as soon as the assignee recognizes it won't make it16:49
ttxmarkwash: we had some issue though during the night16:50
ttxwhich rebuilt a backlog16:50
ttxat least it's not growing anymore16:50
markwashah okay16:50
markwashwell perhaps my hopes for smooth sailing were a bit premature16:50
ttxhopefully that backlog will be absorbed during the night16:51
markwashttx: that one bug maked "critical" looks like it might need a bit more of my attention16:51
ttx(no test slave available for something like 12 hours)16:51
ttx(some cloud provider outage)16:51
ttxyes, your bug list sounds sane16:52
ttxwe can refine it next week16:52
markwashttx, just making sure I didn't forget, the target for cutting i2 is january 21? 22?16:52
ttxthe idea would be to cut MP branches late on the 2116:53
ttxI'll be in UT at that point so late might mean late16:53
markwashgotcha16:54
ttxanything blocking your i-2 efforts ?16:54
markwashno, I think we're in okay shape all around16:54
ttxif you get the opportunity to talk to assignees and get them to realize they won't make it, please defer early16:55
ttxthat will communicate to the rest of the world more accurately what we plan16:55
ttxrather than use the BP dashboard as a motivation tool :)16:55
ttxmarkwash: anything you'd like to see discussed at meeting later ?16:56
markwashnothing in particular16:56
ttxok then. Thanks, and talk to you later!16:56
ttxhub_cap: ready?16:57
markwashsee you then!16:57
hub_capheyo sure ttx16:57
ttxhttps://launchpad.net/trove/+milestone/icehouse-216:57
ttxsounds like defer time here as well16:58
hub_capwe have been pretty stagnant this wk16:58
hub_capyea16:58
hub_capdefintely defer time16:58
ttxIs the status there accurately reflecting your knowledge of those feature implementation progress ?16:58
hub_capyes in soime sort (wrt the "started" ones)16:59
hub_capi think the started ones might just defer16:59
ttxIf yes, sounds like the not started / slow progress should be deferred16:59
hub_capi think the code review will all get in16:59
ttxthen you should review the started and see if they are still likely to make it16:59
hub_capoh yes slow prog as well16:59
ttxthe more you defer, the easier iut will be to prioritize review effort16:59
hub_capok ill ping each person after they get on16:59
hub_capthose west coasters and their love for late mornings17:00
hub_capmakes sense ttx17:00
ttxcould you get this mostly fixed by meeting time ?17:00
ttxyou have /some/ room in i-3 for deferrals17:00
ttxbasically, no point in keeping on that list stuff everyone knows (the assignee and you) won't make it17:01
ttxbetter focus on those that might actually make it17:01
ttxgate gods willing17:01
ttxotherwise your bug list looks sane17:02
ttxI'll revert those FixReleased to FixCommitted17:02
ttxsince they shouldn't be released before milestoen hits17:02
ttxhub_cap: should we already defer the "not started" and "slow progress" or you want to chance to talk to them first ?17:03
hub_capsorry baby...17:04
hub_capi can get them all fixed by meeting17:04
ttxOk then, we'll look at the list again during meeting17:04
ttxanything blocking your i-2 progress ?17:04
hub_capok that sounds perfect17:04
hub_capyea.. i need more core reviews heh17:04
hub_capreviews or reviewers ;)17:04
ttxCan't help with that :) anything you'd like to see discussed at meeting ?17:04
hub_capjk no blockers as of now17:04
hub_capnot at present17:05
ttxalrighty17:05
hub_capill have a updated i2 by meeting today sir17:05
ttxtalk to you later then17:05
ttxthanks!17:05
hub_capyessir thx ttx <317:05
*** markmcclain has joined #openstack-relmgr-office17:46
*** markmcclain1 has joined #openstack-relmgr-office17:52
*** markmcclain1 has left #openstack-relmgr-office17:53
*** markmcclain has quit IRC17:55
*** SergeyLukjanov has quit IRC18:58
*** SergeyLukjanov_ has joined #openstack-relmgr-office18:59
*** SergeyLukjanov_ has quit IRC19:03
*** SergeyLukjanov has joined #openstack-relmgr-office19:03
ttxstevebaker: o/19:31
stevebakerhai!19:31
ttxhttps://launchpad.net/heat/+milestone/icehouse-219:32
ttxyay, defer time here too19:32
stevebakeryep, anything Not Started19:32
ttxsounds like the bare minimum yes19:33
ttxI can help with the deferring19:33
ttxwhat about hot-software-config-rest ? Still likely to make it ?19:33
stevebakerits possible, patches are ready for review19:34
ttxstevebaker: was marked Slow Progress, hence me asking19:34
stevebakerthings changed overnight, it looks like it is Needs Code Review. I've updated it19:35
ttxOK, let's defer all not started, then you can refine over the week (take the "started" out if it looks like they won't make it)19:36
stevebakerbut I'll update every software-config bp which depends on that to i-319:36
ttxThis will help you focus review efforts on what's likely to make it19:36
ttxThere seems to be /some/ room in i-3 for these deferrals alright19:37
stevebakerhmm, I think it will be a big i-319:38
ttxYour buglist is also a bit too massive to be useful as a prioritization tool19:38
ttxyou might want to refine it over the week19:38
ttxwe'll cut it down to milestone-critical next week19:38
ttxHow about we push to i-3 things that are still unassigned ?19:38
stevebakerok, I'll start being brutal19:39
stevebakeryep19:39
ttxok, can help with that too19:39
ttxanything blocking your victorious march to i-2 ?19:39
stevebakerpossibly...19:40
stevebakerhttps://blueprints.launchpad.net/heat/+spec/keystone-v3-only is blocked on this keystone review https://review.openstack.org/#/c/66447/19:40
ttxOK, let's raise it during the meeting19:41
ttxanything else ?19:41
stevebakerok19:41
stevebakerI don't think so19:41
ttxOK, so do you want me to move to i-3 all unassigned bugs and "not started" blueprints ?19:42
stevebakerno, I'll go through it now before the meeting19:42
ttxok then19:42
ttxthnaks and see you in a 80 min19:42
ttxthanks even19:42
stevebakerok, later19:42
*** hub_cap has left #openstack-relmgr-office19:47
*** sahid has quit IRC19:51
*** SergeyLukjanov has quit IRC22:36

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