Bugmasters/Projects/Release

FF 132 bug triage team

This is the current release of Firefox

Hello! If you'd like to help out with bug management for Firefox 132, please email bugmaster@mozilla.com!

If you find any bugs, file them. (How to File a Bug).

You may also be interested in looking at the bugs others have filed, and see if you can replicate them or add any useful information.

1. Make sure you're using Firefox 132. Check by going to :about in the location bar.

2. Make a bugzilla.mozilla.org account.

3. Skim over the UNCONFIRMED bugs against the current release

4. File bugs when you find them ...

5. Triage through the list of 132 untriaged  bugs. So helpful!

--- replicate, comment, confirm

--- needinfo the bug reporter to get more details

--- regression testing

UNCONFIRMED bugs in the 132 Branch

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Note: I would love to figure out how to make a mediawiki-bugzilla chart here to show bugs that have changed state from UNCO to NEW. Or since that may not be super useful, this might be better done in a dashboard; it would be good to know the number of bugs that changed state in this way.

• Number of bugs reported for 132 Branch that were confirmed

Firefox Untriaged bugs in 132 Branch

Bugs that are in the Firefox Untriaged component, reported for 28 branch.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

The following bugs have been replicated, or confirmed as NEW, but haven't yet been assigned to a product and component. It's important to make an effort to get these bugs into a category where developers on particular teams are more likely to see them.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);