Difference between revisions of "Meetings/Swift"
< Meetings
| Line 19: | Line 19: | ||
** https://bugs.launchpad.net/swift/+bug/1580678 status update | ** https://bugs.launchpad.net/swift/+bug/1580678 status update | ||
** is there any sensible gate job that would give some protection? e.g. pick a locale known to have non-ascii characters in translations | ** is there any sensible gate job that would give some protection? e.g. pick a locale known to have non-ascii characters in translations | ||
| + | ** https://review.openstack.org/#/c/323950/ | ||
* Send correct size in POST async update for EC object | * Send correct size in POST async update for EC object | ||
** https://review.openstack.org/#/c/317475/ | ** https://review.openstack.org/#/c/317475/ | ||
Revision as of 21:00, 1 June 2016
| Meeting Time | Every Wednesday at 21:00 UTC in #openstack-meeting |
| Meeting Logs | http://eavesdrop.openstack.org/meetings/swift/2016/ |
| Chair | notmyname |
Agenda: June 1, 2016 2100 UTC
- crypto update [jrichli, acoles]
- rolling upgrade test status update [cschwede]
- pyeclib/liberasurecode migration status update [tdasilva]
- symlinks [tdasilva]
- bugs arising from translations [cschwede]
- https://bugs.launchpad.net/swift/+bug/1580678 status update
- is there any sensible gate job that would give some protection? e.g. pick a locale known to have non-ascii characters in translations
- https://review.openstack.org/#/c/323950/
- Send correct size in POST async update for EC object
- crazy idea? only one +2 for landing code. discuss... [notmyname]
When adding an item, please include your IRC nickname with it.
