QA/Community/Bug Day/Planner: Difference between revisions

From MozillaWiki
< QA‎ | Community‎ | Bug Day
Jump to navigation Jump to search
Line 14: Line 14:
** Update links to the builds to be tested (usually trunk)
** Update links to the builds to be tested (usually trunk)
* Update this page with potential topics and schedule them
* Update this page with potential topics and schedule them
* Promoting Bug Days - Announcements should be posted to the following areas:
* Promoting Bug Days - Announcements should be posted to the following areas Thursday and Monday prior to each Tuesday Bugday:
** Mozilla QA blog
** Mozilla QA blog
** MozillaZine Firefox build Forum
** MozillaZine Firefox build Forum

Revision as of 04:40, 20 March 2007

« back to Mozilla_QA_Community Bug Day

Work in progress - watch for falling wikicode...

Preparing for Bug Day

  • Change 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
    • Releases being targeted
    • Update links to the builds to be tested (usually trunk)
  • Update this page with potential topics and schedule them
  • Promoting Bug Days - Announcements should be posted to the following areas Thursday and Monday prior to each Tuesday Bugday:
    • Mozilla QA blog
    • MozillaZine Firefox build Forum
    • moz.dev.quality newsgroup
    • Submit a story to MozillaZine (this won't work on short notice)
    • Pass the word around on irc: #qa, #firefox, #developers, etc.
    • Update link to the Bug Day under Hot Events
    • Get prominent ad on QMO for when it goes live.
  • Misc.
    • When appropriate, invite developer(s) to participate
    • Adjust plan for regional interests if necessary


Topic Planner

  • 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
    • Public input tools: Attempt to map reports to bugs
      • Talkback
      • Reporter
      • Hendrix
      • Forums
  • Suggestions for future topics:
    • ???
    • ???
  • Schedule:
Date Topic
March 20 Hendrix mining
March 27 Map Hendrix items to bugs
April 3 tbd
April 10 tbd
April 17 tbd
April 24 tbd
May 1 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. I will be working on pulling topics out of the bug day wiki history to accurately complete that archive.

Needs

  • hosts for the Asian and Americas sessions
  • a simple to implement rewards program
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Community/Bug_Day/Planner&oldid=52309"