Jump to: navigation, search

Difference between revisions of "Meetings/Nova/BugsTeam"

< Meetings‎ | Nova
(Nova Bugs Team)
(Next meeting dates)
 
(18 intermediate revisions by 4 users not shown)
Line 3: Line 3:
 
This is the weekly ''Nova Bugs Team'' meeting to maintain Nova's bug list: https://bugs.launchpad.net/nova
 
This is the weekly ''Nova Bugs Team'' meeting to maintain Nova's bug list: https://bugs.launchpad.net/nova
  
Contact: Augustina Ragwitz (auggy), Timofey Durakov (tdurakov)
+
Contact: Maciej Szankin (macsz)
  
US/APAC Meeting Chair: auggy
+
US Meeting Chair: macsz
EU Meeting Chair: tdurakov
 
  
 
The IRC channel for daily communication: <code>#openstack-nova</code>
 
The IRC channel for daily communication: <code>#openstack-nova</code>
Line 16: Line 15:
 
= Next meeting dates =
 
= Next meeting dates =
  
* September 27th (Tuesday) 0800 UTC, <code>#openstack-meeting-4</code> (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160830T080000)
+
* March 7th (Tuesday) 1800 UTC <code>#openstack-meeting-4</code> (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170307T180000)
* October 4th (Tuesday) 1800 UTC, <code>#openstack-meeting-4</code> (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160823T180000)
+
* March 21st (Tuesday) 1800 UTC <code>#openstack-meeting-4</code> (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170321T180000)
  
 
= Agenda for next meeting =
 
= Agenda for next meeting =
  
* Current Stats
+
* Announcements
* Mailing List Discussions
+
** Bug Coordinator role for Pike
* Upcoming Important Dates (bug triage day, RC-phase starts, ...)
 
* Reminders
 
**cleanups based on based on http://45.55.105.55:8082/bugs-dashboard.html
 
** volunteers for the rotating ''bug-skimming-duty'': https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
 
 
* Bug Queue Discussions
 
* Bug Queue Discussions
 
** Add your name and a link if you have an administrative question or want feedback on a bug you updated.
 
** 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
 
** ($irc_name) $bug_report_link | $discussion_summary
* Urgent Bug Fixes
+
* Current Bug Fixes
** Add a link if you have any urgent bug fixes that need attention (>2 weeks no review; has proper testing, gate checks give +1, reviewer comments are addressed)
+
** Are you working on a bug fix? Share the link below!
 +
** (auggy): Work item opportunity: getting bug dashboard into infra
 +
** Do you have bug fixes that need attention? Share the link below! (>2 weeks no review; has proper testing, gate checks give +1, reviewer comments are addressed)
 
* Open Discussion
 
* Open Discussion
 
** New to the team? Introduce yourself!
 
** New to the team? Introduce yourself!

Latest revision as of 16:48, 7 March 2017

Nova Bugs Team

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

Contact: Maciej Szankin (macsz)

US Meeting Chair: macsz

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

  • Announcements
    • Bug Coordinator role for Pike
  • Bug Queue 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
  • Current Bug Fixes
    • Are you working on a bug fix? Share the link below!
    • (auggy): Work item opportunity: getting bug dashboard into infra
    • Do you have bug fixes that need attention? Share the link below! (>2 weeks no review; has proper testing, gate checks give +1, reviewer comments are addressed)
  • Open Discussion
    • 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