* [2008-06-05 15:21:59 +0100] Colin Guthrie wrote:

> Tiago Salem Herrmann wrote:
>> Yes, unfortunately the software point of view is different. IIRC firefox 3
>> is still hanging with soundwrapper and there are annoying lines on text
>> boxes when using Ia-Ora theme.
>> We use the same spec file for all the distros, even CS3. That's why I'm
>> not sure if changing to ff3 is an easy task to do. But I agree that we
>> should think about how to change to ff3 as soon as we get all the known
>> major bugs resolved.
>
> I've not had time to fiddle yet so I'll see if I can work out the
> soundwrapper thing at some point. We can always disable soundwrapper
> anyway. I do find it useful for e.g. realplayer and other plugins, but if
> it has to be sacrificed then I say it's a small concession. IIRC 2008
> didn't have it.
>
> I think that secteam will probably want to keep 2.x around (and we should
> probably still ship it in contrib anyway) for a while and keep using it for
> the backports. Only when Mozilla EOL it do we really need to bother
> consider moving the older distros to FF3. I doubt the policy exception for
> new version of firefox extends to new *major* versions.... (if it did, it's
> probably the shortest path to a Vincent explosion ;))

Well, I would prefer to keep firefox2 going until mozilla decides to
drop it. I think there should be 6-12mos of maintenance on ff2 before
they EOL it. I believe they've done that in the past.

Regardless, we will need to be able to use the cooker ff3 specs as far
back as corp3 eventualy. But we're becoming quite pro for that... corp3
has seen mozilla suite 1.5.x, ff1, ff2, and soon ff3.

/me sighs

>> Negative reviews are really bad for us, but I believe that shipping a non
>> working browser is even worse. :)
>
> Hehe yeah! :)

I think for at least 2009, if ff3 is in main, ff2 should definitely be
in contrib.

--
Vincent Danen @ http://linsec.ca/