Thunderbird:QA TestDay:2009-05-14

From MozillaWiki
Jump to: navigation, search

last testday | index | next testday »

Bug Day May 14, 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 who help us by reporting bugs.

  • Ubuntu users please read the following to get the lastest version of Thunderbird 3.0beta
  • openSUSE users can go here to find TB3 nightly for their distribution version or here for a "one click" install.
  • Fedora users can get the latest Thunderbird preview by enabling the test updates repository:
    • Via the GUI
      • System > Administration > Software Sources
      • Enable the "Test Updates" repository
      • System > Administration > Software Update and find the latest Thunderbird
    • Via yum command line:
      • yum --enablerepo=updates-testing update thunderbird
    • Manual download for F9 F10 F11
  • Other distribution user can find a linux build here

This week is a very special week as the Testday is on my Birthday !!! To celebrate that and the fact that it's openSUSE's community week we would like to focus this week's bugday to bugs that are happening on Linux.

Bugs to work on (queries):

  • Linux Trunk UNCO bugs affecting MailNewsCore and Thunderbird - these bugs need more information , or confirmation from another user that they are happening.
  • Linux UNCO bugs. These bugs are covering all versions of TB - some might not be happening again - knowing that would be great.
  • Seamonkey users - the following bug list affects both seamonkey and thunderbird.
    • Linux UNCO SM and TB those bugs affect both Seamonkey and Thunderbird - any help on those bug will make both product better.


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.

Searching in bugzilla can be tricky - here are a few tricks that might 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-05-14 0530h PDT
    • End time: 2009-05-14 0830h PDT
  • Session 2
    • Start time: 2009-05-14 1130h PDT
    • End time: 2009-05-14 1430h PDT
  • Session 3
    • Start time: 2009-05-14 1830h PDT
    • End time: 2009-05-14 2230h PDT
  • 17 hour duration
    • All sessions & intermediate rest time.
    • Start time: 2009-05-14 0530h PDT
    • End time: 2009-05-14 2230h PDT
Bug Day results
Sessions Product Any Change Only Resolution Change [2]
Session 1 Thunderbird-only Q 16 Q 27 Q 5 Q 7
Core-only Q 11 Q 2
Session 2 Thunderbird-only Q 29 Q 42 Q 7 Q 10
Core-only Q 13 Q 3
Session 3 Thunderbird-only Q 6 Q 9 Q 1 Q 1
Core-only Q 3 Q 0
17 hour Duration Thunderbird-only Q 83 Q 118 Q 22 Q 27
Core-only Q 35 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.