Difference between revisions of "Meetings/Nova/BugsTeam"
m (→Queries) |
|||
| Line 11: | Line 11: | ||
= Next meeting dates = | = Next meeting dates = | ||
| − | + | = Next meeting dates = | |
| − | * | + | * March 1st 2016 1000 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T100000) |
| − | * | + | * March 8th 2016 1800 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160308T180000) |
| − | * March | + | * March 15th 2016 1000 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160315T100000) |
| + | |||
| + | * March 22nd 2016 1800 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160322T180000) | ||
= Agenda for next meeting = | = Agenda for next meeting = | ||
| + | * open questions round | ||
| + | * discuss process adjustments/changes if necessary | ||
* status of action items from last week | * status of action items from last week | ||
* discuss and set the ''report-priority'' of bugs since the last meeting if not yet done. | * discuss and set the ''report-priority'' of bugs since the last meeting if not yet done. | ||
| Line 28: | Line 32: | ||
* get one or more volunteers for the rotating ''bug-skimming-duty''. Get feedback from the volunteers from the previous week if there are noteworthy items. | * get one or more volunteers for the rotating ''bug-skimming-duty''. Get feedback from the volunteers from the previous week if there are noteworthy items. | ||
* reviews for bug fixes which needs attention? (>2 weeks no review) | * reviews for bug fixes which needs attention? (>2 weeks no review) | ||
| − | |||
| − | |||
= Queries = | = Queries = | ||
Revision as of 16:27, 29 February 2016
Contents
Nova Bugs Team
This is the weekly Nova Bugs Team meeting to maintain Nova's bug list: https://bugs.launchpad.net/nova
Contact: Markus Zoeller (markus_z)
The IRC channel for daily communication: #openstack-nova
Eavesdrop: http://eavesdrop.openstack.org/#Nova_Bugs_Team_Meeting
Next meeting dates
Next meeting dates
- March 1st 2016 1000 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T100000)
- March 8th 2016 1800 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160308T180000)
- March 15th 2016 1000 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160315T100000)
- March 22nd 2016 1800 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160322T180000)
Agenda for next meeting
- open questions round
- discuss process adjustments/changes if necessary
- status of action items from last week
- discuss and set the report-priority of bugs since the last meeting if not yet done.
- decide action items for bug reports which need further attention
- expire bugs which are hit by the expiration-policy unless someone disagrees.
- reset In Progress bugs if no patch is available,
- check if we need new tags for functional areas
- get one or more volunteers for the rotating bug-skimming-duty. Get feedback from the volunteers from the previous week if there are noteworthy items.
- reviews for bug fixes which needs attention? (>2 weeks no review)
Queries
- All new bugs
- Best search for bug skimming. Some of these need to be skimmed. Any bugs that can't be confirmed need to be tagged as "needs-attention".
- Untagged bugs
- Bugs that need to be skimmed. Not the best search for skimming because the list won't include anything tagged by the owner or that includes other projects where the bug may have been tagged.
- Potentially stale bugs
- If the assignee has not submitted a patch in 2 weeks, leave a comment informing the assignee that if they have a patch in review, they need to link it and they can update the bug back to "In Progress" and assign it to themselves. Mark as "Confirmed" and remove the assignee.
- Incomplete bugs
- Make sure the bug is truly in an INCOMPLETE state, it's possible the state was never updated after the requester provided the missing info. If the bug is truly INCOMPLETE and has been so for more than 30 days, mark as WONTFIX.
- Official bug tags
Process / Docs
- The Nova bug tagging process: https://wiki.openstack.org/wiki/Nova/BugTriage
- General OpenStack process (Note the definition of priorities): https://wiki.openstack.org/wiki/BugTriage
- Bug Filing Recommendations: https://wiki.openstack.org/wiki/BugFilingRecommendations
