Preparing for Bug Day
Topics
- Good topics for bug days allow for steady progress when tackled collaboratively.
- For Bugzilla: Try to focus bug queries such that bug lists are reasonable in length. Mix up the purpose from week to week. (don't just triage bugs every week)
- Triage Unconfirmed
- Dupes
- Verification
- etc
- For Bugzilla: Try to focus bug queries such that bug lists are reasonable in length. Mix up the purpose from week to week. (don't just triage bugs every week)
- Suggestions for future topics:
- ???
- ???
Schedule
| Date | Topic |
|---|---|
| April 6 | Thunderbird 2 Unconfirmed Bug Triage and Testing |
| April 13 | Firefox 3 Unconfirmed Bug Triage and Testing |
| April 20 | tbd |
| April 27 | tbd |
note: don't forget to check the Bug Day Archive page for previously done topics. It's perfectly fine to revisit past topics. The archives page is out of date.
Changes to the Wiki
- Adjust the following items on the Bug Day wiki page as appropriate:
- Topic of the day
- Move the old topic, if it's a unique topic, to the Bug Day Archive page
- Replace the old topic with the new topic
- Include links to bugzilla queries (tinyurls)
- Update status report for the last bugday
- Note who is moderating each session
- Release being targeted: Update links to the builds to be tested (usually trunk)
- Topic of the day
- Update this page with potential topics and schedule them
Promote Bug Days for increased participation
Post announcements to the following areas Tues and Friday prior to each every other Tuesday Bugday:
- QMO Frontpage
- QMO Event Site
- mozilla.dev.quality newsgroup
- MozillaZine forums
- Litmus
- Mailing Lists:
- communityqateam@mozilla.org, vistqa@mozilla.org, macqa@mozilla.org
- Invite Developers to testdays
Misc
- When appropriate, invite developer(s) to participate
- Adjust plan for regional interests if necessary
Needs
- hosts for the Asian and Americas sessions
- a simple to implement rewards program