Thunderbird:Bugdays: Difference between revisions
(remove specific 27 Mar 08 bug day info) |
|||
| Line 65: | Line 65: | ||
What you want to do is pretty simple: | 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. | * 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. If you are not running trunk but can replicate the bug, please comment but do not confirm. | ||
* Clarify bug reports without distorting or changing the original problem. | * Clarify bug reports without distorting or changing the original problem. | ||
* Change the summary to be more accurate | * Change the summary to be more accurate to the problem being reported, and if appropriate remove words so summary is less chatty | ||
* Close bug reports as [https://bugzilla.mozilla.org/page.cgi?id=fields.html#status WORKSFORME, INVALID, or INCOMPLETE] when it's appropriate to do so. | * Close bug reports as [https://bugzilla.mozilla.org/page.cgi?id=fields.html#status WORKSFORME, INVALID, or INCOMPLETE] when it's appropriate to do so. | ||
* Ask | * Ask bug reporter in a bug comment to provide missing information that will help to replicate and ultimately fix the bugs they report. | ||
* Always cite what version you are using. | |||
Please check the following documentation for more about this process: | Please check the following documentation for more about this process: | ||
| Line 75: | Line 76: | ||
* Read [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] to learn what is an effective bug report that will lead to bug fixes | * Read [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] to learn what is an effective bug report that will lead to bug fixes | ||
If you can, please test with [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ Nightly Trunk Builds]. If you are not permitted to use trunk, then use the [http://www.getthunderbird.com/ latest update of Thunderbird version 2] - currently 2.0.0.12. You can install a trunk build or any release of Thunderbird, and not disturb your production setup by a) using '''custom install''' to specify a directory of your choosing, and b) using [http://kb.mozillazine.org/Starting_Firefox_or_Thunderbird_with_a_specified_profile profile manager] to create a test profile. | |||
If you don't have the necessary rights to change to a bug see | If you don't have the necessary rights to change to a bug see [[Thunderbird:Bug_Triage|Bug triage]] about how to get privileges. Then add a comment to the bug detailing what should be changed and why. You can also make your comments known in the #bugday channel and someone will assist you. | ||
[[category:Thunderbird|*]] | [[category:Thunderbird|*]] | ||
Revision as of 20:22, 25 March 2008
<< 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. If you are not running trunk but can replicate the bug, please comment but do not confirm.
- Clarify bug reports without distorting or changing the original problem.
- Change the summary to be more accurate to the problem being reported, and if appropriate remove words so summary is less chatty
- Close bug reports as WORKSFORME, INVALID, or INCOMPLETE when it's appropriate to do so.
- Ask bug reporter in a bug comment to provide missing information that will help to replicate and ultimately fix the bugs they report.
- Always cite what version you are using.
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
If you can, please test with Nightly Trunk Builds. If you are not permitted to use trunk, then use the latest update of Thunderbird version 2 - currently 2.0.0.12. You can install a trunk build or any release of Thunderbird, and not disturb your production setup by a) using custom install to specify a directory of your choosing, and b) using profile manager to create a test profile.
If you don't have the necessary rights to change to a bug see Bug triage about how to get privileges. Then add a comment to the bug detailing what should be changed and why. You can also make your comments known in the #bugday channel and someone will assist you.