Get Firefox 3 RC3 now!

For Windows and Linux, RC3 = RC2.

God, how many flipping RC's will there be?! Just release it already!

Er, as many as it takes?
There's a reason why they keep pushing another candidate - there's something wrong with the old one that's bad enough to block the release...
 
only pic lens. but does it if I remove that as well.

Hmmm, I'd be tempted to disable all of the add-ons and enable them one by one to see if there is a particular one that the causes it.
Is it only particular sites it happens on, or after a particular length of time ? Is you RAM being maxed out (causing it cache stuff/use paging file or caching) ?
Unfortunately it may be a combination of the above or just one of them, it's just a case of fiddling and logging when it happens and trying to recreate it happening :-/

tolien said:
Steps to reproduce would be a start...

Exactly :)
 
appears to be random, although someone else said it might be to do with flash. Next time it happens I'll have to remember what page it happens on.
 
A new profile might help if you haven't already tried it, Flash 10 seems to work better than 9 and you need at least Silverlight 2 beta 2.
 
God, how many flipping RC's will there be?! Just release it already!

Well unless you're on a Mac, RC3 and RC2 are exactly the same. So this should be the last RC, unless some showstopping bug is discovered at the last minute which seems unlikely. Won't be long now!
 
Er, as many as it takes?
There's a reason why they keep pushing another candidate - there's something wrong with the old one that's bad enough to block the release...

Yes, but in fairness these should have all be sorted in Unit tests, Integrations testing, User acceptance testing etc....Not at RC stage
 
Yes, but in fairness these should have all be sorted in Unit tests, Integrations testing, User acceptance testing etc....Not at RC stage

IIRC it was a new issue which came about because of an Apple update. It's actually an Apple problem, but Mozilla have worked round it.

Besides, what would be the point of an RC if you waited until the product was perfect before releasing it? Many pieces of software have a few RCs. There're some issues that only pop up when the product is released to the public rather than in a limited beta test.
 
IIRC it was a new issue which came about because of an Apple update. It's actually an Apple problem, but Mozilla have worked round it.

Besides, what would be the point of an RC if you waited until the product was perfect before releasing it? Many pieces of software have a few RCs. There're some issues that only pop up when the product is released to the public rather than in a limited beta test.

I'm a Release Engineer for a medium sized software company and have never felt the need to introduce RC's. It just confuses the punters imo. Emergency Patches can always be released at a later date if there is a majore showstopper
 
RCs get a hell of a lot more testing than betas ever could, just by virtue of the number of users who try them. There's ~14000 bugs fixed between Fx2 and Fx3, so a few regressions missed are hardly a big deal - and Fx3 has more unit test coverage than any of it's predecessors...

It's lose-lose. You ship early with bugs, people moan. You ship later with bugs fixed, people moan. You can't win.



Emergency fixes straight after release are just another expression for RCs. The only difference is you don't push RCs to users who didn't ask for them.
 
Back
Top Bottom