Firefox2/Schedule
< Firefox2
Jump to navigation
Jump to search
This document is currently in draft.
Please do not edit these pages without permission. Your feedback and comments are welcomed on the discussion page.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 |
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