Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Trove Meeting, March 18, 2015) |
(→Trove Meeting, March 18, 2015) |
||
| Line 29: | Line 29: | ||
*[peterstac] Come up with a strategy to deal with Mock()ing utility methods | *[peterstac] Come up with a strategy to deal with Mock()ing utility methods | ||
** We have several patchsets that are mocking execute_with_timeout, which can cause unexpected behaviour. | ** We have several patchsets that are mocking execute_with_timeout, which can cause unexpected behaviour. | ||
| − | ** For context see: https://review.openstack.org/#/c/156486/ | + | ** For context see: https://review.openstack.org/#/c/156486/ and https://review.openstack.org/#/c/138719/ |
*[sushilkm] Different timeouts in configuration based per datastore | *[sushilkm] Different timeouts in configuration based per datastore | ||
**https://review.openstack.org/#/c/164640/ | **https://review.openstack.org/#/c/164640/ | ||
Revision as of 17:42, 18 March 2015
Weekly Trove Team Meeting
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:
Guidelines for Writing Clear Agenda Items
An agenda item should have a clearly defined objective.
- [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.
- Bad: Discuss blueprint ‘xyz’
- Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.
When referring to previous conversations or competing viewpoints, be sure to summarize them.
Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.
Trove Meeting, March 18, 2015
- [SlickNik] Trove pulse update:
- [SlickNik] Openstack Feature Freeze this week for kilo-3:
- [SlickNik] Switch from oslo namespace packages to "oslo_" style modules
- [peterstac] Come up with a strategy to deal with Mock()ing utility methods
- We have several patchsets that are mocking execute_with_timeout, which can cause unexpected behaviour.
- For context see: https://review.openstack.org/#/c/156486/ and https://review.openstack.org/#/c/138719/
- [sushilkm] Different timeouts in configuration based per datastore
