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

QA/Community/Bug Day/Planner (view source)

Revision as of 04:08, 20 March 2007

1,270 bytes added , 20 March 2007

m

no edit summary

Twalker

Confirmed users

4,072

edits

@@ Line 2: / Line 2: @@
 ''Work in progress - watch for falling wikicode...''
-== '''How to prepare for Bug Day''' ==
+= Preparing for Bug Day =
-== 1. Announcements should be posted to the following areas: ==
+*Change the following items on the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day Bug Day wiki page] as appropriate:
-*(a) Mozilla QA blog
+** Topic of the day
-*(b) MozillaZine Firefox build Forum
+*** Move the old topic, if it's a unique topic, to the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day:Archive Bug Day Archive page]
-*(c) moz.dev.quality newsgroup
+*** Replace the old topic with the new topic
-*(d) Submit a story to MozillaZine (this won't work on short notice)
+*** Include links to bugzilla queries (tinyurls)
+** Moderators
+** Releases being targeted
+** Update links to the builds you want them to test (usually trunk)
+* Update this page with potential topics and schedule them
+* Advertising - Announcements should be posted to the following areas:
+** 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 [http://wiki.mozilla.org/Mozilla_QA_Community#Hot_Events Hot Events]
+== 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 future topics:
+** ???
+** ???
+*Schedule:
+{| border="1"
+|-
+! 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
+|}
-== 2. Update the topic for the new bug day. ==
+''note: don't forget to check the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day:Archive 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.
-Good topics for bug days allow for steady progress when tackled collaboratively.
-== 3. Change the following sections as appropriate: ==
-*(a) Topic of the day
-*(b) Who is moderating?
-*(c) Releases being targeted?
-*(d) Update links to the builds you want them to test (usually trunk)
-== 4.   Add a link to the Bug Day under Hot Events: ==
-* http://wiki.mozilla.org/Mozilla_QA_Community#Hot_Events