Difference between revisions of "Meetings/Nova"
< Meetings
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
Line 15: | Line 15: | ||
** bug triage: | ** bug triage: | ||
*** updates from lifeless? | *** updates from lifeless? | ||
− | *** strategy for tagging gate breaker bugs? tag with 'testing' or is that too broad? jog0 has been marking them as icehouse-1 and critical, but should we also tag with 'gate-break' or 'ci' or something else to group them for focus? | + | *** strategy for tagging gate breaker bugs? tag with 'testing' or is that too broad? jog0 has been marking them as icehouse-1 and critical, but should we also tag with 'gate-break' or 'ci' or something else to group them for focus? |
− | **** Should we have a dedicated group that works on quickly resolving gate breakage bugs so that jog0 doesn't have to kill himself when these start piling up? | + | **** Should we have a dedicated group that works on quickly resolving gate breakage bugs so that jog0 doesn't have to kill himself when these start piling up? ML on this: http://lists.openstack.org/pipermail/openstack-dev/2013-November/020048.html |
* blueprints | * blueprints | ||
** There are blueprints for nova supporting glance and cinder v2 APIs, but they are stalled, discussion is here: http://lists.openstack.org/pipermail/openstack-dev/2013-November/020041.html | ** There are blueprints for nova supporting glance and cinder v2 APIs, but they are stalled, discussion is here: http://lists.openstack.org/pipermail/openstack-dev/2013-November/020041.html |
Revision as of 19:26, 21 November 2013
Contents
Weekly Nova team meeting
MEETING TIME: Thursdays at 21:00 UTC
This meeting is a weekly gathering of developers working on OpenStack Compute (Nova). We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.
Agenda for next meeting
Scheduled for November 21, 2013, 21:00 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131121T2100)
- General announcements
- compute program mission statement
- sub-teams
- bugs
- bug triage:
- updates from lifeless?
- strategy for tagging gate breaker bugs? tag with 'testing' or is that too broad? jog0 has been marking them as icehouse-1 and critical, but should we also tag with 'gate-break' or 'ci' or something else to group them for focus?
- Should we have a dedicated group that works on quickly resolving gate breakage bugs so that jog0 doesn't have to kill himself when these start piling up? ML on this: http://lists.openstack.org/pipermail/openstack-dev/2013-November/020048.html
- bug triage:
- blueprints
- There are blueprints for nova supporting glance and cinder v2 APIs, but they are stalled, discussion is here: http://lists.openstack.org/pipermail/openstack-dev/2013-November/020041.html
- open discussion
- oslo sync:
- ML: http://lists.openstack.org/pipermail/openstack-dev/2013-November/019098.html
- Important because of lifeless's sync for the recent gate breakage: https://review.openstack.org/#/c/57509/ and then this: https://review.openstack.org/#/c/57511/
- oslo sync:
Sub-teams
There are also some Nova subteam meetings. See Teams#Nova_subteams for details.