Mobile/NativeFennecEndGame: Difference between revisions

From MozillaWiki
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

  1. No more than 10 crashes per ADU
  2. 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)
  3. Memory usage is conservative so the browser is kept alive and supports swapping/round tripping from browser to apps
  4. Rendering Perf: Panning, Zooming, and Scrolling Performance meet or exceed stock browser and chrome beta with full implementation of OMTC and GLLayers
  5. All P1 & P2 features are Resolved: https://wiki.mozilla.org/Mobile/NativeFennec1.0
  6. Sync feature parity: history, bookmarks, passwords, form data, tabs, and zero data loss issues
  7. Font Inflation is fully implemented
  8. UI and String 100% frozen
  9. First Run and Migration from XUL verified
  10. Add-On Support
  11. L10n sign off
  12. Product Sign-Off on Website compatibility: http://people.mozilla.org/~atrain/mobile/Evangelism/chrome-compare/chrome-compare.html

Release Criteria

  1. All of the above +
  2. No more than 5 crashes per ADU
  3. All P1 & P2 bugs reported against features are resolved as verified
  4. All regressions found during beta are verified as fixed
  5. Content Rendering and Readability are verified against Alexa top 50-100 sites (?)
  6. Zero security, privacy, and legal issues (obtain sign-off from those teams)