Comment 40 for bug 237690

On Wed, Jun 11, 2008 at 07:08:10PM -0000, Scott wrote:
> Richard Seguin wrote on 2008-06-05:
>
> > Thank you for reporting this issue... Our firefox team actually gets updated on a
> > regular basis about new releases...
> > As a result I am closing out this bug as they have there [sic] own work flow
> > methods on releases..
>
> That's just it. The problem is the workflow. Our otherwise *extremely*
> efficient Mozilla team has been very slow when it comes to Firefox 3.0
> updates.
>
> As of this writing, 3.0 RC2 is only in hardy-proposed and not in hardy-
> updates. RC1 spent most of it's time in hardy-proposed and only
> recently made it to hardy-updates. And of course RC1 is no longer the
> latest version.
>
> Firefox 3.0 Beta 5 is the *default* web browser in hardy and therefore
> should have been updated as frequently as the 2.0.0.x releases are in
> gutsy (and prior).
>
> Therefore, your typical user who doesn't change any default sources.list
> settings is still running Firefox 3.0 RC1 which has been out for quite
> some time. RC2 has been out for for a week (as of this writing).
>

thats not a problem and you cannot compare a b5 to RC1 transition with
a security 2.0.0.x release. Delay was expected here in order to do
proper QA. And we would even hold back 2.0.0.x if we discover a
critical regression.

In future all will be fine again and releasing 3.0 final in sync would
be nice ;)

 - Alexander