Mobile/NativeFennecEndGame: Difference between revisions
< Mobile
Jump to navigation
Jump to search
No edit summary |
|||
| Line 5: | Line 5: | ||
# Rendering Perf: Panning, Zooming, and Scrolling Performance meet or exceed stock browser and chrome beta with full implementation of OMTC and GLLayers | # Rendering Perf: Panning, Zooming, and Scrolling Performance meet or exceed stock browser and chrome beta with full implementation of OMTC and GLLayers | ||
# All P1 & P2 features are Resolved: https://wiki.mozilla.org/Mobile/NativeFennec1.0 | # All P1 & P2 features are Resolved: https://wiki.mozilla.org/Mobile/NativeFennec1.0 | ||
# Sync feature parity: history, bookmarks, passwords, form data, tabs | # Sync feature parity: history, bookmarks, passwords, form data, tabs, and zero data loss issues | ||
# Font Inflation is fully implemented | # Font Inflation is fully implemented | ||
# UI and String 100% frozen | # UI and String 100% frozen | ||
Revision as of 04:43, 13 March 2012
Beta Criteria
- No more than 10 crashes per ADU
- Raw Start should not exceed 200ms. Warm start with page load should stay within a certain % range of the built-in browser, we should be faster than Opera (Droid Pro, Nexus S, and Galaxy S2)
- Memory usage is conservative so the browser is kept alive and supports swapping/round tripping from browser to apps
- Rendering Perf: Panning, Zooming, and Scrolling Performance meet or exceed stock browser and chrome beta with full implementation of OMTC and GLLayers
- All P1 & P2 features are Resolved: https://wiki.mozilla.org/Mobile/NativeFennec1.0
- Sync feature parity: history, bookmarks, passwords, form data, tabs, and zero data loss issues
- Font Inflation is fully implemented
- UI and String 100% frozen
- First Run and Migration from XUL verified
- Add-On Support
- L10n sign off
- Product Sign-Off on Website compatibility: http://people.mozilla.org/~atrain/mobile/Evangelism/chrome-compare/chrome-compare.html
Release Criteria
- All of the above +
- No more than 5 crashes per ADU
- All P1 & P2 bugs reported against features are resolved as verified
- All regressions found during beta are verified as fixed
- Content Rendering and Readability are verified against Alexa top 50-100 sites (?)
- Zero security, privacy, and legal issues (obtain sign-off from those teams)