Bugmasters/Projects/Beta

From MozillaWiki
Jump to navigation Jump to search
Currently the Beta release!

Firefox 146 bug triage team

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

Every night the latest pre-release version of Firefox is made available as the Nightly release. After 6 weeks of further development that branch becomes the Aurora release, and is more stable than the nightly; 6 weeks later it becomes the Beta release. If you want to test against the Firefox 146 release of Firefox, download the Firefox 146 build and use it as your main browser. 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. Triaging the Firefox 146 bugs will help us catch important bugs at the last minute, and you have a relatively stable development browser to use!

1. Download the Firefox 146 build and run it.
2. Make a bugzilla account.
3. Skim over the current bugs against the Firefox 146 release (currently, the 146 branch).
4. File bugs when you find them...
5. Triage through the list of untriaged Firefox 146 bugs. So helpful!
--- replicate, comment, confirm
--- needinfo the bug reporter to get more details
--- regression testing


UNCONFIRMED bugs in the 146 Branch


No results.

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


Note: 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 146 Branch that were confirmed

Firefox Untriaged bugs in 146 Branch

Bugs that are in the Firefox Untriaged component, reported for 146 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%);