We are weeks away from Firefox 2 Beta 2 and just a few months away from
final release. 1.8.1 includes a large number of fixes for long standing
bugs (some 5-7 years old!). As of this writing we have taken ~2300 bug
fixes, ~750 were opened before the ship of FF1.5/Gecko1.8. Taken as a
whole these fixes are helping to make FF2 the best FF release to date.
Now that we are bearing down on the final release the time has come to
concentrate on the issues that truly block the release. This means that
starting Friday at 10AM PDT the release triage team will not be
accepting bugs unless they meet one of the following criteria:
* Regression/Bug in a planned 1.8.1 feature
* Regression from 1.8
* Security Issue
* TopCrash
* Memory leaks or other major performance issues
* One of the following scheduled and understood issues:
o Visual Refresh
o Pref Panel
o Spell Check
o Tab Overflow
Reminder that the following rules still apply for all bugs:
* Has been on the trunk with no regressions reported in 2 days
* Must have a clear explanation in the bug of:
o Summary of the changes in the fix
o Risk assessment
o A reproducible testcase
o l10n impact
* Does not change any frozen API
* Does not change website compatibility or rendering
This means if you nominate a bug or patch that does not meet this
criteria it will be rejected/minused.
As always we can discuss in here or at a daily 10AM PDT triage call.
Cheers!
Schrep
I think this should have been "any API", not just "any frozen API"
(frozen APIs are frozen anyway ;-).
Frank
The original release date was slated at 1st July; release dates will
*always* move about, it's just part of life. :-)
--
James Ross <sil...@warwickcompsoc.co.uk>
ChatZilla Developer
You can track the schedule of the release here:
http://wiki.mozilla.org/Firefox2/Schedule
We updated it as we get new information during each milestone. Note
that future milestones are, as always, targets.
Best,
Mike