Please join us for this presentation by Scott Tilley from the Florida Institute of Technology.

This is what we're doing...

MV MoCo people: It will be in the presentation area of 10 Forward.
Others can use the conference call #:

• Dial 1-800-707-2533 (password 369) or 1-650-215-1282 (extension 92#)
• Then dial Conference number 8600#

Or view via AirMozilla (http://air.mozilla.com/) streaming video.

Quality metrics is an important part of the overall testing process.

There are a number of coverage tools and challenges such as the types of coverage, how to interpret the numbers as well as how we plan to use the information. This presentation will focus on some of these aspects. Please see http://quality.mozilla.org/projects/quality-metrics for a more detailed explanation of the code coverage project.  Feel free to join the project if you are interested!

We will start with pizza and mingling at 6:30 PM - the presentation will start promptly at 7 PM.

How do I get ready?

http://quality.mozilla.org/projects/quality-metrics

This is what we're doing...

Date and Time:
Wednesday, August 19, 2009
6:30 PM Start Time - Pizza and mingling
7:00 PM Presentation begins
Location:
650 Castro Street, Suite 300
Mountain View, CA 94041
IMPORTANT NOTE: The lobby doors of 650 Castro Street lock at 7 PM, so if you arrive after that time you will have to call 650-903-0800 x 214 to let us know what you are outside.  Thanks.
The presentation slides can be found here:
http://people.mozilla.com/~timr/CodeCoverage/Codecoverage-preso-Aug19-20...

Stay Connected and Do More!

.

During this Bug Day, we will focus on narrowing down unconfirmed cash bugs to find any important ones that have been reported, looking especially for regressions in Firefox 3.5 that weren't in Firefox 3.0.x. Once we find them they can be assigned to developers to be fixed in a security and stability release (e.g., Firefox 3.5.1).

See also http://blog.mozilla.com/security/2009/07/20/how-mozilla-finds-crash-bugs/ for more Information

Triage, what is it?

Well, simply put, triage is taking a bug, making sure it has enough information to reproduce, and ensuring that it is in the proper component. After that, you should try to reproduce the issue. Problems that are easily reproducible (such as a crash that occurs every time you visit a certain website), are more valuable than those that are impossible to reproduce. If you can reproduce a bug, please add a comment to the bug or recommend in #bugday that the bug be confirmed.
For more information on triage, please check out the Bug Triage Guidelines and Project.
Help make Firefox 3.5 even better!

Thanks !

- Tomcat

http://www.communityleadershipsummit.com/schedule/ has all the details regarding this event. While not a Mozilla-run event, there will be several Mozillians in attendance and there should be some interesting sessions.

This is what we're doing...

http://www.communityleadershipsummit.com/schedule/