FennecNativeWeeklyStatus: Difference between revisions
| Line 77: | Line 77: | ||
#[COMPLETE] [https://bugzilla.mozilla.org/show_bug.cgi?id=695204 Site Security] | #[COMPLETE] [https://bugzilla.mozilla.org/show_bug.cgi?id=695204 Site Security] | ||
#[IN PROGRESS] [https://bugzilla.mozilla.org/show_bug.cgi?id=603008 Touch Events] | #[IN PROGRESS] [https://bugzilla.mozilla.org/show_bug.cgi?id=603008 Touch Events] | ||
#[https://bugzilla.mozilla.org/show_bug.cgi?id=695165 Forward] | #[COMPLETE] [https://bugzilla.mozilla.org/show_bug.cgi?id=695165 Forward] | ||
#[Clean up mobile XPCOM components] | #[Clean up mobile XPCOM components] | ||
Revision as of 04:25, 11 January 2012
Milestone Status
Feature Complete
Status: 80%
Why 80%?
P0 and P1 features as listed during the Toronto work week are verified except for Panning Perf. This does not include sync; we are in day-for-day slip but actively testing try builds which include support for sync setup, bookmarks, and history. APK available here: http://people.mozilla.com/~rnewman/0.3/fennec.apk
Panning Perf bug 695448 - (native_droid_panning) Panning perf Sync bug 709339 - [meta] First functional drop of native Sync
Beta
Status: At risk.
Why at risk?
due to Sync. Additionally, the following areas are considered beta blockers and need to be addressed in due time for verification testing in time to declare beta on January 31st (does this mean we pretty much need these things by 1/16 in order to verify them in time for beta?
All of the following P1's & P2's should be fixed prior to Beta; my challenge at this point is how to manage incoming bugs, I guess kbrosnan and I should discuss... Lucasr bnicholson Wesj Cwiis Pcwalton gcp Alexp blassey mfinkle margaret sriram mbrubeck
Mobile World Congress Announcement
Status: Coming Soon
Final Release
Status: Coming Soon
Feature Status
P0 Features
Required prior to cutover to Nightly
- [COMPLETE]Tabs
- [COMPLETE]Reload
- [COMPLETE]Session History
- [COMPLETE]App Updates
- [COMPLETE]New Layout Manager <--there are remaining panning perf bugs to be fixed but general implementation is complete.
P1 Features
Needed prior to cutover to Beta
- [COMPLETE] Viewport Support (Support for Mobile Versions of Websites)
- [COMPLETE] Awesome Bar
- [COMPLETE] Tabbed Browsing Support & Improved Design
- [COMPLETE] Set and Display Preferences
- [COMPLETE] Password Manager (Form Fill)
- [COMPLETE] Content Modal Dialog Prompt Support
- [COMPLETE] Download Notification, Progress, and Launch
- [COMPLETE] Native HTML5 Video Controls
- [COMPLETE] Secure Page Indication
- [COMPLETE] History: Browsing and Bookmarking
- [COMPLETE] Content Permission Prompts (i.e. Geolocation)
- [COMPLETE] IME Support
- [IN PROGRESS] Font Inflation <-- checkpoint on 01/16
- [IN PROGRESS] [Last Comment Bug 709339 - [meta] First functional drop of native Sync Sync]
P2 Features
We will not gate any milestones on the below
- [COMPLETE] Visual Indicators for Previously Visited Links
- [IN PROGRESS] Incremental Decompression
- [COMPLETE] Telemetry for Mobile
- [COMPLETE] Sharing
- [COMPLETE] Site Security
- [IN PROGRESS] Touch Events
- [COMPLETE] Forward
- [Clean up mobile XPCOM components]
Beta Blockers
Still a top priority for Fx11 (These are beta blockers)
- Performance
- Checkerboarding: symptom of us paper over slow painting.
lucasr should also be landing this tomorrow, we can ship sync without this, therefore, we can't ship without it: Bug 707150 - Add mechanism to enable/disable Fennec's local bookmarks/history DB we need dolske happy before this can happen, I need to get help Bug 704682 - Expose password database as a content provider so Sync can update it
Session Restore bnicholson should be landing this tomorrow: Bug 711578 - Session restore doesn't work for initial Fennec session crash
From there, we need these two to land before beta: Bug 697858 - Restore tabs from previous session, including history Bug 710735 - Show the appropriate thing on opening Firefox
AMO Support Met with Fligtar about this on Friday and he is all good to provide us what we need Bug 710323 - about:home - clicking on addons should go to their page in AMO
Not a priority for Fx11, we need to target for for Fx12, Fx13, these are not beta blockers, we can consider them high value once we have met all of our goals for Fx11. It doesn't mean we don't care about the customers who want these but we do have to stay focused on shipping by the end of 'Q1:
Character Encoding - Bug 701824 - "Show character encoding" (Text encoding) preference should be hooked up