Closed
Bug 955952
Opened 10 years ago
Closed 10 years ago
[meta] FxA on FxOS: Gaia blockers
Categories
(Core Graveyard :: Identity, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
1.4 S4 (28mar)
People
(Reporter: spenrose, Unassigned)
References
Details
(Keywords: meta)
A parent for arbitrary open Gaia issues that prevent the overall FxA work from being beta quality.
Reporter | ||
Comment 1•10 years ago
|
||
Splitting the ambiguous "beta" into "blockers" (this bug) and a new bug for "nice to haves". From https://wiki.mozilla.org/B2G/Triage#Triage_for_1.3.0 (h/t Adam Rogers): Issues that Should Block Major issue in new feature - especially those in which a large number of users will be impacted, or a smaller number of users will be significantly impacted Major identifiable regressions (perf or otherwise) Non-localizable strings Top Crashes sec-high, sec-critical security bugs Smoke-test regression Data loss Issues that block partner certification (bluetooth, wifi, legal, etc.) Issues getting a lot of support calls with partners or on SUMO Issues critical around updates (especially if there's been a repro) Anything critical around the first time experience Major Dialer, SMS, and VM communication issues Issues that prevent automated tests in established testsuites (visible test suites on b2g integration branches on TBPL) from running green at least 90% of the time. Certification waivers from the previous release (new policy) Major issue with an embedded 3rd party app (in case it can't be solved, it could be decided to remove the app)
Summary: [meta] FxA on FxOS: Gaia work is beta quality → [meta] FxA on FxOS: Gaia blockers
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Target Milestone: --- → 1.4 S4 (28mar)
Updated•5 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•