Thunderbird:Bugdays: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<small>[[Thunderbird: | <small>[[Thunderbird:Testing|<< Back to Thunderbird Testing]]</small> | ||
= Welcome to the Thunderbird Bug Day wiki! = | = 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 / | Join us on IRC in #bugday at your regional time to discuss and work on bugs and get help from the Thunderbird / [http://www.mozillamessaging.com 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. | ||
= Bug Day March 27, 2008 = | = Bug Day March 27, 2008 = | ||
| Line 11: | Line 11: | ||
See the FAQ below before starting about what to do. Don't be concerned if you don't understand everything, just ask for help. | See the FAQ below before starting about what to do. Don't be concerned if you don't understand everything, just ask for help. | ||
The focus of our first bug day is bugs with status unconfirmed. But you may certainly work on any open bugs that interest you. [[Thunderbird:Bug_Queries|Bug queries]] identifies several classes and categories of bugs, with some ratings of what areas are in most need of attention. | The focus of our first bug day is bugs with status unconfirmed, emphasizing on bugs created pre-Thunderbird 2 release. But you may certainly work on any open bugs that interest you. The page [[Thunderbird:Bug_Queries|Bug queries]] identifies several classes and categories of bugs, with some ratings of what areas are in most need of attention. | ||
= Schedule = | = Schedule = | ||
| Line 55: | Line 55: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th> Beijing, China (UTC+8 | <th> Beijing, China (UTC+8) </th> | ||
<td bgcolor="#ddddff">*Thu 14:00-16:00 </td> | <td bgcolor="#ddddff">*Thu 14:00-16:00 </td> | ||
<td>Thu 21:00-23:00 </td> | <td>Thu 21:00-23:00 </td> | ||
| Line 68: | Line 68: | ||
'''Amer. session - 12:00-14:00 UTC/GMT -8 hours (Los Angeles) (19:00-21:00 UTC)''' | '''Amer. session - 12:00-14:00 UTC/GMT -8 hours (Los Angeles) (19:00-21:00 UTC)''' | ||
Please use | Please use [http://www.timeanddate.com/worldclock/ The World Clock] to help determine when a session is happening in your time zone. | ||
= FAQ - How to I do this? = | = FAQ - How to I do this? = | ||
| Line 78: | Line 78: | ||
* Ask reporters to provide missing information that will help to replicate and ultimately fix the bugs they report. | * Ask reporters to provide missing information that will help to replicate and ultimately fix the bugs they report. | ||
You will want to test with | You will want to test with [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ Nightly Trunk Builds]. If you do not know how, ask for help on how to set it up. Or, 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. | ||
Note: If you don't have the necessary rights to make a change to a bug see the [[Thunderbird:Bug_Triage|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. | Note: If you don't have the necessary rights to make a change to a bug see the [[Thunderbird:Bug_Triage|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. | ||
| Line 86: | Line 86: | ||
** Mozilla QA linked to from the "For Testers" section of mozilla.org/developer | ** Mozilla QA linked to from the "For Testers" section of mozilla.org/developer | ||
** A good document on how to find existing bugs | ** A good document on how to find existing bugs | ||
** Read | ** 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. | ||
[[category:Thunderbird|*]] | [[category:Thunderbird|*]] | ||
Revision as of 05:31, 24 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.
Bug Day March 27, 2008
Our first bug day is March 27, 2008 according to the schedule below. Please be patient if we have to work any "bugs" out of our first bugday.
See the FAQ below before starting about what to do. Don't be concerned if you don't understand everything, just ask for help.
The focus of our first bug day is bugs with status unconfirmed, emphasizing on bugs created pre-Thunderbird 2 release. But you may certainly work on any open bugs that interest you. The page Bug queries identifies several classes and categories of bugs, with some ratings of what areas are in most need of attention.
Schedule
Bug days are arranged into three sessions so as to be convenient for participants around the world. The three sessions target for those in Asia/Australia, Europe/Africa, and North/South America. Of course, anyone may attend any or all sessions as they wish. Some help 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 |
A bit simpler 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 help determine when a session is happening in your time zone.
FAQ - How to I do this?
What we want to accomplish 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 the problems.
- Close bug reports as WORKSFORME or INVALID 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.
You will want to test with Nightly Trunk Builds. If you do not know how, ask for help on 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.
Note: If you don't have the necessary rights to make a 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.
- Please check the following documentation
- Bug triage process.
- Mozilla QA linked to from the "For Testers" section of mozilla.org/developer
- A good document on how to find existing bugs
- Read Bug Writing Guidelines to learn what is an effective bug report that will lead to bug fixes.