Difference between revisions of "Meetings/Swift"
< Meetings
Line 5: | Line 5: | ||
Agenda: | Agenda: | ||
− | + | * I don't want swift to depend on swiftclient any more (torgomatic) | |
+ | ** move swift-bench out to its own repository | ||
+ | ** make container-sync not depend on swiftclient. | ||
+ | ** Then we can do crazy things in swiftclient like py3.3 compatibility, or new dependencies (like "six", which helps with py3 compatibility) without transitively doing crazy stuff in swift. | ||
− | + | * Havana release plans/schedule | |
− | + | * huge review queue | |
− | + | ** do we need review days? | |
+ | ** do we need to prune the core devs list? | ||
+ | ** do we need an official "review sprint"? |
Revision as of 18:05, 4 September 2013
Meeting Time: Every other Wednesday at 19:00 UTC
Next Meeting: September 4, 2013
Agenda:
- I don't want swift to depend on swiftclient any more (torgomatic)
- move swift-bench out to its own repository
- make container-sync not depend on swiftclient.
- Then we can do crazy things in swiftclient like py3.3 compatibility, or new dependencies (like "six", which helps with py3 compatibility) without transitively doing crazy stuff in swift.
- Havana release plans/schedule
- huge review queue
- do we need review days?
- do we need to prune the core devs list?
- do we need an official "review sprint"?