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

March 7th (Tuesday) 1800 UTC #openstack-meeting-4 (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170307T180000)
March 21st (Tuesday) 1800 UTC #openstack-meeting-4 (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170321T180000)

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

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

Previous meetings

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

@@ Line 3: / Line 3: @@
 This is the weekly ''Nova Bugs Team'' meeting to maintain Nova's bug list: https://bugs.launchpad.net/nova
-Contact: Markus Zoeller (markus_z)
+Contact: Maciej Szankin (macsz)
-The IRC channel for daily communication: #openstack-nova
+US Meeting Chair: macsz
-= Next meeting dates =
+The IRC channel for daily communication: <code>#openstack-nova</code>
-* February 9th 2016 1800 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160209T180000)
+Eavesdrop: http://eavesdrop.openstack.org/#Nova_Bugs_Team_Meeting
-* '''Cancelled:''' February 16th 2016 1000 UTC
+Etherpad: https://etherpad.openstack.org/p/nova-bugs-team
-* February 23rd 2016 1800 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160209T180000)
+= Next meeting dates =
-* March 1st 2016 1000 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160209T100000)
+* March 7th (Tuesday) 1800 UTC <code>#openstack-meeting-4</code> (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170307T180000)
+* March 21st (Tuesday) 1800 UTC <code>#openstack-meeting-4</code> (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170321T180000)
 = Agenda for next meeting =
-* status of action items from last week
-* discuss and set the ''report-priority'' of bugs since the last meeting if not yet done.
+* Announcements
-* decide action items for bug reports which need further attention
+** Bug Coordinator role for Pike
-* expire bugs which are hit by the ''expiration-policy'' unless someone disagrees.
+* Bug Queue Discussions
-* 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.
+** Add your name and a link if you have an administrative question or want feedback on a bug you updated.
-* reset ''In Progress'' bugs if no patch is available,
+** ($irc_name) $bug_report_link | $discussion_summary
-* check if we need new tags for functional areas
+* Current Bug Fixes
-* spreading knowledge and discuss open points
+** Are you working on a bug fix? Share the link below!
-* discuss process adjustments/changes if necessary
+** (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 =
 * [https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 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".
 * [https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 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.
 * [https://bugs.launchpad.net/nova/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any 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.
 * [https://bugs.launchpad.net/nova/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on 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.
 * [https://bugs.launchpad.net/nova/+manage-official-tags Official bug tags]
@@ Line 41: / Line 49: @@
 = Previous meetings =
-<none>
+: http://eavesdrop.openstack.org/meetings/nova_bugs_team/2016
 [[Category: Nova]]
 [[Category: meetings]]

Difference between revisions of "Meetings/Nova/BugsTeam"