Tuesday, 2015-01-27

*** SlickNik has joined #openstack-relmgr-office01:06
SlickNikttx: Can we do our 1:1 for trove earlier if possible? I have another personal appointment crop up at 5 UTC that I cannot miss — so would appreciate it if we can move our 1:1 to an earlier spot.01:09
SlickNikttx: Let me know. Thanks!01:09
*** Kiall has quit IRC04:10
*** asalkeld has joined #openstack-relmgr-office07:24
ttxSlickNik: sure, ping me when around07:45
SlickNikttx: around now if you want to sync07:45
ttxSlickNik: still warming up, how about in 15min ?07:46
SlickNikttx: sounds good. Take your time — I'll be around. :)07:46
ttxSlickNik: available now07:58
ttx#startmeeting ptl_sync07:58
openstackMeeting started Tue Jan 27 07:58:43 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.07:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:58
openstackThe meeting name has been set to 'ptl_sync'07:58
SlickNikttx: back07:59
ttx#topic Trove07:59
ttx#link https://launchpad.net/trove/+milestone/kilo-207:59
ttxSo... kilo-2 milestone is next week07:59
ttx#info 2 done, 7 inreview, 1 inprogress08:00
SlickNikI've been away for a couple of weeks, and I need to whip that milestone into shape.08:00
SlickNikWorking hard on it this week.08:00
SlickNikMost of the BPs are still work in progress, so will have to move them to kilo-3.08:00
ttxSlickNik: If all code is not up for review yet, you should switch them to Good progress or Slow progress08:01
ttxbecause the way it looks now, it just needs reviews08:01
ttxKeep "Needs code review" for those that have all code proposed08:01
ttxAlso as soon as you're sure it won't hit next week target, move them to k308:02
SlickNikttx: ++ Sounds good. Will go through them today and mark them to reflect the state more precisely.08:02
ttxno need to continue to claim they will make it08:02
ttxYou also have a pretty long bug list08:03
ttxwould be good to reduce it to real milestone priorities/blockers08:03
ttxFor example, those without an assignee should move to k3 at this point I think08:03
ttxSo it would be good to clean that section as well08:04
SlickNikAgreed. Will do it.08:04
SlickNikWill send you a note once I've cleaned it up.08:04
ttxSlickNik: sounds good08:04
ttxThat's all I had08:05
ttxAnything on your side ?08:05
SlickNikttx: Quick heads up that next week is the Trove Mid Cycle Sprint.08:05
SlickNikSo busy getting things organized for that as well.08:05
SlickNik#link https://wiki.openstack.org/wiki/Sprints/TroveKiloSprint08:06
ttxSlickNik: ok. Remember we'll need a SHA for k2 sometimes between Tuesday and Thursday :)08:06
SlickNikYes, I'll make sure I set aside some time for that amidst the sprint.08:06
ttxHave a good week!08:06
SlickNikThanks, I'll drop you a note once I've cleaned out the items on the k2 page a bit — sometime tomorrow.08:07
SlickNikThat's pretty much all I had.08:08
ttxasalkeld: around?09:00
asalkeldttx, hi09:01
ttx#topic Heat09:01
ttx#link https://launchpad.net/heat/+milestone/kilo-209:01
asalkeldttx, i'll push versioned objects to k309:02
ttx#info 3 done, 4 inprogress09:02
ttxcompared to 1 done, 1 inreview, 4 inprogress, 1 uhnknown 2 weeks ago09:02
asalkeldyeah, progress09:02
asalkeldi'll weed the others out09:03
ttxyeah, if code is not proposed by end of week, no reason to keep any open09:03
ttxunless you think they can still make it of course09:03
asalkeldsome are small09:04
asalkeldbut no progress09:04
asalkeldso i'll chase those09:04
ttxsame for bugs, by the end of week you can probably push back those bugfixes that won't make it09:04
asalkeldok, makes senses09:04
ttxWe'll do the final defers next week, and tag between Tuesday and Thursday09:05
asalkeldsounds good09:05
ttxAnything on your side ?09:05
asalkeldno not much on the go09:06
ttxalright... have a good week then!09:06
asalkeldyou too09:06
*** asalkeld has left #openstack-relmgr-office11:42
*** Kiall has joined #openstack-relmgr-office12:25
ttxeglynn: around?13:00
*** eglynn has joined #openstack-relmgr-office13:01
eglynnttx: apols for the lateness13:01
ttx#topic Ceilometer13:01
ttxeglynn: np13:01
ttx#link https://launchpad.net/ceilometer/+milestone/kilo-213:01
ttx#info 7 inreview, 2 inprogress13:01
eglynnall progressing nicely except the hyperV related BPs13:02
ttxcompared to 3 inreview, 4 inprogress, 2 blocked two weeks ago13:02
ttxwould be good to finalize some of them13:02
eglynnif I don't see more traction on the hyper-V work, it'll be punted before EoW13:02
ttxfeeling confident they can stiull make it ?13:02
eglynnyep, everything else looks do-able13:03
ttxthe earlier the better, next week will be busy gatewise13:03
eglynnwhen are you planning to start laying down kilo-2 tags?13:03
ttxwe'll tag sometimes between Tuesday and Thursday next week, when you have a SHA for me13:03
eglynnWednesday next week or Thurs?13:03
ttxso next week 1:1 we'll determine the last blockers13:04
eglynnsounds like aplan13:04
ttxsame for the bugs list, but yours is already quite tidy13:04
ttxI don't think I have much more to say... focus on getting at least some of those completed in time :)13:05
ttxeglynn: anything on your side ?*13:05
eglynnre. CrossProjectMeeting this evening, I'll be a few mins late for it13:05
eglynn(I'm on half-days PTO all this week)13:05
ttxeglynn: is it fine if we start with the devref stuff?13:06
ttxok, will keep agenda as-is13:06
ttxhave a good (and busy reviewing) week :)13:07
ttxeglynn: you coming to FOSDEM ?13:07
eglynnthanks for your time!13:07
eglynnttx: nope, not this year, sadly ... travel budget a bit constrained13:07
ttxeglynn: ack13:08
ttxSergeyLukjanov: ready when you are13:08
SergeyLukjanovttx, hey13:08
ttx#topic Sahara13:08
ttx#link https://launchpad.net/sahara/+milestone/kilo-213:08
ttx#info 3 done, 6 inreview13:08
ttxcompared with 7 inreview, 1 inprogress, 2 blocked two weeks ago13:09
ttxnice progress, still a lot to covber though13:09
SergeyLukjanovwe have a lot of bug fixing13:09
SergeyLukjanovand unfortunetaly there were a lot of vacations :(13:09
ttx2 of the targeted bugs are unassigned, you still think you can get those fixed ?13:09
SergeyLukjanovthe things on review are really near to be merged13:09
SergeyLukjanovttx, probably not13:10
SergeyLukjanovthere were bug fixing day yesterday and bug scratch a week before, so, the issues list in a pretty good shape13:10
ttxhttps://review.openstack.org/#/c/115884/ is merged and "Implements: blueprint edp-improve-compatibility" -- is that one completed ?13:10
SergeyLukjanovttx, it was done on hadoop side and on sahara side the CR is on review13:11
SergeyLukjanovttx, oh, nope, it was merged today, so, moving it to implemented :)13:12
ttxone down, 5 to go13:12
SergeyLukjanovI've been updating the launchpad page yesterday evening when it wasn't yet approved ;)13:12
ttxSergeyLukjanov: we'll push the tag sometimes between Tue and Thu next week, whenever you have a SHA for me13:13
SergeyLukjanovttx, most probably one or two bps will be moved to k313:13
SergeyLukjanovttx, ack13:13
ttxack, move BPs / Bugs out to k3 when you know they won't make it13:13
SergeyLukjanovttx, yup13:13
ttxotherwise we'll revisit the list next week for final blockers adjustment13:13
SergeyLukjanovttx, I don't think we'll have any critical blockers13:14
ttxSergeyLukjanov: that's all I had... anything on your side ?13:14
SergeyLukjanovttx, we have a bunch of horizon CRs under review for a long time again :( I don't know how to improve it, probably record screencast for each CR13:14
ttxSergeyLukjanov: that would make a good topic for a future cross-project meeting, if you can make it13:15
ttxthat will only get worse13:15
SergeyLukjanovttx, yeah, I think we need to discuss it13:15
SergeyLukjanovI will add topic to the meeting agenda13:16
ttxYou can push the topic for next week meeting (too late for today's)13:16
ttxso add it to the "backlog" section of the agenda13:16
SergeyLukjanovyeah, sure, that's I was planning to do13:16
ttxSergeyLukjanov: cool13:16
SergeyLukjanovso, nothing more from my side13:16
ttxbecause it's not just Sahara, it's all projects horizon panels in the future13:16
SergeyLukjanovttx, thank you13:16
SergeyLukjanovttx, yeah, exactly13:16
ttxSergeyLukjanov: have a good week!13:17
ttxdhellmann: ready when you are13:17
dhellmannttx: here13:17
SergeyLukjanovttx, you too!13:17
ttx#topic Oslo13:18
ttx#link https://launchpad.net/oslo/+milestone/kilo-213:18
ttx#link https://launchpad.net/oslo/+milestone/next-kilo13:18
ttxdhellmann: how are you doing on the kilo-2 incubator objectives ?13:18
dhellmannoslo.log is coming along nicely - dims and I have a patch for nova that's mostly working and seems to prove out the API13:19
dhellmannthat means we should be able to make an official release, and then clean up the incubator bits we've been holding back on deleting13:19
dhellmannwe also have oslo.messaging, oslo.i18n, and oslo.vmware releases coming up this week13:19
ttxwith the namespace stuff ? or more ?13:20
dhellmannthe namespace stuff is the main reason, but there will be a few other patches, too13:20
ttxdhellmann: will namespace conversion be completed with those ? Or are there more in the pipe ?13:20
dhellmannthe messaging and vmware releases are the last ones for the namespace conversion13:21
dhellmannafter that we'll be back to the usual feature/bug work13:21
ttx#info oslo.messaging, oslo.i18n, and oslo.vmware releases coming up this week, mostly to drop namespace packages13:21
ttxHow is oslo.context doing ?13:22
dhellmannthe last piece there is to delete it from the incubator, and once we have oslo.log released we can do that (the incubated versions are pretty tightly coupled)13:22
ttxwhat about oslo.policy ? It's marked "needs infra"13:23
dhellmannI think we're waiting for the import to happen, let me check again13:23
dhellmannah, no, we have that repo now13:23
ttxyeah, couldn't find what it was still blocking on13:23
ttxok, so looking good for next weeks goals overall13:24
dhellmannI'll have to check with ayoung on that. I don't see any changes open blocking it.13:24
ttxprobably just a question of tagging an initial release at this point13:24
dhellmannyeah, a bit more rushed at the end than I like but I think we'll mostly do all of this -- policy might slip13:24
dhellmannthat could be it.13:25
ttxdhellmann: we have "Avoiding private symbols in Oslo libraries" topic at cross-project meeting today13:25
ttxthat's all I had -- anything on your side13:26
dhellmannthat topic is from the ML thread I started. I wanted to make sure the PTLs saw it, since there were no responses.13:26
dhellmannbut that's all I had for this week13:27
ttxalright, see you later at the meetings then13:27
dhellmannthanks, have a good afternooN!13:27
dhellmannttx: one thing I forgot, no rush: Who else reviews changes to the release-tools repo? Should I pester someone about approval for those sanity script changes I made?13:33
ttxdhellmann: I usually +2/approve when I get another +113:35
ttxdhellmann: SergeyLukjanov did a few of such reviews in the past13:36
* SergeyLukjanov lurking13:36
ttxdhellmann: bnemec has a question up on the first in line13:36
dhellmannttx: oops, missed that13:37
ttxdhellmann: nothing really blocking though13:37
SergeyLukjanovdhellmann, you could ping me for an additional +1 - I'm pretty interested in release-tools13:37
ttxSergeyLukjanov: have a look at https://review.openstack.org/#/c/143039/ then :)13:38
ttxI need those in for k213:38
dhellmannttx: I replied to bnemec13:38
dhellmannSergeyLukjanov: thanks, I'll keep that in mind13:39
ttxdhellmann: about bnemec, I figured I should not bypass his question, as it's not the beest sway to encourage new people to review your sandbox project :)13:39
ttxbest way*13:39
dhellmannttx: definitely, thanks for pointing it out13:40
*** david-lyle_afk is now known as david-lyle14:49
mesteryttx: Ready and waiting!15:04
mesteryttx: Hold on for a few minutes, baby woke up, I'll ping you back soon.15:06
ttxmestery: ack15:08
mesteryttx: here15:11
ttx#topic Neutron15:11
ttx#link https://launchpad.net/neutron/+milestone/kilo-215:11
mesteryttx: Not much progress in closing BPs, but a lot of them have had patches landed.15:11
ttx#info 3 done, 20 inreview, 3 inprogress, 1 notstarted15:11
ttxcompared to 3 done, 18 inreview, 6 inprogress, 5 notstarted two weeks ago15:12
mesteryttx: Progress is good15:12
ttxso yeah, not that many completion15:12
ttxhttps://blueprints.launchpad.net/neutron/+spec/reorganize-unit-test-tree still not started ?15:12
ttxdoes it still have any chance to be completed by next week ?15:13
mesteryttx: I need to ping marun on that one, it's not clear to me on the status.15:13
mesteryttx: He indicated it was fairly trivial (it's mostly moving code around)15:13
ttxok, defer to k3 if it's doomed15:13
mesteryttx: Ack15:13
ttxotherwise, this is mostly about getting code reviewed and last patches in15:13
mesteryttx: Yes, exactly.15:13
ttxnext week we'll probably tidy the list down to what is in the pipe15:14
ttxand tag when that merges15:14
mesteryttx: I hope to start trimming it by Friday actually15:14
mesteryMaking next week's trimming easier15:14
ttxmestery: I'm fine with that too :)15:14
mesteryIf things aren't in the queue by Friday, I'll move those ones out.15:14
mesteryNext week it'll be a race on what has yet to merge.15:14
ttxwould be good to trim down the bug list as well15:15
ttxi.e. if no review, move out of the k2 list15:15
mesteryttx: Ack on that.15:15
ttxI don't think I need to take more of your precious time15:16
ttxanything on your side ?15:16
mesteryI just wanted to point out that our "plugin decomposition" has been a great success so far!15:16
mesteryI'll have metrics for you next week, but it's looking really good.15:16
ttxyou can use the spare 5 min to plug another review :)15:16
mesteryrofl :)15:16
mesteryThat's I'll I've got, thanks ttx!15:16
ttxcool, looking forward to those stats15:17
* ttx still has to work on release scripts that will support uploading neutron-*aas to the neutron LP page15:17
ttxnext on my todo list15:17
ttxmestery: have a good week!15:17
mesteryttx: You too!15:17
ttxnikhil_k: ready when you are15:18
*** thingee has joined #openstack-relmgr-office15:26
ttxthingee: no nikhil_k so far, you can go now if you want15:26
thingeettx: ok, whew had connection problems...at the cinder midcycle meetup right now :)15:27
ttx#topic Cinder15:27
thingeettx: no wifi...tethering to a phone just for you15:27
ttxshould be quick15:27
ttx#link https://launchpad.net/cinder/+milestone/kilo-215:27
ttx#info 5 done, 21 inreview15:27
ttxcompared to 2 done, 17 inreview, 6 started two weeks ago15:28
ttxI'd say it's time to get all of those in :)15:28
thingeeI agree...I have a few I'll be kicking this week unless they get in a better state.15:28
ttxnext week we'll refine the list down to waht's inflight in the gate and milestone blockers15:28
thingeeBeen communicating in reviews/emails to owners of patches that are going slow.15:28
ttxthen tagging between Tuesday and Thursday as those get in15:28
ttxIt's time to refine the bug list as well -- the ones that don't have review nor assignee are probably good candidates for k3 deferrals15:29
thingeeGood thing I have the whole gang here in Austin. We'll spend sometime coordinating on these.15:29
thingeeyeah I'll make sure the bugs are finalized by the next time we talk15:29
ttxThat's all the urgent stuff I had15:29
ttxAnything on your side ?15:30
thingeenope. Just gotta get those reviews through. I have confidence in the team and with the revisions a lot of these bps have already had in code reviews.15:30
ttxawesome, have a great sprint then15:30
thingeewelcome back btw15:31
ttxnikhil_k: still not around ?15:31
nikhil_kttx: hi15:31
thingeealthough I notice you work during your travel time :)15:31
ttxnikhil_k: hi!15:31
ttx#topic Glance15:31
ttxthingee: that happens :)15:31
nikhil_kttx: apologies, traveling to a different time zone. missed the time :/15:31
ttxnikhil_k: no problem, mike was early15:31
ttx#link https://launchpad.net/glance/+milestone/kilo-215:32
ttx#info 5 in review, 2 inprogress, 1 notstarted15:32
ttxcompared to 1 inreview, 1 notstarted two weeks ago15:32
ttxso, some progress there but still missing completed ones15:33
ttxnikhil_k: are all of those still looking likely to be completed by next week ?15:33
nikhil_kttx: I have optimistically added the not started onr and the ones not in review yet15:33
ttxthat's optimistic. I like your optimism15:34
nikhil_kso, if you don't mind - can do some cleanup this Friday based on the situation15:34
ttxnikhil_k: that works15:34
ttxespecially if that helps to focus on the remaining reviews15:34
nikhil_kttx: Sorry, had added those a while back. there was not progress on them for some reason15:34
ttxwe'll refine the bug list as well next week15:34
ttxremember we'll need a tag between Tue and Thu next week15:34
ttxnikhil_k: that's all I had, anything on your side ?15:35
nikhil_kSure. The issue is the team is meeting here for mini summit travel15:35
nikhil_kSo, if no reviews come we may have to scrap off many "in review " ones too15:35
nikhil_kHowever, some of them are glance_store BPs15:36
nikhil_kttx: what do you want to do with the bugs?15:36
ttxnikhil_k: we can refine the list so that only milestone blockers are shown... or let them all live and postpone those which won't make it to k315:37
ttxdepends if you want to use the list to communicate blockers or targets of opportunity15:37
nikhil_kok, sounds good!15:37
ttxdavid-lyle: ready when you are15:38
david-lylettx: ready15:39
ttx#topic Horizon15:39
ttx#link https://launchpad.net/horizon/+milestone/kilo-215:39
ttx#info 7 done, 13 inreview, 6 inprogress15:39
ttxstill a lot of ground to cover, but nice progress overall15:40
ttxdon't hesitate to aggressively trim the list when you know it won't make it15:40
david-lyleyeah, lots of reviews left15:40
ttxsame for bugs15:40
ttxnext week we'll trim it down to stuff in flight15:41
david-lyleI've been pruning bps already, a few more will go for sure15:41
ttxfor a tag between Tue and Thu, as soon as you have a SHA15:41
ttxhttps://review.openstack.org/#/c/133241/ merged and implements make-batchaction-help-text-configurable15:42
ttxshould that one be marked completed ?15:42
ttxoh, it is15:42
ttxconfused with add-batchactions-help-text15:42
david-lyleyes the commit message is confusing15:42
david-lylefor the automated tooling15:42
ttxok then, that's all I had15:43
ttxanything you wanted to mention?15:43
david-lyleno, I think we're making solid progress, just a lot of reviews to tackle15:43
ttxhave a great review week then15:43
ttxnotmyname: around?16:51
ttx#topic Swift16:52
ttx#link https://launchpad.net/swift/+milestone/next-kilo16:52
ttxnotmyname: any release in sight?16:52
notmynamelooking for a final +2 on https://review.openstack.org/#/c/147743/16:52
notmynameotherwise, that's it16:52
* notmyname hopes for having it land today16:52
ttx2.2.2 ?16:53
notmyname(because , really, when will we have that chance again for?)16:53
ttxWhat's the target date for final release ?16:53
ttx2/2 ?16:53
notmynameya, next week16:53
ttx2/2 for 2.2.2 sounds appropriate16:53
ttxok, I can tag the rc when you give me the SHA16:54
notmynameI will asa sson as I have it. thanks16:54
notmynameand I'll update LP with the info too16:54
ttxI travel on 2/2 so I may not be around when you get up, but can tag and release first thing on Tuesday morning16:54
* ttx turns next-kilo into 2.2.216:55
notmynameRC this week? as soon as I give you the SHA?16:55
notmynamethen final next week?16:55
ttxif you want to refer to stuff there16:56
notmynameIw ill16:56
ttxok, sounds like a plan16:56
ttxnotmyname: anything else ?16:57
ttxnotmyname: alright then16:57
ttxnotmyname: let me know the SHA when you have it and I'll process it16:57
* ttx needs to update a few release scripts first16:58
ttxmorganfainberg: ready when you are16:58
* morganfainberg is mostly here.16:58
ttx#topic Keystone16:58
ttx#link https://launchpad.net/keystone/+milestone/kilo-216:59
morganfainberglots to review16:59
morganfainbergand i'm actively punting things to k316:59
ttx#info 1 done, 10 inreview, 4 inprogress, 1 notstarted16:59
ttxcompared to 4 inreview, 4 inprogress, 2 notstarted two weeks ago17:00
morganfainbergnot started might be started but the person assigned has been hard to pin down on the topic.17:00
*** notmyname has quit IRC17:00
morganfainbergi opted to leave it not-started until meeting and either punt to k3 or move to correct status17:00
ttxI guess that means a few targets have been added along the way :)17:00
ttx"Keystone to Keystone Service Providers" -- does that one still have a chance to be completed in k2 ?17:01
morganfainbergthat one is under active work and should land this week17:01
ttxso ,same old process next week -- we'll tidy the list to the last milestone blockers during the 1:1 on Tuesday, then tag sometimes between Tuesday and Thursday17:02
morganfainbergsounds good17:02
*** notmyname has joined #openstack-relmgr-office17:02
ttxThe bugs list is pretty tidy now17:02
ttxso good17:02
ttxmorganfainberg: that's all I had17:02
morganfainbergthere might be 1-2 more bugs that end up there17:02
ttxanything on your side ?17:02
morganfainbergbut they would land there becasue they are completed this week17:02
morganfainbergnope i'm good.17:02
ttxgreat, have a good week17:03
*** zz_johnthetubagu is now known as johnthetubaguy17:11
johnthetubaguyttx: sorry, its getting late with you, just wanted to check if you are still around?17:12
ttxjohnthetubaguy: I'm around17:16
ttxshould be with deva though17:16
ttxdevananda: around?17:16
ttxjohnthetubaguy: ok, let's do it now17:16
ttx#topic Nova17:16
johnthetubaguysorry, got distracted17:20
johnthetubaguy#link https://launchpad.net/nova/+milestone/kilo-217:20
johnthetubaguyso, did some tidy stuff, pushed out some things to kilo-317:20
ttx#info 3 done, 52 inreview17:21
johnthetubaguywe probably have some in NeedsCodeReview but are actually complete, but I have not done that yet17:21
ttxup from 22 inreview, 29 inprogress, 17 notstarted two weeks ago17:21
ttxhttps://review.openstack.org/#/c/140408/ concludes virt-driver-cpu-pinning17:22
ttxthat's the only one I spotted17:22
ttxjohnthetubaguy: are you doing reviews on the prio stuff during the Nova meetup ?17:23
johnthetubaguycool, I will mark that as complete, that looks right17:23
johnthetubaguywell I did most of it myself last night, so we could do more of that today17:23
ttxbecause that's a giganormous amount of reviews to convert to fully-implemented17:24
ttxjohnthetubaguy: I propsoe next Tuesday we cull the list down to inflight stuff17:24
ttxthat leaves one week to approve reviews17:24
ttxthen tag betwen Tue and Thu17:24
ttxjohnthetubaguy: does that work for you ?17:24
johnthetubaguythat sounds like a good plan17:25
ttxOK, I won't take more of your precious review time then17:25
devanandattx: here17:25
ttxunless you had something else to discuss17:25
johnthetubaguythat sounds cool17:25
ttx#topic Ironic17:26
johnthetubaguythanks for that, hoping to get some stuff merged17:26
ttxjohnthetubaguy: thx for making it!17:26
ttxdevananda: o/17:26
johnthetubaguyno worries17:26
* johnthetubaguy runs away17:26
ttx#link https://launchpad.net/ironic/+milestone/kilo-217:26
ttx#info 4 inreview, 3 inprogress, 1 blocked, 3 unknown17:26
ttxcompared to 4 inreview, 3 inprogress, 4 blocked 2 weeks ago17:27
ttxnot sure that counts as real progress ;)17:27
devanandathat's a fair summary of our progress17:27
devanandathough, hmm17:27
devanandawe've landed several specs that aren't reflected in targeting17:27
ttxany idea what those unknowns status actually are ?17:27
devanandaeven though I swear I ran spec2bp yesterday17:28
devanandathere is progress on each of those 3 unknownbs17:28
ttxa buggy script ? no way!17:28
* devananda needs to nag people more often to update their BP statuses17:28
ttxdevananda: unknown progress I guess17:29
devanandasome code is up, but not landed, and certainly not complete17:29
ttxdevananda: by Tuesday next week we'll have to trim the list to inflight stuff17:29
ttxand this still looks very much like WIP17:29
devanandagiven the current slow pace of reviews, I suspect we may not complete any of those, but we'll see17:30
ttxso prepare yourself for some serious weed out next week :)17:30
devanandaalso, midcycles17:30
ttxyou can anticipate and defer what is already condemned17:30
devanandanext week is our first sprint17:30
devanandain EU17:30
devanandaand the following week is another sprint (by a mostly non-overlapping set of people) in SF17:30
devanandaso I am expecting us to land a /lot/ of this during those two weeks17:31
ttxas long as you can give me a SHA for k2 sometimes next week between Tue and Thu we should be golden17:31
ttxmaybe focus on what's almost there17:31
ttxand we'll try to delay the tag as much as we can17:31
ttxdevananda: when do you arrive on this side or Earth ?17:31
devanandaif we can do that by EOD thursday UTC+1, that would give us the full sprint time to land essential things17:32
devanandaFriday morning in brussels17:32
ttxyep, that works17:32
devanandanice. I'll let folks know that that's our plan17:32
ttxI'll see you there17:32
ttxdevananda: anything else ?17:34
ttxalright then, see you Friday17:35
openstackMeeting ended Tue Jan 27 17:35:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-01-27-07.58.html17:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-01-27-07.58.txt17:35
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-01-27-07.58.log.html17:35
*** johnthetubaguy is now known as zz_johnthetubagu17:41
-openstackstatus- NOTICE: Gerrit and Zuul will be offline for a few minutes for a security update17:54
*** openstack` has joined #openstack-relmgr-office18:04
sdaguettx: http://status.openstack.org/release/ doesn't seem to be picking up most of the patches18:04
*** openstack` is now known as openstack18:06
ttxsdague: it's pretty brittle, relies on parsing BP whiteboard18:06
sdagueoh... not on topic?18:07
*** thingee has quit IRC18:34
*** SergeyLukjanov has quit IRC18:49
*** SergeyLukjanov has joined #openstack-relmgr-office18:52
ttxsdague: let me find the code for that19:55
ttxsdague: http://git.openstack.org/cgit/openstack-infra/releasestatus/tree/releasestatus.py#n11319:57
ttxnot sure that would be that much more reliable (topic)19:58
ttxcurrently it's the blueprint link in commit messages which triggers BP whiteboard addition, which triggers presence of the patch on the release status page19:58
ttxso... pretty brittle19:59
*** thingee has joined #openstack-relmgr-office20:09
sdaguettx: yeh, and it seems broken there, because it's not picking up some nova patches which are in the whiteboard20:16
*** openstack has joined #openstack-relmgr-office20:38
*** sendak.freenode.net sets mode: +ns 20:38
*** sendak.freenode.net sets mode: -o openstack20:44
-sendak.freenode.net- *** Notice -- TS for #openstack-relmgr-office changed from 1422391088 to 138867215820:44
*** sendak.freenode.net sets mode: +ct-s 20:44
*** nikhil- has joined #openstack-relmgr-office20:44
*** russellb has joined #openstack-relmgr-office20:44
*** stevebak` has joined #openstack-relmgr-office20:44
*** thingee has joined #openstack-relmgr-office20:44
*** SergeyLukjanov has joined #openstack-relmgr-office20:44
*** notmyname has joined #openstack-relmgr-office20:44
*** eglynn has joined #openstack-relmgr-office20:44
*** Kiall has joined #openstack-relmgr-office20:44
*** SlickNik has joined #openstack-relmgr-office20:44
*** jraim has joined #openstack-relmgr-office20:44
*** redrobot has joined #openstack-relmgr-office20:44
*** mestery has joined #openstack-relmgr-office20:44
*** mikal has joined #openstack-relmgr-office20:44
*** anteaya has joined #openstack-relmgr-office20:44
*** dansmith has joined #openstack-relmgr-office20:44
*** dhellmann has joined #openstack-relmgr-office20:44
*** jgriffith has joined #openstack-relmgr-office20:44
*** david-lyle has joined #openstack-relmgr-office20:44
*** devananda has joined #openstack-relmgr-office20:44
*** mordred has joined #openstack-relmgr-office20:44
*** eglynn-officeafk has joined #openstack-relmgr-office20:44
*** ChanServ has joined #openstack-relmgr-office20:44
*** morganfainberg has joined #openstack-relmgr-office20:44
*** mattoliverau has joined #openstack-relmgr-office20:44
*** sdague has joined #openstack-relmgr-office20:44
*** nikhil_k has joined #openstack-relmgr-office20:44
*** flaper87 has joined #openstack-relmgr-office20:44
*** dolphm has joined #openstack-relmgr-office20:44
*** ttx has joined #openstack-relmgr-office20:44
*** zz_johnthetubagu has joined #openstack-relmgr-office20:44
*** sendak.freenode.net sets mode: +o ChanServ20:44
*** sendak.freenode.net 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/"20:44
*** asalkeld has joined #openstack-relmgr-office20:48
*** stevebak` is now known as stevebaker20:59
*** SergeyLukjanov has quit IRC21:02
*** SergeyLukjanov has joined #openstack-relmgr-office21:05
*** asalkeld has left #openstack-relmgr-office21:36
*** dhellmann has quit IRC22:54
*** dhellmann has joined #openstack-relmgr-office22:56
*** eglynn has quit IRC23:25
*** eglynn has joined #openstack-relmgr-office23:38
*** thingee has quit IRC23:38
*** eglynn has quit IRC23:55

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