BETA (131)

This is a draft, please help check and correct these queries - lizzard

Queries

When release management tracks a bug in Beta we are committed to follow through on it until it is resolved. Our goal is to land fixes in time to test them before the beta version of Firefox moves to the release channel. It's especially important to track regressions, topcrashes, critical and high priority security fixes, issues that will impact many users, and issues that affect new or highlighted features.

• tracked for 131]
  • Resolved/Fixed
  • Regressions, all security, no resolved
  • Earlier regressions, non-security, no resolved

Tracked bugs

It's often useful to sort these by the last changed date, and go through the oldest first.

46 Total; 6 Open (13.04%); 23 Resolved (50%); 17 Verified (36.96%);

Tracking nominations

Bugs nominated (by anyone) for tracking. These need frequent triage. It's good to mark which versions are affected and unaffected. If you can't easily tell from the comments, ask for QA help.

Tracking nominations: https://bugzilla.mozilla.org/buglist.cgi?o1=equals&v1=%3F&known_name=tracking-ff32%3F&f1=cf_tracking_firefox37&query_based_on=tracking-ff32%3F&query_format=advanced&list_id=12011632 (current query)

No results.

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

Security tracking noms