Thunderbird:QA TestDay:2009-01-15

From MozillaWiki
Jump to: navigation, search

last week | index | next week »

Bug Day January 15, 2009

How to get help, how to get started, and schedule for Bugdays.

Bug days are conducted to reduce the number of UNCOnfirmed bugs in the bugzilla database, and to improve the quality of the bugs in the database.


Help shape Thunderbird 3. And help trunk testers in the process.

component=General bugs - If you touch one, please change component to something better (even if it's just a guess). Especially critical and major bugs.

Swat, squash, pound, massage, improve unconfirmed trunk bugs:

Other bugs that may interest you, from Bug queries or a variety from prior bugdays:


Before starting, see the Bugdays page for information about what to do and how to get help. Don't be concerned if you don't understand everything, just ask for help.


For this bugday, the times of the sessions, accounting for 30mins [1] of grace period before and after each session, were as follows:

  • Session 1
    • Start time: 2009-01-15 0530h PDT
    • End time: 2009-01-15 0830h PDT
  • Session 2
    • Start time: 2009-01-15 1130h PDT
    • End time: 2009-01-15 1430h PDT
  • Session 3
    • Start time: 2009-01-15 1830h PDT
    • End time: 2009-01-15 2230h PDT
  • 17 hour duration
    • All sessions & intermediate rest time.
    • Start time: 2009-01-15 0530h PDT
    • End time: 2009-01-15 2230h PDT
Bug Day results
Sessions Product Any Change Only Resolution Change [2]
Session 1 Thunderbird-only Q 22 Q 27 Q 13 Q 16
Core-only Q 5 Q 3
Session 2 Thunderbird-only Q 25 Q 32 Q 5 Q 5
Core-only Q 7 Q 0
Session 3 Thunderbird-only Q 15 Q 18 Q 4 Q 4
Core-only Q 3 Q 0
17 hour Duration Thunderbird-only Q 109 Q 134 Q 29 Q 34
Core-only Q 25 Q 5

Many thanks to volunteers and developers (total 5 - 10) who turned up for this bug day, and others that I may have possibly missed.


  • Spreadsheet of bugday results is compiled and updated after each session / bugday.
  • The letter Q stands for the query with all the appropriate criteria, which over time may differ from the results that have been logged.
  • [1] Session and period time includes 30mins before and after the official time period, so as to include early and late/spill over activity.
  • [2] A resolution change may be non-terminal, for example a bug may have been reopened.