QA/Community/Bug Day: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
mNo edit summary
Line 1: Line 1:
= Welcome to the Mozilla QA Community Bug Day wiki!! =   
= Welcome to the Mozilla QA Community Bug Day wiki!! =   


For those of you unfamiliar with Bug Days; 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 work on areas in Bugzilla. The exact are 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.
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 work on 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: More Firefox 2.0 bug verification =
== Community Representatives ==
We'd like to start recruiting a few individuals from the community to take under our wings and give a larger role in community QA projects like Bug Days and Test Days.


'''Tuesday, Aug 22, 2006'''  
== Staying Connected ==
* Verify More Firefox 2.0 regression bugs
* Click [http://mail.mozilla.org/listinfo/communityqateam here] to join the mailing list.
** We'll be working this * [http://tinyurl.com/mm5bh Unverified fixed1.8.1 regression] bug list.
* Hang out in #qa when we're not scheduled in #bugday or #testday
* next week (Sept. 5th): Back to Basics
* Keep an eye on this page. Weekly updates will be posted by Thursday afternoon (California time)
* Read the [http://weblogs.mozillazine.org/qa/ Mozilla QA blog]
 
= Schedule '''<-- New! Check this out.''' =
In an effort to make Bug Days more accessible to interested folks around the globe, I've decided to split up Bug Day into three 2 hour sessions. Below is the schedule we'll use to catch East Asia, Europe and the USA in "prime time."
 
*East Asia session: 8pm-10pm in Tokyo, Japan gmt+9
*Europe session: 8pm-10pm in Paris, France gmt+2           
*USA session: 6pm-8pm in San Francisco, CA. gmt-7, 9pm-11pm in N.Y., NY. gmt-4               
 
= Topic of the Day =
 
'''Tuesday, Sept. 12, 2006'''  
* Firefox 2.0 unconfirmed bug triage
** We'll looking at this [http://tinyurl.com/maq9o bug list] of Firefox 2.0 General Unconfirmed bugs.
** If that list becomes empty, we'll use this broader [http://tinyurl.com/p7hoz bug list] of all Firefox 2.0 Unconfirmed bugs.


= Review of last week =
= Review of last week =
I was basically the only one working bug dayI verified 16 2.0 regression bugs.
Discussed with a few visitors ideas for improving Bug Day participationThe biggest concern seemed to be the event time not being convenient for most.


= FAQ =
= FAQ =
Line 21: Line 37:
** Read [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] to learn how to write effective bug reports that lead to bug fixes.
** Read [http://www.mozilla.org/quality/bug-writing-guidelines.html 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.
* Review the documentation specific to the topic of the day.
* Join the #qa channel
* Join the '''#bugday''' channel <-- '''Changed channel'''
** Go to your favorite IRC client  
** Go to your favorite IRC client  
*** [http://www.ircreviews.org/clients/platforms-windows.html Windows clients]
*** [http://www.ircreviews.org/clients/platforms-windows.html Windows clients]

Revision as of 19:12, 7 September 2006

Welcome to the Mozilla QA Community Bug Day wiki!!

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 work on 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.

Community Representatives

We'd like to start recruiting a few individuals from the community to take under our wings and give a larger role in community QA projects like Bug Days and Test Days.

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

Schedule <-- New! Check this out.

In an effort to make Bug Days more accessible to interested folks around the globe, I've decided to split up Bug Day into three 2 hour sessions. Below is the schedule we'll use to catch East Asia, Europe and the USA in "prime time."

  • East Asia session: 8pm-10pm in Tokyo, Japan gmt+9
  • Europe session: 8pm-10pm in Paris, France gmt+2
  • USA session: 6pm-8pm in San Francisco, CA. gmt-7, 9pm-11pm in N.Y., NY. gmt-4

Topic of the Day

Tuesday, Sept. 12, 2006

  • Firefox 2.0 unconfirmed bug triage
    • We'll looking at this bug list of Firefox 2.0 General Unconfirmed bugs.
    • If that list becomes empty, we'll use this broader bug list of all Firefox 2.0 Unconfirmed bugs.

Review of last week

Discussed with a few visitors ideas for improving Bug Day participation. The biggest concern seemed to be the event time not being convenient for most.

FAQ

Where do I start?

  • The following documentation is good to become familiar with for anyone working on Mozilla projects:
  • Review the documentation specific to the topic of the day.
  • Join the #bugday channel <-- Changed channel

What build should I be testing with?

Past Bug Day Archives here