QA/Community/Bug Day: Difference between revisions
| Line 9: | Line 9: | ||
= Topic of the Day = | = Topic of the Day = | ||
== | == Thunderbird 2 unconfirmed triage == | ||
Thunderbird are Go! Since we released Thunderbird 2 we have a lot of new unconfirmed bug reports. We will take a look at this Bugs | Thunderbird are Go! Since we released Thunderbird 2 we have a lot of new unconfirmed bug reports. We will take a look at this Bugs | ||
Revision as of 20:48, 23 April 2007
« back to Mozilla_QA_Community
Welcome to the Mozilla QA Community Bug Day wiki!!
Note - New bugday times throughout the world. See the new schedule below. After discussion with several community members, we decided to move bugday times a bit earlier for each region. This change is an attempt to increase bugday participation by having regional session in the afternoon when people are at work or on university campus rather than in the evening when most people aren't willing or able to volunteer their time.
Join us on IRC in #bugday every Tuesday for your regional time to discuss and work on Bugzilla bug topics and get help from the Mozilla QA team.
Bug Days are an excellent way to contribute to Mozilla's 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. We gather together at predetermined times to focus on particular areas in Bugzilla. The exact area or topic for Bug Day may vary week to week. But the general idea is to work through some sort of bug list as a team.
Topic of the Day
Thunderbird 2 unconfirmed triage
Thunderbird are Go! Since we released Thunderbird 2 we have a lot of new unconfirmed bug reports. We will take a look at this Bugs
We'll be actively pinging anyone in the channel to take a couple bugs. So if you're there be prepared to do a little bugzilla work. :-)
Triage work of this [1]
Please use the Thunderbird 2 Release to test with.
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 session as they wish.
I've replaced the table, but it still needs some polishing and adding to (particulary, the colors may have to go) -- Aleksej
| Timezone / Session | E. Asia/Australia session | Europe/Africa session | Americas session |
| Los Angeles, USA (PST=UTC-8+DST) | Mon 23:00-01:00 | Tue 05:00-07:00 | *Tue 12:00-14:00 |
|---|---|---|---|
| UTC | Tue 06:00-08:00 | Tue 12:00-14:00 | Tue 19:00-21:00 |
| UK (BST=UTC+DST) | Tue 07:00-09:00 | Tue 13:00-15:00 | Tue 20:00-22:00 |
| Berlin, Germany (CEST=UTC+1+DST) | Tue 08:00-10:00 | *Tue 14:00-16:00 | Tue 21:00-23:00 |
| Moscow, Russia (UTC+3+DST) | Tue 10:00-12:00 | Tue 16:00-18:00 | Tue 23:00-01:00 |
| Beiging, China (UTC+8, DST n/a) | *Tue 14:00-16:00 | Tue 20:00-22:00 | Wed 03:00-05: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 +2 hours (Berlin) (12:00-14:00 UTC)
Amer. session - 12:00-14:00 UTC/GMT -7 hours (Los Angeles) (19:00-21:00 UTC)
Please use that and the tools at The World Clock to help determine when a session is happening for you.
Some of us hang around between or after sessions, so you may find someone in #bugday outside of this time, and if not, you can always find people in #qa.
Community Representatives
Bug days are led by Mozilla's QA staff and by experienced volunteers from our community.
- Asia - Tracy (future - Emily?)
- Euro - Tomcat
- Americas - Tracy (future - Triona?)
Staying Connected
- Click here to join the mailing list.
- Hang out in #qa when we're not scheduled in #bugday or #testday
- Keep an eye on this page. Weekly updates will be posted by Thursday afternoon (California time)
- Read the Mozilla QA blog
FAQ
Where do I start? While the topic of day may have a particular focus for the session, we usually want to try to do the following:
- Replicate the problems specified in bug reports and mark them as "confirmed" whenever we are able to do so.
- Clarify bug reports whenever we can do so 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 would help to replicate and ultimately fix the bugs they report.
Note: If you don't have the necessary rights to make a change to a bug, add a comment to the bug detailing what should be changed and why. You can also make this known in the #bugday channel, and one of the moderators or an experienced volunteer will assist you.
- The following documentation is good to become familiar with for anyone working on Mozilla projects:
- 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 how to write effective bug reports that lead to bug fixes.
- Review the documentation specific to the topic of the day.
- Join the #bugday channel
- Go to your favorite IRC client
- Connect to irc.mozilla.org and "/join #bugday"
- Then, just ask the moderators how you can help for the topic of the day.
What build should I be testing with?
- Get the latest Firefox Trunk builds, the next version of Firefox in development.
Bug Day History
Bug Day Planning For contributors planning and hosting Bug Days please see the Bug Day Plannner