Criteria for deciding whether a bug should be fixed

• Very high volume crash or browser not working
• Security-critical issues
• High volume startup crashes
• Privacy and data loss problems
• Feature or basic functionality issues which affect many users
• Memory leaks, battery life
• Test automation is working and meaningful
• Bugs affecting upcoming Android releases (Specifically Q)

Bugs that meet one more more of these criteria should be marked as a P1. If a bug does not meet these criteria it should either be closed or be marked as a P5.

New bugs to be triaged

Product and Engineering Management will triage new bugs (bugs with no priority filed after 2019-07-01). If management decides a bug looks important enough to fix in Fennec ESR 68, they will set the bug priority to P1.

If a bug is something that QA that can't reproduce locally, such as a mysterious top crash or a new feature to be added, management can skip the QA confirmation step and send the bug directly to engineering by setting firefox-esr68 status flag to affected.

Unprioritized bugs in the Firefox for Android product:

No results.

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

Unprioritized bugs with a Fennec whiteboard tag:

No results.

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

Triaged bugs to be confirmed by QA

QA will confirm whether the following high priority bugs are reproducible. If a bug is reproducible, QA will set the firefox-esr68 status flag to affected. If the bug is not reproducible, QA will set the firefox-esr68 status flag to unaffected and then, at their discretion, needinfo the bug reporter for more information or resolve the bug as "RESOLVED INVALID".

Triaged bugs in the Firefox for Android product that have not been confirmed by QA:

No results.

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

Triaged bugs with a Fennec whiteboard tag that have not been confirmed by QA:

No results.

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

Confirmed bugs to be fixed

These are bugs that management would like fixed in Fennec ESR 68 and QA has confirmed are reproducible (or at least worth more investigation, such as a top crash that can't easily be reproduced).

Confirmed P1 bugs in the Firefox for Android product:

No results.

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

Confirmed P1 bugs with a Fennec whiteboard tag:

No results.

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

Fixed bugs to be verified by QA

These are bugs that have been fixed in mozilla-central, but not verified by QA or uplift to Fennec ESR 68 yet.

Bugs in the Firefox for Android product that have been fixed in mozilla-central but not ESR 68:

No results.

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

Bugs with a Fennec whiteboard tag that have been fixed in mozilla-central but not ESR 68:

No results.

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

Verified bugs to be uplifted to ESR 68

These are bugs that have been verified by QA in mozilla-central, but not uplifted to Fennec ESR 68 yet.

Bugs in the Firefox for Android product that have been QA verified in mozilla-central but not uplifted ESR 68:

No results.

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

Bugs with a Fennec whiteboard tag that have been QA verified in mozilla-central but not uplifted to ESR 68:

No results.

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

Links

• Fennec 68 top crashes
• Fennec bugs that affect 68 (We should check whether these bugs also affect Fenix.)