Firefox/Goals/2010Q2

From MozillaWiki
< Firefox‎ | Goals
Revision as of 00:22, 23 March 2010 by Beltzner (talk | contribs)
Jump to navigation Jump to search
Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.
  • [NEW] Publish and maintain a Firefox roadmap
  • [NEW] publish and maintain Firefox product plans for 3.5.x / Firefox.next
  • [NEW] Ship a Firefox.next beta before the Mozilla 2010 Summit
  • New Firefox Theme
    • Windows complete (no blocking bugs)
    • Beta quality for Mac, Linux
  • Feature Work
    • This is the quarter where a bunch of our awesome ideas need to very quickly get very solid.
    • Self-hosted Home Tab
    • App Tabs
    • Design/Implement better approach for privacy/security sensitive notifications
  • Jetpack Enablement
    • As with our feature work, this is the quarter where Jetpack gets real.
    • This isn't "a labs project," this is the Firefox SDK.
    • All 0.2-targetted JEPs completed, plus page-worker which is post-0.2 but feels very high value
  • Integrated Developer Tools
    • Beta quality designer-friendly inspector
    • Beta quality activity console with jetpack integration
    • Basic content debugging
  • Performance
    • We have some really solid knowledge about Ts and bugs in the queue, but we clearly have problems estimating the amount of ground we can cover in a quarter, too.
    • Ts still matters, but we're running into the fact that we don't "believe" clean Ts very much.
      • We should refine/rebuild that test to reflect a more plausible startup scenario (e.g. 5 tabs, timer only stops after we: start up, accel-L, type www.locallycachedgoogle.com, load that page)
    • Produce a complete startup timeline.
      • Identify 5 most expensive modules ("chunks of code"), focus perf work there
      • Example: make sessionrestore O(1) within the startup path (!)

Eng-wide Goals we should expect to be heavily involved with:

  • Ship Lorentz
    • We have work here around making sure the OOPP UI lands safely, but this is really eng-wide, and mostly on bsmedberg right now
  • Electrolysis
    • Able to build, run Firefox with a separate content process. (Things might break, chrome might not work fully, but the browser should stay standing).
  • J-PAKE
    • Working with Shaver, Lucas on how to articulate an eng-wide "land security features" goal