This Bug Day, we'll be focusing on unconfirmed bugs reported using Firefox 3.5. It's important to find any severe bugs that were missed during the release cycle. Any blocker, critical, or major bugs that are found could get fixed in the upcoming Firefox 3.5.1 or another maintenance release.

How do I get ready?

Meet us on #bugday for help and guidance. You can use this URL for a good search query to get started with.

This is what we're doing...

During this Bug Day, we will focus on narrowing down unconfirmed 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. Once we find them, we'll hand them off to developers to get them into a "point" update (e.g., Firefox 3.5.1).

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!