Thunderbird:QA TestDay:2008-04-03

From MozillaWiki
Jump to: navigation, search

last week | index | next week »

Bug Day April 3, 2008

Our second bug day is Thursday April 3, 2008 (extending into Friday morning April 4 for Asia), using the time schedule on the Bugdays page. If you are unable to join us on this date, please see the schedule of future bugdays.

Detailed bug day information, tips and schedule are available on the Bugdays page.


Suggested starting points for this bug day, listed below, are bugs with no activity for 150 days which are unconfirmed or crashers needing improved description or feedback from reporter. You may of course work on any open bugs that interest you - these Bug queries identify several classes and categories of bugs.


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: 2008-04-03 0530h PDT
    • End time: 2008-04-03 0830h PDT
  • Session 2
    • Start time: 2008-04-03 1130h PDT
    • End time: 2008-04-03 1430h PDT
  • Session 3
    • Start time: 2008-04-03 1730h PDT
    • End time: 2008-04-03 2030h PDT
  • 16 hour duration
    • All sessions & intermediate rest time.
    • Start time: 2008-04-03 0530h PDT
    • End time: 2008-04-03 2030h PDT
Bug Day results
Sessions Product Any Change Last bug day Only Resolution Change [2] Last bug day
Improvement Improvement
Session 1 Thunderbird-only Q 9 Q 9 down (-7) Q 2 Q 2 down (-9)
Core-only Q 0 Q 0
Session 2 Thunderbird-only Q 21 Q 24 up (+1) Q 5 Q 5 down (-4)
Core-only Q 3 Q 0
Session 3 Thunderbird-only Q 8 Q 10 down (-10) Q 0 Q 0 down (-9)
Core-only Q 2 Q 0
Session Total Thunderbird-only 38 43 down (-16) 7 7 down (-22)
Core-only 5 0
15 hour Duration Thunderbird-only Q 58 Q 74 down (-17) Q 15 Q 16 down (-22)
Core-only Q 16 Q 1

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


  • 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.


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.