Firefox2/Schedule: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(switched ics file to the gcal)
No edit summary
Line 36: Line 36:
* intended for beta users, available in at least all tier 1 locales
* intended for beta users, available in at least all tier 1 locales
|- valign="top"
|- valign="top"
| Beta 2 || July 2006 || Product Frozen
| Beta 2 || August 2006 || Product Frozen
* based on feedback from Beta 1
* based on feedback from Beta 1
* all feature work is complete, including UI
* all feature work is complete, including UI
Line 42: Line 42:
* intended for beta users, available in at least all tier 1 locales
* intended for beta users, available in at least all tier 1 locales
|- valign="top"
|- valign="top"
| RC 1 || August 2006 || Release Candidate
| RC 1 || September 2006 || Release Candidate
* based on bugfixes from Beta 2
* based on bugfixes from Beta 2
* should represent final product
* should represent final product
* intended for wide audience of early adopters, available in all locales
* intended for wide audience of early adopters, available in all locales
|- valign="top"
|- valign="top"
| RC 2 || August 2006 || Release Candidate (if needed)
| RC 2 || September 2006 || Release Candidate (if needed)
* based on bugfixes from RC 1
* based on bugfixes from RC 1
* should represent final product
* should represent final product
* intended for wide audience of early adopters
* intended for wide audience of early adopters
|- valign="top"
|- valign="top"
| Final || August 2006 || Final Release
| Final || September 2006 || Final Release
* based on bugfixes from RC 2
* based on bugfixes from RC 2
|-
|-
|}
|}

Revision as of 18:04, 20 July 2006

Development Schedule for Firefox 2
The Mozilla Developer's Calendar holds the most up to date schedule for the development milestones and planned release dates of Firefox 2. You can either ...

The chart below describes the milestones, and maintains our original target dates and actual release dates for documentation purposes, and so that we can remember how long things actually took when planning future releases.

Planned Milestones (with target and actual release dates)

Release Target Description
Alpha 1 March 2006
actual: March 29, 2006
Developer Preview ("Dogfood")
  • includes new infrastructure pieces for stress testing and API feedback
  • intended for developers only, no guarantees about stability or dataloss
Alpha 2 May 2006
actual: May 12, 2006
Mostly Complete
  • all backend API/hooks are complete and being used by UI
  • UI design for features is complete
  • all new features are at least functional to the point of placeholder UI
  • intended for product testers and high-risk early adopters
Alpha 3 May 2006
actual: May 26, 2006
Feature Complete
Beta 1 June 2006
actual: July 12, 2006
Feature Frozen
  • all feature work is complete, including UI
  • all strings are complete and available for l10n to start
  • intended for beta users, available in at least all tier 1 locales
Beta 2 August 2006 Product Frozen
  • based on feedback from Beta 1
  • all feature work is complete, including UI
  • all strings are frozen, only necessary string changes accepted
  • intended for beta users, available in at least all tier 1 locales
RC 1 September 2006 Release Candidate
  • based on bugfixes from Beta 2
  • should represent final product
  • intended for wide audience of early adopters, available in all locales
RC 2 September 2006 Release Candidate (if needed)
  • based on bugfixes from RC 1
  • should represent final product
  • intended for wide audience of early adopters
Final September 2006 Final Release
  • based on bugfixes from RC 2