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