| NEWS: (updated 2008-09-30) Infrastructure status | New SSH fingerprints | New package signing key |
BugZappers/Meetings/Minutes-2008-Jan-30
From FedoraProject
< BugZappers | Meetings
Contents |
Enhancing Bugbot
- Followup discussion from previous meeting
- Tailor output to be specific to bug triage
- Possibly have a separate bot on a separate channel
ACTION: poelcat to propose what new format would look like
Wiki Updating
- snecklifter updated this page http://fedoraproject.org/wiki/BugZappers/FindingBugs
- Simple click me queries for new triagers to find bugs in need of triage
- http://fedoraproject.org/wiki/BugZappers is front page
- Most pages have been updated, though a few still need tuning and expansion
- Need a good page on locating and triaging duplicate bugs
Identifying Duplicate Bugs
- Need a good wiki page for training
- good example: http://bugzilla.gnome.org/duplicates.cgi
Bugzilla Reporting
- Gnome project has some really good reports and examples
- http://bugzilla.gnome.org/page.cgi?id=reports.html
- http://bugzilla.gnome.org/reports/weekly-bug-summary.cgi
ACTION: jmn to investigate gnome type implementation in Fedora which can better address: 1. identifying duplicate bugs 1. better reports
Suggested Triage Commitment
- Followup to past discussion about whether it makes sense to ask people to commit to triage for a certain length of time
- Some ideas here: http://fedoraproject.org/wiki/BugZappers/Joining #4
- Commit for a full release cycle--from one GA date to another
- Fedora 9 development cycle
- Create two wiki pages
1. Current triagers 1. Past triagers
- Refresh current triagers page at start of each release cycle
- Create a list of functional areas people can self-assign themselves to
1. DECISON: All in attendance thought it was a good idea 1. ACTIONS: a. poelcat to create wiki pages for maintaining a triager list a. jds2001 to create a list of major functional areas and comps groups
Bug Lifecycle Discussion
- thoughts and comments to flame fest created by: http://fedoraproject.org/wiki/JohnPoelstra/BugLifeCycle
- biggest points of contention were
1. having to have a separate bug for each issue AND release 1. bodhi auto-closing ALL bugs without the developer being able to opt out
- lmacken may be able to work around this issue in Bodhi
DECISION: For now drop requirement of limiting one bug to one release
IRC Log
Next Meeting
- Move all unfinished business to next meeting
- Wednesday, February 6, 2007
- 17:00 UTC (12 PM EST)
- #fedora-meeting
- http://fedoraproject.org/wiki/BugZappers/Meetings/Agenda-2008-Feb-06
