|
|
| Line 45: |
Line 45: |
|
| |
|
| == Issues and Risks<br> == | | == Issues and Risks<br> == |
| | | <br> |
| === Release Plan ===
| |
| | |
| * See page above
| |
| | |
| One of the more concrete things discussed was being good with labeling an aurora quality app on mobile, as "beta"<br> We need to specify specific quality, performance, and stability criteria around the above<br> If Fx10 for mobile is a "go", we will target Fx11 as the version for this Java UI release
| |
| | |
| Test Plans
| |
| | |
| * See page above
| |
| | |
| Need test cases and plans for functional, performance, and stability<br> elancaster and smooney are on point for this
| |
| | |
| === Sync ===
| |
| | |
| * need status
| |
| | |
| Built-in browser in ICS has bookmarks and history sync built-in and it is really easy to set up.
| |
| | |
| Sync in it's current phase isn't really usable. Passphrase: 20 characters long has and nobody can remember it; it isn't user-friendly to set-up. Jay does not want to ship with Sync unless it is easy to set up.
| |
| | |
| Product vote is that Sync by default should not be encrypted if we add passwords, we want to lessen the number of characters
| |
| | |
| Password sync is damn awesome in fennec; we don't want to lose it
| |
| | |
| Will write to the system store for history and bookmarks. Tradeoff: We will want to keep the passwords private b/c system store does not have the most optimal password protection. This should get better in ICS.
| |
| | |
| Proposal: Make sync an APK to be installed on any device; will support history for browsing, bookmarks, passwords, and possibly form history.
| |
| | |
| === Places ===
| |
| | |
| * need status
| |
| | |
| Highly migrated throughout the gecko; can't just enable/disable.<br> Colorizing Visited Links is broken; instead of leveraging places, we can fix this.<br> There is currently no reason to include Places into the startup pane
| |
| | |
| === Extensibility ===
| |
| | |
| * need status
| |
| | |
| We need to closely evaluate whether Add-ons will add a memory hit<br> Add-on support is extremely important to us; thew plan is to start by supporting restart-less add-ons<br> Jetpack support for mobile is interesting, though we are going to decouple from their schedule<br> Fabrice to build out ad-block plus<br> For v1, we will not support add-ons touching Fx UI<br> It will be way easier to re-write add-ons for Java than it was for re-writing electrolysis<br> We should help port over no-script they just finished and the have a ton of UI, openID just came online, too.
| |
| | |
| === L10n ===
| |
| | |
| We do not have a complete plan at this point.<br> Smooney is driving the l10n requirements.
| |
| | |
| [edit] Layout Transform API
| |
| | |
| Roc confirmed it is there & ready for us to develop with
| |
| | |
| === Update Snippets ===
| |
| | |
| RelEng needed to make sure it was generated<br> Christian is on-point for this; taken care of as of 10/26
| |
| | |
| === Ts Expanded ===
| |
| | |
| Home Tab and Twitter Pages; this will be a weekly, manual test owned by Mobile QA (Naoki, Kevin, Aaron)
| |
| | |
| === Video ===
| |
| | |
| Flash: pre-honeycomb support is being worked on. Jay is following up.<br> h.264, Jay is following up.
| |
| | |
| === ARM v6 (p2) ===
| |
| | |
| Our hardware targets do not include ARMv6 phones<br> We need to do some things to make it run: turn off the jit, possible pix- stuff<br> Does it run, how quickly can I make it run, when I do and if it is slow, how much work will it be to be less painful?<br> Ted is on this; elancaster is getting him an ARMv6 phone
| |
| | |
| === JS Optimization for ARM ===
| |
| | |
| We need to connect with the JS team on whether there is any low-hanging fruit<br> We need to get better with v8<br> Damon is on point to circle back with dmandelin
| |
| | |
| [edit] Fx10 for mobile
| |
| | |
| Will complete the cycle; we will get good platform testing for c2p<br> When Fx10 moves to aurora, there will be the usual cost associated with the cut overs<br> Agreed to do a Final go/no-go
| |
| | |
| [edit] Marketing
| |
| | |
| We sign-off in October<br> We need a go-to-market plan <br>
| |
| | |
| <br> | | <br> |