Mozilla ices Firefox 4 beta 12 release to nail final bugs
Temporary breather could push release to March
Customer Success Testimonial: Recovery is Everything
Mozilla looks set to miss its February deadline for the release of its forthcoming browser Firefox 4.
The open-source outfit delayed building beta 12 of Firefox 4 late last week, because Mozilla wanted to stamp out the few remaining hardblocker bugs found in the browser, before releasing the latest test build.
Earlier this month, Mozilla seemed pretty confident that the 12th Firefox 4 beta would be the final test iteration, after originally mulling the prospect of a pushing out a 13th beta.
"As of now, beta 12 is the last planned beta," Mozilla's Christian Legnitto wrote last week.
"We reserve the right to have a beta 13 if issues found in beta 12 need additional coverage before a release candidate (RC)."
However, beta 12 has been temporarily iced while the team await the final list of bugs, or "betaN hardblockers[1]", prior to releasing that test build.
All of which could push the final release of Firefox 4 into March. The browser has been subjected to a series of delays, while Mozilla has battled to get its bugs list down to zero.
Mozilla's Asa Dotzler saw reasons to be cheerful this morning.
"From what I can tell, there are only seven unwritten patches standing between Firefox 4 and hundreds of millions of users. yay :-)" he wrote on Twitter. ®
COMMENTS
Good stuff
It's good that they are desperately trying to stamp out on bugs. Sure, it is taking ages, but what is better? Releasing early with many bugs, or being late with major bugs removed?
fine for me
I've been using FF4 since about beta 4. Main problems i had then were broken add ons. It's got better every time, FF 4 b11 is completely usable for me.
I would love to use Chrome as by all accounts it is fast, stable and secure. Just two problems. The interface is completely uncustomizable - you have the buttons Google decides on, where it decides you have them and the size they decide they will be. You cannot change a thing. And secondly, the add ons are completely limited. In FF they can change pretty much anything, so most minor annoyances such as tab behaviour can be remedied if you find the right add on. In Chrome, add ons seem to be limited to adding extra buttons in the space provided on the toolbar. So my complaint about not being able to customize the layout and buttons cannot even be fixed by add ons.
Chrome is up to version 120 something and it still looks exactly like it did first time out. I appreciate all the work under the bonnet but surely it's about time they did a little bit of diddling on the outside where its usability is awful.
Security feature?
Sadly Verified by Visa isn't a security feature at all, it's just a way for Visa to offload the risk of loss through stolen cards onto the retailers rather than suffer the risk itself.
The fact that there's no actual verification that you own the card when you set it up or say you've lost your password blows up the idea of it being for security.
IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
Steps to Take Before Choosing a Business Continuity Partner
Enabling efficient data center monitoring
