<< Back to Thunderbird QA

Welcome to Thunderbird Bugdays Planning!

Please participate in the planning and discussion of bugdays (see below) to improve Thunderbird Bug Days and other QA efforts. Our goal is to improve Thunderbird by helping the process that improves Thunderbird code by:

• developing a sense of fun, community and purpose
• encouraging triage activity
• developing and mentoring new triagers

Current Operations and Planning

• Discussion and planning:
  • mozilla.dev.apps.thunderbird
  • Weekly Status Meetings
  • Here (obviously)
• Announcements and publicity:
  • Several days prior to bugday in: #qtb-qa, #maildev, #seamonkey, #thunderbird, #tb-bugs, #calendar, forums.mozillazine.org (builds, bugs, support), mozilla.dev.apps.thunderbird, mozilla.dev.planning, mozilla.dev.apps.seamonkey, mozilla.dev.apps.calendar, mozilla.support.thunderbird, thunderbird-mail.de
  • Permanent or several weeks prior in: header of #bugday, Thunderbird:QA_Days, weekly on devnews calendar
  • Occassional: planet SUSE
• Time Schedule
• Results are posted or announced:
  • mozilla.dev.apps.thunderbird
  • in each Bug Day page and cumulative spreadsheet

Improving future Bug Days

Your ideas (or questions) do not need to be fully developed. Any idea can help generate further discussion. Put four tildas after your idea to stamp it with your name and date Our present efforts include developing the QA infrastructure (wiki) and reaching out to the established QA community, localizers. You can help in any of these areas.

• Ideas to improve bug days participation
  • reference item: The slow death of the press release
  • How can we increase participation from Asia, North and South America? (EU seems to be partly on board)
    • add <your idea> - <rationale for your idea>
  • Do community building PR surrounding a bug day that is a few weeks in the future and see if the story gets picked up. If it does, then you'll really get on people's radar outside of the usual mozilla venues. (ctalbert)
  • Always blog about the results, and always keep a spirit of fun in everything you do. It will always help to draw people. No one wants to work on something dull. :-) (ctalbert)
  • I have found (through some unscientific experimentation on calendar-qa) that two days notice in electronic forums is nearly perfect. If you do much more than that, the notice gets buried under newer messages, if you do it later, people don't see it. (Though I have sometimes had amazing success with day-before notifications). (ctalbert)
  • add <your idea> - <rationale for your idea>

• Ideas to improve bug days operation
  • add <your idea> - <rationale for your idea>

• Ideas for focus - i.e. groupings of bugs to work on
  • add <your idea> - <rationale for your idea>
  • send and sent errors --wsm 11:42, 19 April 2011 (PDT)
  • message retention --wsm 11:42, 19 April 2011 (PDT)
  • Reduction of Duplicates - Many unconfirmed (or even confirmed bugs) may have duplicates in the "Core" product under MailNews or elsewhere. For instance, there are 3 address book components, 2 are application specific (SM & TB), one is core, I think there are various bugs in the TB one that are duplicates in core --Standard8 01:19, 7 April 2008 (PDT)
    • dupeme in whiteboard (Thunderbird+Core, SM Address Book) 79 bugs --wsm 18:33, 27 May 2008 (PDT)
  • Reconfirming old bugs - How confident are we that all the "new" bugs in the database are still valid? Has someone changed the UI since, thus invalidating the bug, or has someone fixed the bug as a result of something else? There are ~2000 bugs classified as "new", are they really all [still valid] new? --Standard8 01:19, 7 April 2008 (PDT). // crude approximation 1958 bugs: created > 2007-04-01, untouched in 250 days, not version=2/gecko 1.9 --wsm 18:33, 27 May 2008 (PDT)
  • delete folder issues, a perhaps not so good query --wsm 12:48, 8 April 2008 (PDT)
  • Meta Tracking Bug dep triages - I'm thinking mostly of bug 71728 right now, but there are probably several tracking bugs who have incomplete dependency lists or dependencies tripping over each other. query of meta bugs Jcranmer 16:28, 22 May 2008 (PDT)
  • Critical bugs lacking qualifying keywords 225 bugs --wsm 18:33, 27 May 2008 (PDT)
  • dataloss keyword 96 bugs --wsm 11:16, 28 May 2008 (PDT)
  • bugs with mailxxx keywords, especially mailtrack --wsm 11:57, 28 May 2008 (PDT)
  • new mail/messages, over half are UNCO (49 bugs) --wsm 04:30, 2 June 2008 (PDT)
  • reporter probably gone (27 bugs) courtesy Nikolay Shopik --wsm 07:07, 8 June 2008 (PDT)
  • install (88 bugs) --wsm 12:11, 4 July 2008 (PDT)
  • zug is a triager who makes great comments in many bugs - but someone with privileges is needed to make status/resolution changes.
    • zug UNCO bugs (26 bugs)
    • zug UNCO +enh (136 bugs)
  • unsent/send later/outbox (54 bugs, including Seamonkey) --wsm 14:45, 9 January 2009 (UTC)
  • attachment corruption (14 bugs) --wsm 12:30, 26 May 2009 (UTC)
  • grouping in message list pane --wsm 04:47, 26 September 2011 (PDT)

• References
  • Thunderbird and mailnews bug queries
  • Getting to know the Mozilla QA Community! - The Results
  • Time Zones

Past

• Publicity
  • Standard8’s Blog (Mark Banner)
  • david ascher's blog
  • April's issue of About:mozilla newsletter

• Bugdays History / Changes
  • Thunderbird:QA_TestDay:2008-04-10 - Session 3 04-03 had no activity. Session 3 for 04-10 will change to a 3-hour slot (instead of 2 hours) and delay start time +1hr to a) give PTD better later coverage, b) still cover all of Americas, c) give Asia better morning coverage. Session 1 and 2 did well.
  • Thunderbird:QA_TestDay:2008-04-03 - Session 1 (Asia) lightly attended, and we lacked an evening session for Americas, so we moved Session 1 by ~16 hours to better cover Americas. Removed regional designations so that potential participants don't get a "message" that any sessions (not of their geography) should be avoided.
  • Thunderbird:QA_TestDay:2008-03-27 - Adopted QMO's schedule of three, 2-hour sessions