|
|
| Line 1: |
Line 1: |
| | Meeting Time: Every Wednesday at 19:00 UTC in #openstack-meeting | | Meeting Time: Every Wednesday at 19:00 UTC in #openstack-meeting |
| | | | |
| − | For the meeting : May 28 2014
| + | Next meeting: June 11, 2014 |
| | | | |
| − | Subject: I think there should be better handling of Swift related bugs.
| + | *Note:* June 4 meeting skipped because of the Swift hackathon in Denver |
| − | I am not talking about bugs that are assigned to people and they don't work on them. I am talking about bugs that are not assigned.
| |
| − | Current list of such Swift bugs is a salad of features, suggestions, bugs that are unassigned but patches were submitted, or bugs that should be closed since they are not relevant ( those are the most annoying, since people can resolve them and then after the patch will land on Gerrit - they will face -2)
| |
| − | For example https://bugs.launchpad.net/swift/+bug/1308446 this one is New, unassigned, not in progress. However digging into reviews, one can find that the patch
| |
| − | https://review.openstack.org/#/c/88204/ was submitted on Apr 17 2014.
| |
| − | (Gil Vernik)
| |
| − | | |
| − | Next Meeting: May 21 2014
| |
| − | | |
| − | | |
| − | | |
| − | Agenda:
| |
| − | * Summit Follow-up
| |
| − | ** What did you think? What can we do better next time?
| |
| − | ** Action Items
| |
| − | *** object-specs repo
| |
| − | *** python3 plan
| |
| − | *** core mentors
| |
| − | *** better docs
| |
| − | *** ops/deployer requests
| |
| − | *** helping contributors
| |
| − | *** distributed tracing
| |
| − | *** better replication
| |
| − | * Storage Policies Plan
| |
| − | * Parallel object auditor patch: what else needs to be done?
| |
| − | * Open Discussion
| |
Revision as of 17:12, 3 June 2014
Meeting Time: Every Wednesday at 19:00 UTC in #openstack-meeting
Next meeting: June 11, 2014
- Note:* June 4 meeting skipped because of the Swift hackathon in Denver
