Jump to: navigation, search

Difference between revisions of "Meetings/Nova/BugsTeam"

< Meetings‎ | Nova
(Agenda for next meeting)
(Agenda for next meeting)
Line 20: Line 20:
  
 
* Info
 
* Info
** Stats about where we are right now: http://45.55.105.55:3000/dashboard/db/openstack-bugs
+
** Stats about where we are right now
 
** Discussions on the ML
 
** Discussions on the ML
 
** Important future dates (bug triage day, RC-phase starts, ...)
 
** Important future dates (bug triage day, RC-phase starts, ...)
 
** Reminder: cleanups based on based on http://45.55.105.55:8082/bugs-dashboard.html
 
** Reminder: cleanups based on based on http://45.55.105.55:8082/bugs-dashboard.html
 
** Reminder: volunteers for the rotating ''bug-skimming-duty'': https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
 
** Reminder: volunteers for the rotating ''bug-skimming-duty'': https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
 
* Last Week's Action Items
 
** results/conclusions/left items?
 
  
 
* Bug Report Discussions:
 
* Bug Report Discussions:

Revision as of 16:51, 20 September 2016

Nova Bugs Team

This is the weekly Nova Bugs Team meeting to maintain Nova's bug list: https://bugs.launchpad.net/nova

Contact: Augustina Ragwitz (auggy)

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

  • Bug Report Discussions:
    • Add your name and a link if you have an administrative question or want feedback on a bug you updated.
    • ($irc_name) $bug_report_link | $discussion_summary
  • Open Discussion
    • Reviews for urgent bug fixes needing attention (>2 weeks no review; has proper testing, gate checks give +1, reviewer comments are addressed)
    • New to the team? Introduce yourself!

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