Firefox2/Schedule

This document is being reworked at the moment - update due by March 14th, 2006.

Please do not edit these pages without permission. Your feedback and comments are welcomed on the discussion page.

Milestones

Date	Task/Deadline
2005
	Publish initial Firefox 2 plan for feedback
	P1 Features and Leads finalized
	Initial Functional Spec for P1 Features
2006
	2nd Draft of Functional Specs
	3rd Draft of Functional Specs
	Functional Specs Complete aviary-2.0 blocking triage
	Alpha 1 lockdown
	QA testing on Alpha 1
	ALPHA 1
	Alpha 2 lockdown
	QA testing on Alpha 2
	ALPHA 2 - feature complete, although UI need not be final
	UI polish & revisions from feedback work on firefox2 blockers
	Beta 1 lockdown
	QA testing on Beta 1
	BETA 1 - feature frozen, string complete
	bugfixes & UI polish from feedback work on firefox2 blockers
	Beta 2 lockdown
	QA testing on Beta 2
	BETA 2 - feature & string frozen, wide public beta
	bugfixes & UI polish from feedback work on firefox2 blockers
	Release Candidate 1 lockdown
	RELEASE CANDIDATE 1
	Release Candidate 2 lockdown
	RELEASE CANDIDATE 2
	Release Candidate 3 lockdown
	RELEASE CANDIDATE 3
	Final QA testing on Release Candidate
	Release ready
	FIREFOX 2

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