Coordinate with QA team about included infrastructure changes
Categories
(Firefox for Android :: Search, task, P2)
Tracking
()
People
(Reporter: jmahon, Assigned: skhan)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid])
Please reach out to rpapa & his team to make sure they have what they need to be able to test these changes effectively.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
The Android team has not been keeping our P1 bug list up to date, so we're resetting all our P1 bugs to P2 to avoid signalling that we're actively working on bugs that we're not. The BMO documentation https://wiki.mozilla.org/BMO/UserGuide/BugFields#priority says P1 means "fix in the current release cycle" and P2 means "fix in the next release cycle or the following (nightly + 1 or nightly + 2)".
If you are actively working on this bug and expect to ship it in Fx 122 or 123, then please restore the priority back to P1.
Coordinated with QA team and here is the jira with the test cases and test plan we came up with
https://mozilla-hub.atlassian.net/browse/QA-3905
Description
•