07:58:43 #startmeeting ptl_sync 07:58:44 Meeting 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:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:58:47 The meeting name has been set to 'ptl_sync' 07:59:04 ttx: back 07:59:06 #topic Trove 07:59:15 #link https://launchpad.net/trove/+milestone/kilo-2 07:59:36 So... kilo-2 milestone is next week 08:00:06 #info 2 done, 7 inreview, 1 inprogress 08:00:12 I've been away for a couple of weeks, and I need to whip that milestone into shape. 08:00:19 Working hard on it this week. 08:00:56 Most of the BPs are still work in progress, so will have to move them to kilo-3. 08:01:25 SlickNik: If all code is not up for review yet, you should switch them to Good progress or Slow progress 08:01:38 because the way it looks now, it just needs reviews 08:01:58 Keep "Needs code review" for those that have all code proposed 08:02:27 Also as soon as you're sure it won't hit next week target, move them to k3 08:02:47 ttx: ++ Sounds good. Will go through them today and mark them to reflect the state more precisely. 08:02:50 no need to continue to claim they will make it 08:03:06 You also have a pretty long bug list 08:03:17 would be good to reduce it to real milestone priorities/blockers 08:03:34 For example, those without an assignee should move to k3 at this point I think 08:04:10 So it would be good to clean that section as well 08:04:25 Agreed. Will do it. 08:04:40 Will send you a note once I've cleaned it up. 08:04:54 SlickNik: sounds good 08:05:08 That's all I had 08:05:21 Anything on your side ? 08:05:35 ttx: Quick heads up that next week is the Trove Mid Cycle Sprint. 08:05:50 So busy getting things organized for that as well. 08:06:13 #link https://wiki.openstack.org/wiki/Sprints/TroveKiloSprint 08:06:14 SlickNik: ok. Remember we'll need a SHA for k2 sometimes between Tuesday and Thursday :) 08:06:44 Alright 08:06:46 Yes, I'll make sure I set aside some time for that amidst the sprint. 08:06:51 Have a good week! 08:07:53 Thanks, I'll drop you a note once I've cleaned out the items on the k2 page a bit — sometime tomorrow. 08:08:23 That's pretty much all I had. 08:08:29 Thanks! 08:10:12 cheers 09:00:47 asalkeld: around? 09:01:18 ttx, hi 09:01:24 #topic Heat 09:01:33 #link https://launchpad.net/heat/+milestone/kilo-2 09:02:10 ttx, i'll push versioned objects to k3 09:02:10 #info 3 done, 4 inprogress 09:02:26 compared to 1 done, 1 inreview, 4 inprogress, 1 uhnknown 2 weeks ago 09:02:57 yeah, progress 09:03:08 i'll weed the others out 09:03:31 yeah, if code is not proposed by end of week, no reason to keep any open 09:03:38 ok 09:03:58 unless you think they can still make it of course 09:04:09 some are small 09:04:15 but no progress 09:04:21 so i'll chase those 09:04:32 https://blueprints.launchpad.net/heat/+spec/lazy-load-outputs 09:04:46 same for bugs, by the end of week you can probably push back those bugfixes that won't make it 09:04:58 ok, makes senses 09:05:33 We'll do the final defers next week, and tag between Tuesday and Thursday 09:05:49 sounds good 09:05:53 Anything on your side ? 09:06:15 no not much on the go 09:06:36 alright... have a good week then! 09:06:41 you too 13:00:35 eglynn: around? 13:01:27 ttx: apols for the lateness 13:01:31 #topic Ceilometer 13:01:33 eglynn: np 13:01:40 #link https://launchpad.net/ceilometer/+milestone/kilo-2 13:01:53 #info 7 inreview, 2 inprogress 13:02:02 all progressing nicely except the hyperV related BPs 13:02:05 compared to 3 inreview, 4 inprogress, 2 blocked two weeks ago 13:02:26 would be good to finalize some of them 13:02:40 if I don't see more traction on the hyper-V work, it'll be punted before EoW 13:02:41 feeling confident they can stiull make it ? 13:02:53 +1 13:03:03 yep, everything else looks do-able 13:03:22 the earlier the better, next week will be busy gatewise 13:03:28 when are you planning to start laying down kilo-2 tags? 13:03:39 we'll tag sometimes between Tuesday and Thursday next week, when you have a SHA for me 13:03:39 Wednesday next week or Thurs? 13:03:46 cool 13:04:02 so next week 1:1 we'll determine the last blockers 13:04:13 sounds like aplan 13:04:30 same for the bugs list, but yours is already quite tidy 13:05:24 I don't think I have much more to say... focus on getting at least some of those completed in time :) 13:05:42 cool 13:05:48 eglynn: anything on your side ?* 13:05:49 re. CrossProjectMeeting this evening, I'll be a few mins late for it 13:05:59 (I'm on half-days PTO all this week) 13:06:24 eglynn: is it fine if we start with the devref stuff? 13:06:31 sure 13:06:48 ok, will keep agenda as-is 13:06:53 cool 13:07:04 have a good (and busy reviewing) week :) 13:07:11 eglynn: you coming to FOSDEM ? 13:07:12 thanks for your time! 13:07:38 ttx: nope, not this year, sadly ... travel budget a bit constrained 13:08:06 eglynn: ack 13:08:14 SergeyLukjanov: ready when you are 13:08:20 ttx, hey 13:08:27 #topic Sahara 13:08:35 #link https://launchpad.net/sahara/+milestone/kilo-2 13:08:50 #info 3 done, 6 inreview 13:09:05 compared with 7 inreview, 1 inprogress, 2 blocked two weeks ago 13:09:23 nice progress, still a lot to covber though 13:09:25 we have a lot of bug fixing 13:09:26 cover* 13:09:36 and unfortunetaly there were a lot of vacations :( 13:09:48 2 of the targeted bugs are unassigned, you still think you can get those fixed ? 13:09:57 the things on review are really near to be merged 13:10:02 ttx, probably not 13:10:31 there were bug fixing day yesterday and bug scratch a week before, so, the issues list in a pretty good shape 13:10:38 https://review.openstack.org/#/c/115884/ is merged and "Implements: blueprint edp-improve-compatibility" -- is that one completed ? 13:11:50 ttx, it was done on hadoop side and on sahara side the CR is on review 13:12:04 ok 13:12:19 ttx, oh, nope, it was merged today, so, moving it to implemented :) 13:12:25 heh 13:12:31 one down, 5 to go 13:12:35 yeah 13:12:56 I've been updating the launchpad page yesterday evening when it wasn't yet approved ;) 13:13:15 SergeyLukjanov: we'll push the tag sometimes between Tue and Thu next week, whenever you have a SHA for me 13:13:24 ttx, most probably one or two bps will be moved to k3 13:13:26 ttx, ack 13:13:43 ack, move BPs / Bugs out to k3 when you know they won't make it 13:13:51 ttx, yup 13:13:55 otherwise we'll revisit the list next week for final blockers adjustment 13:14:13 ttx, I don't think we'll have any critical blockers 13:14:19 SergeyLukjanov: that's all I had... anything on your side ? 13:14:55 ttx, 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 CR 13:15:31 SergeyLukjanov: that would make a good topic for a future cross-project meeting, if you can make it 13:15:43 that will only get worse 13:15:51 ttx, yeah, I think we need to discuss it 13:15:56 https://etherpad.openstack.org/p/sahara-reviews-in-horizon 13:16:03 I will add topic to the meeting agenda 13:16:10 You can push the topic for next week meeting (too late for today's) 13:16:20 so add it to the "backlog" section of the agenda 13:16:25 yeah, sure, that's I was planning to do 13:16:31 SergeyLukjanov: cool 13:16:42 so, nothing more from my side 13:16:47 because it's not just Sahara, it's all projects horizon panels in the future 13:16:47 ttx, thank you 13:16:56 ttx, yeah, exactly 13:17:19 SergeyLukjanov: have a good week! 13:17:28 dhellmann: ready when you are 13:17:45 ttx: here 13:17:50 ttx, you too! 13:18:00 #topic Oslo 13:18:06 #link https://launchpad.net/oslo/+milestone/kilo-2 13:18:12 #link https://launchpad.net/oslo/+milestone/next-kilo 13:18:46 dhellmann: how are you doing on the kilo-2 incubator objectives ? 13:19:15 oslo.log is coming along nicely - dims and I have a patch for nova that's mostly working and seems to prove out the API 13:19:34 that means we should be able to make an official release, and then clean up the incubator bits we've been holding back on deleting 13:19:56 we also have oslo.messaging, oslo.i18n, and oslo.vmware releases coming up this week 13:20:12 with the namespace stuff ? or more ? 13:20:29 the namespace stuff is the main reason, but there will be a few other patches, too 13:20:33 ack 13:20:52 dhellmann: will namespace conversion be completed with those ? Or are there more in the pipe ? 13:21:11 the messaging and vmware releases are the last ones for the namespace conversion 13:21:26 after that we'll be back to the usual feature/bug work 13:21:48 #info oslo.messaging, oslo.i18n, and oslo.vmware releases coming up this week, mostly to drop namespace packages 13:22:08 How is oslo.context doing ? 13:22:36 the 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:50 ok 13:23:02 what about oslo.policy ? It's marked "needs infra" 13:23:17 I think we're waiting for the import to happen, let me check again 13:23:31 ah, no, we have that repo now 13:23:41 fixing 13:23:43 yeah, couldn't find what it was still blocking on 13:24:20 ok, so looking good for next weeks goals overall 13:24:36 I'll have to check with ayoung on that. I don't see any changes open blocking it. 13:24:54 probably just a question of tagging an initial release at this point 13:24:55 yeah, a bit more rushed at the end than I like but I think we'll mostly do all of this -- policy might slip 13:25:16 that could be it. 13:25:41 dhellmann: we have "Avoiding private symbols in Oslo libraries" topic at cross-project meeting today 13:26:10 that's all I had -- anything on your side 13:26:12 ? 13:26:55 that topic is from the ML thread I started. I wanted to make sure the PTLs saw it, since there were no responses. 13:27:00 but that's all I had for this week 13:27:10 alright, see you later at the meetings then 13:27:16 thanks, have a good afternooN! 13:33:41 ttx: 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:35:37 dhellmann: I usually +2/approve when I get another +1 13:36:28 dhellmann: SergeyLukjanov did a few of such reviews in the past 13:36:46 * SergeyLukjanov lurking 13:36:58 dhellmann: bnemec has a question up on the first in line 13:37:02 https://review.openstack.org/#/c/147256/ 13:37:08 ttx: oops, missed that 13:37:20 dhellmann: nothing really blocking though 13:37:26 dhellmann, you could ping me for an additional +1 - I'm pretty interested in release-tools 13:38:03 SergeyLukjanov: have a look at https://review.openstack.org/#/c/143039/ then :) 13:38:13 I need those in for k2 13:38:59 ttx: I replied to bnemec 13:39:04 SergeyLukjanov: thanks, I'll keep that in mind 13:39:49 dhellmann: 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:57 best way* 13:40:56 ttx: definitely, thanks for pointing it out 15:04:25 ttx: Ready and waiting! 15:06:55 ttx: Hold on for a few minutes, baby woke up, I'll ping you back soon. 15:08:13 mestery: ack 15:11:06 ttx: here 15:11:10 #topic Neutron 15:11:18 #link https://launchpad.net/neutron/+milestone/kilo-2 15:11:40 ttx: Not much progress in closing BPs, but a lot of them have had patches landed. 15:11:43 #info 3 done, 20 inreview, 3 inprogress, 1 notstarted 15:12:06 compared to 3 done, 18 inreview, 6 inprogress, 5 notstarted two weeks ago 15:12:17 ttx: Progress is good 15:12:24 so yeah, not that many completion 15:12:51 https://blueprints.launchpad.net/neutron/+spec/reorganize-unit-test-tree still not started ? 15:13:04 does it still have any chance to be completed by next week ? 15:13:07 ttx: I need to ping marun on that one, it's not clear to me on the status. 15:13:22 ttx: He indicated it was fairly trivial (it's mostly moving code around) 15:13:23 ok, defer to k3 if it's doomed 15:13:29 ttx: Ack 15:13:45 otherwise, this is mostly about getting code reviewed and last patches in 15:13:55 ttx: Yes, exactly. 15:14:04 next week we'll probably tidy the list down to what is in the pipe 15:14:09 and tag when that merges 15:14:17 ttx: I hope to start trimming it by Friday actually 15:14:25 Making next week's trimming easier 15:14:30 mestery: I'm fine with that too :) 15:14:36 If things aren't in the queue by Friday, I'll move those ones out. 15:14:44 Next week it'll be a race on what has yet to merge. 15:15:08 would be good to trim down the bug list as well 15:15:25 i.e. if no review, move out of the k2 list 15:15:41 ttx: Ack on that. 15:16:06 I don't think I need to take more of your precious time 15:16:10 anything on your side ? 15:16:17 lol 15:16:30 I just wanted to point out that our "plugin decomposition" has been a great success so far! 15:16:37 I'll have metrics for you next week, but it's looking really good. 15:16:41 you can use the spare 5 min to plug another review :) 15:16:46 rofl :) 15:16:55 That's I'll I've got, thanks ttx! 15:17:01 cool, looking forward to those stats 15:17:23 * ttx still has to work on release scripts that will support uploading neutron-*aas to the neutron LP page 15:17:31 next on my todo list 15:17:35 cool 15:17:39 mestery: have a good week! 15:17:45 ttx: You too! 15:18:36 nikhil_k: ready when you are 15:26:47 thingee: no nikhil_k so far, you can go now if you want 15:27:10 ttx: ok, whew had connection problems...at the cinder midcycle meetup right now :) 15:27:18 #topic Cinder 15:27:19 ttx: no wifi...tethering to a phone just for you 15:27:22 yay 15:27:25 should be quick 15:27:32 #link https://launchpad.net/cinder/+milestone/kilo-2 15:27:47 #info 5 done, 21 inreview 15:28:00 compared to 2 done, 17 inreview, 6 started two weeks ago 15:28:08 I'd say it's time to get all of those in :) 15:28:31 I agree...I have a few I'll be kicking this week unless they get in a better state. 15:28:36 next week we'll refine the list down to waht's inflight in the gate and milestone blockers 15:28:45 Been communicating in reviews/emails to owners of patches that are going slow. 15:28:45 then tagging between Tuesday and Thursday as those get in 15:29:21 It's time to refine the bug list as well -- the ones that don't have review nor assignee are probably good candidates for k3 deferrals 15:29:25 Good thing I have the whole gang here in Austin. We'll spend sometime coordinating on these. 15:29:50 yeah I'll make sure the bugs are finalized by the next time we talk 15:29:56 That's all the urgent stuff I had 15:30:00 Anything on your side ? 15:30:38 nope. 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:58 awesome, have a great sprint then 15:31:03 thanks! 15:31:08 welcome back btw 15:31:14 nikhil_k: still not around ? 15:31:17 ttx: hi 15:31:20 although I notice you work during your travel time :) 15:31:35 nikhil_k: hi! 15:31:42 #topic Glance 15:31:46 thingee: that happens :) 15:31:46 ttx: apologies, traveling to a different time zone. missed the time :/ 15:31:59 nikhil_k: no problem, mike was early 15:32:13 #link https://launchpad.net/glance/+milestone/kilo-2 15:32:30 #info 5 in review, 2 inprogress, 1 notstarted 15:32:44 compared to 1 inreview, 1 notstarted two weeks ago 15:33:00 so, some progress there but still missing completed ones 15:33:28 nikhil_k: are all of those still looking likely to be completed by next week ? 15:33:34 ttx: I have optimistically added the not started onr and the ones not in review yet 15:34:00 that's optimistic. I like your optimism 15:34:02 so, if you don't mind - can do some cleanup this Friday based on the situation 15:34:09 nikhil_k: that works 15:34:22 especially if that helps to focus on the remaining reviews 15:34:37 ttx: Sorry, had added those a while back. there was not progress on them for some reason 15:34:37 we'll refine the bug list as well next week 15:34:50 s/not/no/ 15:34:54 remember we'll need a tag between Tue and Thu next week 15:35:18 nikhil_k: that's all I had, anything on your side ? 15:35:23 Sure. The issue is the team is meeting here for mini summit travel 15:35:46 So, if no reviews come we may have to scrap off many "in review " ones too 15:36:04 However, some of them are glance_store BPs 15:36:18 ok 15:36:37 ttx: what do you want to do with the bugs? 15:37:17 nikhil_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 k3 15:37:30 depends if you want to use the list to communicate blockers or targets of opportunity 15:37:45 ok, sounds good! 15:38:48 cheers 15:38:55 david-lyle: ready when you are 15:39:04 thanks! 15:39:09 ttx: ready 15:39:15 #topic Horizon 15:39:21 #link https://launchpad.net/horizon/+milestone/kilo-2 15:39:42 #info 7 done, 13 inreview, 6 inprogress 15:40:10 still a lot of ground to cover, but nice progress overall 15:40:37 don't hesitate to aggressively trim the list when you know it won't make it 15:40:46 yeah, lots of reviews left 15:40:47 same for bugs 15:41:02 next week we'll trim it down to stuff in flight 15:41:03 I've been pruning bps already, a few more will go for sure 15:41:13 for a tag between Tue and Thu, as soon as you have a SHA 15:41:19 ok 15:42:09 https://review.openstack.org/#/c/133241/ merged and implements make-batchaction-help-text-configurable 15:42:15 should that one be marked completed ? 15:42:25 oh, it is 15:42:34 confused with add-batchactions-help-text 15:42:47 yes the commit message is confusing 15:42:56 for the automated tooling 15:43:00 heh 15:43:07 ok then, that's all I had 15:43:12 anything you wanted to mention? 15:43:29 no, I think we're making solid progress, just a lot of reviews to tackle 15:43:43 indeed 15:43:53 have a great review week then 15:44:07 thanks 16:51:51 notmyname: around? 16:51:57 hello 16:52:03 #topic Swift 16:52:10 #link https://launchpad.net/swift/+milestone/next-kilo 16:52:18 notmyname: any release in sight? 16:52:36 looking for a final +2 on https://review.openstack.org/#/c/147743/ 16:52:43 otherwise, that's it 16:52:52 * notmyname hopes for having it land today 16:53:00 2.2.2 ? 16:53:04 yes 16:53:18 (because , really, when will we have that chance again for?) 16:53:22 s/for// 16:53:24 What's the target date for final release ? 16:53:31 2/2 ? 16:53:34 asap 16:53:47 ya, next week 16:53:53 2/2 for 2.2.2 sounds appropriate 16:53:57 :-) 16:54:29 ok, I can tag the rc when you give me the SHA 16:54:50 I will asa sson as I have it. thanks 16:54:55 and I'll update LP with the info too 16:54:59 I travel on 2/2 so I may not be around when you get up, but can tag and release first thing on Tuesday morning 16:55:04 ok 16:55:10 * ttx turns next-kilo into 2.2.2 16:55:24 RC this week? as soon as I give you the SHA? 16:55:28 then final next week? 16:55:37 yes 16:55:49 ok 16:56:08 https://launchpad.net/swift/+milestone/2.2.2 16:56:17 if you want to refer to stuff there 16:56:30 Iw ill 16:56:56 ok, sounds like a plan 16:57:02 notmyname: anything else ? 16:57:14 no 16:57:44 notmyname: alright then 16:57:48 thanks 16:57:56 notmyname: let me know the SHA when you have it and I'll process it 16:58:09 * ttx needs to update a few release scripts first 16:58:50 morganfainberg: ready when you are 16:58:52 * morganfainberg is mostly here. 16:58:58 #topic Keystone 16:59:18 #link https://launchpad.net/keystone/+milestone/kilo-2 16:59:26 lots to review 16:59:34 and i'm actively punting things to k3 16:59:52 #info 1 done, 10 inreview, 4 inprogress, 1 notstarted 17:00:02 compared to 4 inreview, 4 inprogress, 2 notstarted two weeks ago 17:00:12 not started might be started but the person assigned has been hard to pin down on the topic. 17:00:29 i opted to leave it not-started until meeting and either punt to k3 or move to correct status 17:00:44 I guess that means a few targets have been added along the way :) 17:00:54 yep. 17:01:20 "Keystone to Keystone Service Providers" -- does that one still have a chance to be completed in k2 ? 17:01:25 yes. 17:01:40 that one is under active work and should land this week 17:02:02 so ,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 Thursday 17:02:10 sounds good 17:02:23 The bugs list is pretty tidy now 17:02:32 so good 17:02:36 morganfainberg: that's all I had 17:02:40 there might be 1-2 more bugs that end up there 17:02:44 anything on your side ? 17:02:54 but they would land there becasue they are completed this week 17:02:56 nope i'm good. 17:03:09 great, have a good week 17:03:12 cheers 17:12:29 ttx: sorry, its getting late with you, just wanted to check if you are still around? 17:16:10 johnthetubaguy: I'm around 17:16:17 should be with deva though 17:16:21 devananda: around? 17:16:45 johnthetubaguy: ok, let's do it now 17:16:52 #topic Nova 17:20:05 hey 17:20:13 sorry, got distracted 17:20:23 #link https://launchpad.net/nova/+milestone/kilo-2 17:20:38 so, did some tidy stuff, pushed out some things to kilo-3 17:21:17 #info 3 done, 52 inreview 17:21:21 we probably have some in NeedsCodeReview but are actually complete, but I have not done that yet 17:21:31 up from 22 inreview, 29 inprogress, 17 notstarted two weeks ago 17:22:14 https://review.openstack.org/#/c/140408/ concludes virt-driver-cpu-pinning 17:22:19 that's the only one I spotted 17:23:00 johnthetubaguy: are you doing reviews on the prio stuff during the Nova meetup ? 17:23:04 cool, I will mark that as complete, that looks right 17:23:19 well I did most of it myself last night, so we could do more of that today 17:24:05 because that's a giganormous amount of reviews to convert to fully-implemented 17:24:28 johnthetubaguy: I propsoe next Tuesday we cull the list down to inflight stuff 17:24:34 that leaves one week to approve reviews 17:24:41 then tag betwen Tue and Thu 17:24:50 johnthetubaguy: does that work for you ? 17:25:03 that sounds like a good plan 17:25:16 OK, I won't take more of your precious review time then 17:25:21 ttx: here 17:25:24 unless you had something else to discuss 17:25:50 that sounds cool 17:26:00 #topic Ironic 17:26:05 thanks for that, hoping to get some stuff merged 17:26:05 johnthetubaguy: thx for making it! 17:26:12 devananda: o/ 17:26:13 no worries 17:26:16 * johnthetubaguy runs away 17:26:23 #link https://launchpad.net/ironic/+milestone/kilo-2 17:26:47 #info 4 inreview, 3 inprogress, 1 blocked, 3 unknown 17:27:04 compared to 4 inreview, 3 inprogress, 4 blocked 2 weeks ago 17:27:13 not sure that counts as real progress ;) 17:27:18 yea 17:27:24 that's a fair summary of our progress 17:27:38 though, hmm 17:27:50 we've landed several specs that aren't reflected in targeting 17:27:55 any idea what those unknowns status actually are ? 17:28:00 even though I swear I ran spec2bp yesterday 17:28:32 there is progress on each of those 3 unknownbs 17:28:33 a buggy script ? no way! 17:28:52 * devananda needs to nag people more often to update their BP statuses 17:29:00 devananda: unknown progress I guess 17:29:22 some code is up, but not landed, and certainly not complete 17:29:29 devananda: by Tuesday next week we'll have to trim the list to inflight stuff 17:29:43 and this still looks very much like WIP 17:29:48 indeed 17:30:06 given the current slow pace of reviews, I suspect we may not complete any of those, but we'll see 17:30:09 so prepare yourself for some serious weed out next week :) 17:30:24 also, midcycles 17:30:27 you can anticipate and defer what is already condemned 17:30:29 next week is our first sprint 17:30:37 indeed 17:30:37 in EU 17:30:48 and the following week is another sprint (by a mostly non-overlapping set of people) in SF 17:31:06 so I am expecting us to land a /lot/ of this during those two weeks 17:31:12 as long as you can give me a SHA for k2 sometimes next week between Tue and Thu we should be golden 17:31:29 maybe focus on what's almost there 17:31:40 and we'll try to delay the tag as much as we can 17:31:55 devananda: when do you arrive on this side or Earth ? 17:31:59 of* 17:32:01 if we can do that by EOD thursday UTC+1, that would give us the full sprint time to land essential things 17:32:11 Friday morning in brussels 17:32:12 yep, that works 17:32:21 nice. I'll let folks know that that's our plan 17:32:22 I'll see you there 17:32:26 \o/ 17:34:39 devananda: anything else ? 17:34:58 nope! 17:35:05 alright then, see you Friday 17:35:08 #endmeeting