#openstack-meeting: swift（2015-09-02）

Meeting summary

1. 1. https://wiki.openstack.org/wiki/Meetings/Swift (notmyname, 21:01:23)
   
   
2. swift releases (notmyname, 21:02:00)
   1. we released 2.4.0 yesterday (notmyname, 21:02:12)
   2. http://lists.openstack.org/pipermail/openstack-announce/2015-September/000575.html (notmyname, 21:02:42)

      21:07:25 <notmyname> looking at the calendar (when the liberty release is) and where we are now and when the expected RC windows are done....
      21:07:30 <notmyname> that gives us one month
      21:07:57 <notmyname> so, one month from now -- ie the end of september, give or take a day or two -- will be our next release
      21:08:02 <notmyname> 4 weeks from today
      21:08:26 <notmyname> depending on what lands, that will be either 2.4.1 or 2.5.0

   3. https://review.openstack.org/#/c/202657/ looks like a nice improvement and already has 1 +2, so I left it there (notmyname, 21:10:25)
   4. ACTION: notmyname to find the liberty dependency freeze date (notmyname, 21:12:43)
   
   
3. swiftclient release (notmyname, 21:18:37)
   1. https://review.openstack.org/#/q/status:open+project:openstack/python-swiftclient,n,z (notmyname, 21:20:27)
   2. https://bugs.launchpad.net/python-swiftclient/ (notmyname, 21:21:41)

      21:23:33 <notmyname> although I haven't fully looked, I expect the next swiftclient release to be 2.6.0

   
   
4. global ec cluster spec (notmyname, 21:31:41)
   1. https://review.openstack.org/#/c/209447/3/specs/in_progress/global_ec_cluster.rst,unified (notmyname, 21:33:18)

      21:34:11 <notmyname> kota_: after reading over it, it seems like you're presenting an idea, but not too much detail on implementation

      21:34:25 <notmyname> other than "we duplicate all the EC fragments"

   
   
5. open discussion (notmyname, 21:52:17)