21:00:05 #startmeeting swift 21:00:06 Meeting started Wed Sep 9 21:00:05 2015 UTC and is due to finish in 60 minutes. The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:10 The meeting name has been set to 'swift' 21:00:12 hello, everyone 21:00:17 who's here for the swift meeting? 21:00:17 o/ 21:00:18 o/ 21:00:20 yo 21:00:21 hi 21:00:21 o/ 21:00:23 hey 21:00:23 hi 21:00:36 o/ 21:00:45 <- 21:01:05 welcome 21:01:09 o/ 21:01:10 agenda is 21:01:11 #link https://wiki.openstack.org/wiki/Meetings/Swift 21:01:13 hello 21:01:18 hola! 21:01:25 not a ton of topics, but a few important ones 21:01:37 #topic general updates 21:01:48 first up, some general updates 21:02:03 we did a swiftclient release earlier this week 21:02:14 thanks acoles for helping me out there while I was offline 21:02:19 np 21:02:26 that's the python-swiftclient 2.6.0 21:02:55 looking ahead, we do have the chance to do another swiftclient bugfix release if necessary and have that in "Liberty" 21:03:00 yo 21:03:14 but not more significant changes 21:03:28 I'm not anticipating that we'd do that. but if it's necessary, we can 21:03:53 o/ 21:04:05 also, because of the way versioning works, the next release of it that is after the liberty release will be at least 2.7.0 (increasing the minor version) 21:04:36 so, we better improve swiftclient enough that it deserves it :) 21:04:44 heh :-) 21:05:45 also, I'm working on some new tshirts. I'd appreciate it if you could fill this out soon, if you haven't already. it will take less than a minute https://www.surveymonkey.com/r/5WQ7Y9F 21:06:23 I don't have final artwork yet, so no I can't show you the design yet ;-) 21:06:46 notmyname: does it have a bird on it? ;) 21:06:55 hurricanerix: good guess! 21:07:12 jrichli, can it be translated to cookie form ? : ) 21:07:22 perhaps 21:07:22 and it would be very rude to quickly resell such a shirt for profit 21:07:57 #topic swift this month 21:08:07 notmyname: just a tip: google translate for swift 迅速 :) 21:08:22 nobody? bah. 21:08:27 tdasilva: don't use it 21:08:32 lol 21:08:35 heh 21:08:47 I would have to have confirmation on that from kota_ and ho first ;-) 21:08:52 kota_, does it have a completely different meaning ? : ) 21:09:03 absolutely 21:09:12 torgomatic: people might think its for apple swift 21:09:12 "rapid" 21:09:21 yes 21:09:42 or quickly? 21:09:52 kota_: forgot to click on the "6 more translations" button 21:09:52 yeah. "quick" 21:09:52 * torgomatic was just hoping someone would ask about the shirt-resale so he'd get to say "flipping the bird" in an officially-logged meeting 21:09:54 anyway I guess it is not Swift. 21:10:08 kota_: +1 21:10:10 grown 21:10:15 :-) 21:10:21 ok 21:10:25 so swift this month... 21:10:26 ;-) 21:10:42 torgomatic: what do mean about the shirt resale? :) 21:11:04 we need a release by the end of the month that will be in the Liberty openstack reelase 21:11:12 here's the release schedule for it 21:11:16 #link https://wiki.openstack.org/wiki/Liberty_Release_Schedule 21:11:27 note that the liberty release is oct 15 21:11:32 o-pensutakku suifuto 21:12:18 so we need to have our release ready at the end of the month. gives us a small window for last minute bug fixes, if they show up 21:12:32 here's how release versions will work now (it's slightly different) 21:12:40 we are not doing RC tags any more 21:13:03 instead, we'll cut a release, eg 2.5.0 21:13:19 then if we find something, we'll patch/backport it and make a 2.5.1 release 21:13:47 and as time goes on an if we need to do a backport, we'll do that on whatever the next version is, eg 2.5.2 21:14:13 basically, like the swiftclient, the first release in the M cycle will need to increment the minor version number 21:15:02 so we'll likely do a swift 2.5.0 release at the end of the month. possibly followed by a 2.5.1 (and 2.5.x for long-term backports). and in the M cycle we'll start with 2.6.0 21:15:04 make sense? 21:15:44 ok :-) 21:15:49 so liberty will == 2.5.x whatever x is on release day? 21:15:59 acoles: yes 21:16:10 makes sense 21:16:30 and if we have a backport to do in 6 months, that will be 2.5.x+1 21:16:49 so the next thing is dependencies 21:16:57 I think the only thing in question on pyeclib 21:17:16 we need to get the right versions of the dependencies into global-requirements asap 21:17:30 kota_: I believe you were asking about pyeclib 21:17:41 peluse__: 21:17:56 I need to check with tsg on the state of things there 21:18:04 currently, tsg- is working on bumping pyeclib 21:18:08 ok, good 21:18:23 are there any other dependency changes that anyone knows of? 21:18:29 he said, yesterday he wanted to push it latest 1.0.9 into pypi, but seems not yet. 21:18:42 kota_: ok. I'll bug him about it 21:19:50 no other dependency updates? 21:20:29 so that just leaves everything else 21:20:31 notmyname: was a decision made on where pyeclib source code will be moved to? or if it will be moved at all? 21:20:56 tdasilva: not yet. like the releases of pyeclib, that conversation is going slowly 21:21:02 ok 21:21:09 tdasilva: and actually, I'm ok with waiting until after liberty to change it 21:21:51 notmyname: understood 21:21:52 the point to change it is for long-term maintenance and speed of doing releases/patches. ie not because something is broken today 21:22:08 so stuff to get done by the end of the month for a swift release 21:22:24 obviously, there's still a ton of stuff going on in the community 21:23:01 the EC issues should take priority to land. we should release with as few known, open EC bugs as possible 21:23:06 #link https://bugs.launchpad.net/swift/+bugs?field.tag=ec 21:23:41 I could use some help in that list. I want to go through the "undecided" ones and set a priority. can someone help me with that? 21:24:30 notmyname: I'd be up for it. 21:24:38 minwoob_: thanks! 21:24:44 notmyname: Np. 21:25:04 me too. 21:25:05 notmyname: minwoob and i presented the idea to peluse late last week and he said he'd look into prioritizing the remaining open EC bugs 21:25:14 great 21:25:38 if we can get those ranked today or tomorrow, then we can have a good sense of what's left and what's possible to get done 21:25:59 notmyname: it'd be also great to have core members leave some inputs (i understand how thin of time they have across countless Swift bugs) 21:26:22 wbhuber: yeah. I saw your comment earlier (and responded) ;-) 21:26:42 any other questions about stuff for swift in liberty? 21:27:03 as patches, especially EC patches, are proposed, I'll keep the stars up to date 21:27:40 We can probably discuss in #openstack-swift regarding prioritization of the remaining EC bugs. 21:27:46 minwoob_: yes 21:28:05 minwoob_: +1 21:28:14 ok, let's move on to the summit then 21:28:22 #topic tokyo summit 21:28:43 I hope you've started your japan visa process if necessary. 21:29:12 several of you have talks (that's great!!). please let me know if I can do anything to help you prepare 21:29:25 the summit is tuesday-friday 21:29:44 kota_ says he's going to throw a party for us 21:30:13 the thing we need to do is come up with the topics for the tech sessions 21:30:31 this summit has the same room types as vancouver did 21:30:39 I'm in prep tho... 21:30:43 fishbowls are large rooms for large discussions 21:31:05 working sessions are smaller rooms, and the topic is buried in the description 21:31:13 and there is a free-form meetup on friday 21:31:34 for this summit, we have 2 fishbowls, 12 working rooms, and the full day on friday 21:32:31 as opposed to fish goals, which are something that you have to do in school 21:32:33 boom. there 21:32:34 https://etherpad.openstack.org/p/tokyo-summit-swift 21:32:40 #link https://etherpad.openstack.org/p/tokyo-summit-swift 21:32:55 let's use that etherpad for coordinating and collecting topic ideas 21:33:13 nice 21:34:07 so start filling it out, and as we get closer we'll rank the proposed topics and I'll figure out a schedule for them 21:35:43 any other questions about the summit? 21:36:28 ok, moving on 21:36:35 #topic open discussion 21:36:38 do we have a projector in the rooms? 21:36:41 yes! 21:36:50 or at least a largeish TV 21:36:50 nice! 21:37:26 It would be great to have some container sync improvements land. patch 205803 would be a good one. 21:37:26 jrichli: https://review.openstack.org/#/c/205803/ 21:37:35 next week's meeting: I'll be traveling. either let's cancel or someone else volunteer to lead this meeting 21:39:18 i think we know what we have to focus on for 2-3 weeks 21:39:26 so could skip a meeting 21:39:28 jrichli: thanks. I know that IBM really wants those container sync patches to land 21:39:40 acoles: :-) 21:40:00 notmyname: sorry to rewind a little - where will the ranking of EC bugs/patches be recorded? 21:40:16 acoles: was thinking along that line too 21:40:31 acoles: first step is to set the priority in LP. from there we'll be able to write them down in ranked order 21:41:17 notmyname: ok. maybe on priority reviews page? 21:41:18 I can (ab)use the https://wiki.openstack.org/wiki/Swift/PriorityReviews page for that 21:41:23 acoles: yeah :-) 21:41:30 yup. that :) 21:41:57 ok, so I don't hear any calls for a meeting next week. let's skip it 21:42:14 anything else for this week? 21:42:42 if anybody has a chance, please review: https://review.openstack.org/#/c/210117/ 21:43:42 tdasilva: nice 21:43:52 reading in today's working. 21:44:01 kota_: thanks 21:44:48 thanks for working on Swift! 21:44:51 #endmeeting