See Firefox release schedule, published by Asa Dotzler on his blog:
See Firefox release schedule, published by Asa Dotzler on his blog:
Why Rapid Releases Can Improve Stability
Wow very well set out.
Spot on.
In all this, we always have only six weeks of new development work isolated in every such snapshot (or "version") and not more than a year like previously, so pinpointing a cause gets easier. Then, we less of a rush to get a feature into a specific version as there's another one coming just six weeks earlier, so things will only go into the code in a better thought-out state. Even more, we have switches of some way we can throw to disable problematic code and give developers six more weeks to get it into shape if needed. And over all that, we have roughly three months (twelve weeks) of pure fixing and stabilization period on every snapshot/version to get problems worked out, with different sizes of testing audiences.
...something surprising happened. We released Firefox 5, and Firefox didn’t get crashier.
In the months before Firefox's first rapid release, one concern echoed throughout engineering: crashes.
We had always relied on long stabilization periods to get crash rates down. Firefox 4 would be our last high-stability release. We hoped improvements on other aspects of quality would outweigh the decreased stability.
But then something surprising happened. We released Firefox 5, and Firefox didn’t get crashier.
VersionCrashes per 100 active daily users
3.6.20 1.8
4.0.1 1.6
5.0.1 1.4
6.0 1.6
Excellent
Last edited by SilverWave; August 27th, 2011 at 06:06 PM.
firefox 7.0~b2+build1+nobinonly-0ubuntu0.11.04.1~mfn1
And on we go
firefox-trunk 9.0~a1~hg20110826r75916+nobinonly-0ubuntu1~umd1~natty
9!
LOL.
A web browser is not a document viewer, it is a full-blown programming environment
Interesting...
Well saidWhy do people so often make these meaningless “Y MB of memory with Z tabs open” comments? My theory is that it’s because most people have no idea how complicated web browsers and web pages are. Mild experience with HTML authoring is endemic — heaps of people have thrown together a basic web page, and it’s just a document with with some structure and styling, right? So they think the difference between the website they wrote for their scout troop in 1997 (the one with the “under construction” animated GIF) and the front page of TechCrunch is merely a difference of degree, not kind.
They’re wrong. For one, HTML and related technologies are hugely more powerful and complicated now than they were a few years ago. Also, their scout troop website probably didn’t contain multiple megabytes of JavaScript code tracking its visitors’ every move. A web browser is not a document viewer, it is a full-blown programming environment with some very sophisticated text and graphical capabilities. A web page is not a document but a program. Therefore, the memory (and CPU) usage of different web pages varies dramatically.
Iran May Have Acquired Google SSL Certificate, Prompts Browser Security Alerts
Users are urged to update their browsers. It seems Mozilla will release an update today.
More info and discussion at http://ubuntuforums.org/showthread.php?t=1836052
2 Min job
Deleting the DigiNotar CA certificate
Bookmarks