Thunderbird:QA TestDay:2008-05-01

From MozillaWiki
Jump to: navigation, search

last week | index | next week »

Bug Day May 1, 2008

Time schedule for Thursday bugday (into Friday morning for Asia) is on the Bugdays page, which also tells you how to get started and how to get help.

Bug days are done to reduce the number of unconfirmed bugs in the bugzilla database, and a more general sense seeks to improve the quality of the bugs in the database.


"Focus" for this bug day - suggested starting points - is listed below. You may of course work on any bugs that interest you. Bug queries identifies categories you might consider.

quick pick variety pack - leftovers from prior bugdays

(1) Move from General to another component if possible, in addition to other actions and comments.


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: 2008-05-01 0530h PDT
    • End time: 2008-05-01 0830h PDT
  • Session 2
    • Start time: 2008-05-01 1130h PDT
    • End time: 2008-05-01 1430h PDT
  • Session 3
    • Start time: 2008-05-01 1830h PDT
    • End time: 2008-05-01 2230h PDT
  • 17 hour duration
    • All sessions & intermediate rest time.
    • Start time: 2008-05-01 0530h PDT
    • End time: 2008-05-01 2230h 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 28 Q 38 up (+9) Q 9 Q 9 up (+4)
Core-only Q 10 Q 0
Session 2 Thunderbird-only Q 45 Q 49 up (+29) Q 13 Q 13 up (+11)
Core-only Q 4 Q 0
Session 3 Thunderbird-only Q 16 Q 20 down (-8) Q 3 Q 4 down (-4)
Core-only Q 4 Q 1
Session Total Thunderbird-only 89 107 up (+30) 25 26 up (+11)
Core-only 18 1
17 hour Duration Thunderbird-only Q 109 Q 151 up (+56) Q 34 Q 39 up (+21)
Core-only Q 42 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.


  • An updated spreadsheet of the previous bugdays' 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.