Hi Folks,

We have a handful of bugs that look reasonable to cause a FF2 RC2:

        https://bugzilla.mozilla.org/show_bug.cgi?id=353160
        https://bugzilla.mozilla.org/show_bug.cgi?id=353264
        https://bugzilla.mozilla.org/show_bug.cgi?id=353266

We'd also really like to give the localizer teams time to finish up
their work - especially around the late changing en-US help.   Things
such as:

        https://bugzilla.mozilla.org/show_bug.cgi?id=353628
        https://bugzilla.mozilla.org/show_bug.cgi?id=353467
        https://bugzilla.mozilla.org/show_bug.cgi?id=353271
        https://bugzilla.mozilla.org/show_bug.cgi?id=353485

Schedule would look like such:

RC1 Release: Tuesday Sept 26
RC2 l10n Freeze: Thurs Sept 28 23:59 PDT
RC2 Code Freeze: Friday Sept 29 09:00 PDT
RC2 Release Target: Fri Oct 6

This schedule is pending feedback from RC1.  If we are forced to do
further Release Candidates we will not be taking any more l10n changes.

We are in the end game here - which means days matter and our tolerance
for risk is *zero*.  We will not take bugs unless they are of great
benefit: crashes, web compatibility, and major regressions.  IMHO FF2
RC1 is already a tremendously superior product to FF15.    So let's wrap
this up!

The release drivers will start approving bugs for RC2 by marking 1.8.1+
and commenting "Approved for RC2" in the bug.  Triage will continue
daily at 10AM PDT (650) 903-0800x91, conf# 8602.  You can join there or
#bonecho if you have any questions.

All the best,

Schrep

Hi Folks,

We have a handful of bugs that look reasonable to cause a FF2 RC2:

     https://bugzilla.mozilla.org/show_bug.cgi?id=353160
     https://bugzilla.mozilla.org/show_bug.cgi?id=353264
     https://bugzilla.mozilla.org/show_bug.cgi?id=353266

We'd also really like to give the localizer teams time to finish up
their work - especially around the late changing en-US help.   Things
such as:

     https://bugzilla.mozilla.org/show_bug.cgi?id=353628
     https://bugzilla.mozilla.org/show_bug.cgi?id=353467
     https://bugzilla.mozilla.org/show_bug.cgi?id=353271
     https://bugzilla.mozilla.org/show_bug.cgi?id=353485

Schedule would look like such:

RC1 Release: Tuesday Sept 26
RC2 l10n Freeze: Thurs Sept 28 23:59 PDT
RC2 Code Freeze: Friday Sept 29 09:00 PDT
RC2 Release Target: Fri Oct 6

This schedule is pending feedback from RC1.  If we are forced to do
further Release Candidates we will not be taking any more l10n changes.

We are in the end game here - which means days matter and our tolerance
for risk is *zero*.  We will not take bugs unless they are of great
benefit: crashes, web compatibility, and major regressions.  IMHO FF2
RC1 is already a tremendously superior product to FF15.    So let's wrap
this up!

The release drivers will start approving bugs for RC2 by marking 1.8.1+
and commenting "Approved for RC2" in the bug.  Triage will continue
daily at 10AM PDT (650) 903-0800x91, conf# 8602.  You can join there or
#bonecho if you have any questions.

All the best,

Schrep

At one point, after a similar discussion to do with 1.5, we discussed how we might go through and up the maxVer for extension authors who are non-responsive. And make it supersimple to update the maxVer of the extension without having to repackage and reupload the thing.

Anyone (morgamic?) know if any of that happened?

Also, are we doing any QAing of the most popular / featured extensions? I'm pretty sure we are, but was wondering where the test matrix for that might be located ...

Forgive me if this is covered elsewhere, but: should extension and theme
authors now be testing compatibility updating their code to say it works
with Firefox 2, so when people upgrade they can immediately renew all
their extensions? Or are we waiting until release?

Gerv
_______________________________________________
dev-planning mailing list
dev-plann...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-planning

Forgive me if this is covered elsewhere, but: should extension and theme
authors now be testing compatibility updating their code to say it works
with Firefox 2, so when people upgrade they can immediately renew all
their extensions? Or are we waiting until release?

Gerv

Hey Gerv,

Extension and Theme authors should definitely be testing with  
Firefox2.   We'll be reaching out explicitly to extension authors asap.

Mike

On Sep 25, 2006, at 5:42 AM, Gervase Markham wrote:

One other option would be (perhaps depending on User-Agent) to remove
them from search results or otherwise reduce their visibility on addons.
That might spur authors on to update things.

Gerv