Jump to: navigation, search

Difference between revisions of "Meetings/Nova/BugsTeam"

< Meetings‎ | Nova
m (add etherpad remove past meeting)
(Previous meetings)
Line 48: Line 48:
  
 
= Previous meetings =
 
= Previous meetings =
http://eavesdrop.openstack.org/meetings/nova_bugs_team/
+
2016: http://eavesdrop.openstack.org/meetings/nova_bugs_team/2016
  
  
 
[[Category: Nova]]
 
[[Category: Nova]]
 
[[Category: meetings]]
 
[[Category: meetings]]

Revision as of 12:32, 1 March 2016

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

Etherpad: https://etherpad.openstack.org/p/nova-bugs-team

Next meeting dates

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

Previous meetings

2016: http://eavesdrop.openstack.org/meetings/nova_bugs_team/2016