Hi all, There has been much wonderful enthusiasm for getting as much great stuff into 1.0.0 as possible, but the reality of where we are now is that only the most critical issues are in consideration for TEF+. Urgent means that it is an issue that *by itself* could keep the device from shipping.
A non-exhaustive list of examples for TEF+ blocking bugs include: a) failures in app installs and updates without obvious workarounds (like "try again") b) failures in app updates c) partner certification blockers d) high or critical severity security issues e) major regressions in user visible functionality or performance f) platform crashes/reboots g) frequent & clear STR crashers in core Gaia or partner apps Examples of bugs that are highly unlikely to be approved for TEF+: a) UI polish or jank b) performance improvements that don't block certification and aren't regressions c) any features or functional/platform improvements d) occasional correctness issues that can be easily overcome (say by restarting the affected app) e) infrequent app crashes These are just examples and are not intended as canon. But if you want to nominate a bug, please first ask yourself: "Is my bug more like the first group or the second?" Your help in keeping the daily incoming TEF? number down to only the well-qualified candidates will help the triager give the most important bugs the attention they need. If you have an important bug that you think still should be addressed but does not fit the above definition of a blocker, please nominate it as a tracking-b2g18 bug. While that list is not being aggressively triaged, it does provide some chance of landing your fix for 1.0.0 if it addresses a major issue AND has an extraordinarily low risk of regressions. At minimum it will help us prioritize for the 1.0.1 and 1.1 releases. Thanks! Lucas. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
