Thunderbird:Bugdays

<< Back to Thunderbird Testing

Welcome to the Thunderbird Bug Day wiki!

Join us on IRC in #bugday at your regional time to discuss and work on bugs and get help from the Thunderbird / Mozilla Messaging team. Bug Days are an excellent way to contribute to QA efforts. It doesn't matter if you've been involved with Mozilla for years or if this is your first step into our amazing open source community. Anyone can participate and be a valuable contributor.

Schedule

Bug days are arranged into three sessions so as to be convenient for participants around the world. The three sessions target Asia/Australia, Europe/Africa, and North/South America. Of course, anyone may attend any or all sessions as they wish. Some assistance may hang around between or after sessions, so you may find someone in #bugday to help you outside of the scheduled times.

Timezone / Session	E. Asia/Australia session	Europe/Africa session	Americas session
Los Angeles, USA (PDT=UTC-8 +1)	Wed 21:00-23:00	Thu 04:00-06:00	*Thu 12:00-14:00
UTC	Thu 06:00-08:00	Thu 13:00-15:00	Thu 19:00-21:00
UK (BST=UTC)	Thu 06:00-08:00	Thu 13:00-15:00	Thu 19:00-21:00
Berlin, Germany (CEST=UTC+1)	Thu 07:00-09:00	*Thu 14:00-16:00	Thu 20:00-22:00
Moscow, Russia (UTC+3)	Thu 9:00-11:00	Thu 16:00-18:00	Thu 22:00-00:00
Beijing, China (UTC+8)	*Thu 14:00-16:00	Thu 21:00-23:00	Fri 04:00-06:00

Simplified schedule:

Asia session - 14:00-16:00 UTC/GMT +8 hours (Beijing) (06:00-08:00 UTC)
Euro session - 14:00-16:00 UTC/GMT +1 hours (Berlin) (13:00-15:00 UTC)
Amer. session - 12:00-14:00 UTC/GMT -8 hours (Los Angeles) (19:00-21:00 UTC)

Please use The World Clock to determine when a session is happening in your time zone.

FAQ - How to I do this?

What you want to do is pretty simple:

• Replicate the problem specified in the bug report and mark as "confirmed" if you are able to replicate and the steps to reproduce are documented and clear and the problem does not exist in trunk builds.
• Clarify bug reports without distorting or changing the original problem.
• Change the summary to be more accurate of the problem being reported, and if appropriate remove words so summary is less wordy
• Close bug reports as WORKSFORME, INVALID, or INCOMPLETE when it's appropriate to do so.
• Ask reporters to provide missing information that will help to replicate and ultimately fix the bugs they report.

Please check the following documentation for more about this process:

• Bug triage
• Read Bug Writing Guidelines to learn what is an effective bug report that will lead to bug fixes

You will want to test with Nightly Trunk Builds. Ask for help if you do not know how to set it up. Or, if you are not permitted to use trunk, then use the latest update of Thunderbird version 2 - currently 2.0.0.12.

If you don't have the necessary rights to change to a bug see the Bug triage page about how to get privileges, then add a comment to the bug detailing what should be changed and why. You can also make this known in the #bugday channel and someone will assist you.