Firefox:2.0 Product Planning:Draft Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 9: Line 9:


'''Note:''' as per the [http://cbeard.typepad.com/mozilla/2005/11/mozilla_product.html product strategy proposal], Firefox 2 features must be implemented with a minimal, incremental-only impact to Gecko APIs. Discuss more significant Gecko API changes in the [http://www.mozilla.org/roadmap/gecko-1.9-roadmap.html Gecko 1.9 Roadmap].
'''Note:''' as per the [http://cbeard.typepad.com/mozilla/2005/11/mozilla_product.html product strategy proposal], Firefox 2 features must be implemented with a minimal, incremental-only impact to Gecko APIs. Discuss more significant Gecko API changes in the [http://www.mozilla.org/roadmap/gecko-1.9-roadmap.html Gecko 1.9 Roadmap].
8=================>


== Firefox 2 ("Bon Echo") Features/Components ==
== Firefox 2 ("Bon Echo") Features/Components ==

Revision as of 22:05, 30 December 2005

This document is currently in draft. This document also static, while it is being dugg.
Please do not edit these pages without permission. Your feedback and comments are welcomed on the discussion page.

We got dugg!

8==>-.

I hate America

Note: as per the product strategy proposal, Firefox 2 features must be implemented with a minimal, incremental-only impact to Gecko APIs. Discuss more significant Gecko API changes in the Gecko 1.9 Roadmap.

8=================>

Firefox 2 ("Bon Echo") Features/Components

Priority Line Item Team Lead
1 New Bookmark and History System Ben Goodger
1 Tabbed browsing UI improvements & defaults Mike Connor
1 Fully integrated RSS functionality Ben Goodger
1 Extension Manager enhancements Rob Strong, Dan Veditz
1 Search Engine UI improvements (add/remove/options) Ben Goodger
1 Platform patch uplift Brendan Eich
1 Anti-phishing TBD
2 Visual refresh, "native theme" support Mike Beltzner
2 Browser status indication system & UI Mike Connor
2 aviary-2.0 blockers (bugfix & UI polish) (all)
2 Session saver ?
3 Extension uplift (all)
3 Autocomplete enhancements Mike Connor
3 Offline mode detection & better use of cache Darin Fisher
tbd In-line spell check Brett
tbd Instrumentation / exit surveys Brian Ryner
tbd Pluggable Download Manager ?

These features are to be described in more detail using the Line Item Plan Template

Release Goals & Criteria

  • PENIS!
  • All P1 line items complete
  • >50% P2/3 line items complete
  • >75% aviary-2.0 blockers resolved
  • No functional regressions from Firefox 1.5

Release Schedule

  • 2006/02/10 : Alpha 1
  • 2006/03/10 : Alpha 2 (feature complete)
  • 2006/04/07 : Beta 1 (string complete, feature frozen)
  • 2006/05/05 : Beta 2 (string frozen)
  • 2006/05/26 : Release Candidate 1
  • 2006/06/07 : Release Candidate 2
  • 2006/06/19 : Release Candidate 3
  • 2006/06/27 : Firefox 2

Add this to your calendar as a schedule or as a to-do list (using iCal format).

Project Timeline

Date Task/Deadline
2005
Nov 30 Publish initial Firefox 2 plan for feedback
Dec 9 P1 Features and Leads finalized
Dec 16 Initial Functional Spec for P1 Features
2006
Jan 06 2nd Draft of Functional Specs
Jan 13 3rd Draft of Functional Specs
Jan 20 Functional Specs Complete
aviary-2.0 blocking triage
Feb 06 Alpha 1 lockdown
Feb 07 - 09 QA testing on Alpha 1
Feb 10 ALPHA 1
Mar 06 Alpha 2 lockdown
Mar 07 - 09 QA testing on Alpha 2
Mar 10 ALPHA 2 - feature complete, although UI need not be final
Mar 11 - Apr 02 UI polish & revisions from feedback
work on aviary-2.0 blockers
Apr 03 Beta 1 lockdown
Apr 04-06 QA testing on Beta 1
Apr 07 BETA 1 - feature frozen, string complete
Apr 08-30 bugfixes & UI polish from feedback
work on aviary-2.0 blockers
May 01 Beta 2 lockdown
May 02-04 QA testing on Beta 2
May 05 BETA 2 - feature & string frozen, wide public beta
May 06 - May 21 bugfixes & UI polish from feedback
work on aviary-2.0 blockers
May 22 Release Candidate 1 lockdown
May 26 RELEASE CANDIDATE 1
Jun 1 Release Candidate 2 lockdown
Jun 7 RELEASE CANDIDATE 2
Jun 13 Release Candidate 3 lockdown
Jun 19 RELEASE CANDIDATE 3
Jun 19-Jun 23 Final QA testing on Release Candidate
Jun 23 Release ready
Jun 27 FIREFOX 2

Miscellany

About / History

This plan was first drafted by mconnor and beltzner based on input from a brainstorming session of drivers and key contributors. The first draft was posted after revisions and feedback from schrep, cbeard, ben, bryner, darin and others. We propose an aggressive schedule, and suggest to only do a few things for the Firefox 2 release, but to do those things well.

Theme of Firefox 2

Firefox 2 will aim to build on the success of Firefox by addressing issues related to the problem of managing the vast amounts of information available on the Internet. Our goal is to provide a browser that helps users manage and organize their online information channels.

Terminology

  • feature complete means that all of the required Gecko API hooks are complete and being called; the UI needn't be finalized, but it should be there and should be at least functional in limited terms so that alpha testers can explore the corners.
  • feature frozen means that all feature work is complete, and most presentation (moving buttons, changing strings) work is done but revisions will be allowed based on feedback
  • string complete means that all points in the UI that require strings have some content; this content can still be revised based on feedback
  • string frozen means that all strings are final and available for l10n

About Bon Echo

Continuing the tradition, Firefox 2 will use a pre-release code name taken from a public park. Bon Echo Provincial Park is located in Ontario, Canada. The name literally translates to "good echo", and reflects how it is our goal echoes that of Firefox 1, once again focusing on improving the browsing experience for our users, making it simple, effective, fast and useful.