Jump to: navigation, search

Difference between revisions of "Meetings/Nova/BugsTeam"

< Meetings‎ | Nova
(added bugs I'd like to discuss)
(introduce "bug report discussions" to talk about specific reports and lessons-learned or questions.)
Line 22: Line 22:
  
 
= Agenda for next meeting =
 
= Agenda for next meeting =
 +
 
* info round
 
* info round
 
** some stats about where we are right now: http://45.55.105.55:3000/dashboard/db/openstack-bugs
 
** some stats about where we are right now: http://45.55.105.55:3000/dashboard/db/openstack-bugs
 
** 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: volunteers for the rotating ''bug-skimming-duty'': https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
 +
 
* last weeks action items
 
* last weeks action items
 
** results/conclusions/left items?
 
** results/conclusions/left items?
* new action items
+
 
** specific bugs to discuss
+
* bug report discussions:
*** (markus_z) https://bugs.launchpad.net/nova/+bug/1610069 I don't know if the "policy.json" cleanup maybe removed too much. @alaski|claudiub
+
** (markus_z) https://bugs.launchpad.net/nova/+bug/1608726 TIL: The API doesn't wait for other calls to succeed|fail. There is no pipeline.
*** (markus_z) https://bugs.launchpad.net/nova/+bug/1610393 I don't know how the api extensions work @alex_xu|sdague
+
** ($irc_name) $bug_report_link | $discussion_summary
** split tasks based on http://45.55.105.55:8082/bugs-dashboard.html
+
 
** get one or more volunteers for the rotating ''bug-skimming-duty'': https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
 
** Get feedback from the volunteers from the previous week if there are noteworthy items.
 
 
* open round
 
* open round
 
** reviews for urgent bug fixes which needs attention? (>2 weeks no review; has proper testing, gate checks give +1, reviewer comments are addressed)
 
** reviews for urgent bug fixes which needs attention? (>2 weeks no review; has proper testing, gate checks give +1, reviewer comments are addressed)

Revision as of 12:09, 10 August 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

  • last weeks action items
    • results/conclusions/left items?
  • open round
    • reviews for urgent bug fixes which needs attention? (>2 weeks no review; has proper testing, gate checks give +1, reviewer comments are addressed)
    • new contributor who likes to have mentoring or has general bug triage questions?

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