MozillaZine

Mozilla 0.9.6 Released

Tuesday November 20th, 2001

mozilla.org today made available for download binaries of the Mozilla 0.9.6 Milestone. The builds are available on the releases page, or you can get them directly from the ftp site.

New to this milestone are fixes for about 1,600 bugs including support for site icons in both the url bar and tabs (expect IE's favicons to show up in 0.9.7), displaying both Windows Bitmap (.bmp) and Windows Icon (.ico) files inline on all platforms, a new print preview implementation, Page Setup improvements on the Macintosh, Mail message 'labels' (Correction: This feature is not fully complete, only parts of the backed have landed.), and a new select and search context menu item, among others. If you are interested in more information on any of these new features, be sure to check out the release notes.

Also, mozilla.org last week released the source code on which Netscape 6.2 was based.


#166 Re: Re: Where it's at

by asa <asa@mozilla.org>

Friday November 23rd, 2001 2:48 PM

You are replying to this message

"I've discussed with you before why MTBF is a weak quality metric. A system could never crash and yet still be completely unusable"

You are the one that said "the stability situation is not under control". I responded to that statement with a comment about MTBF. MTBF is the primary measure of _stability_. Usability and stability are two different animals. I never claimed that MTBF was a measure of usability. Don't put words in my mouth.

"The open and assigned line is continuing to go up, which means that reviewed and validated bugs are continuing to be reported faster than they're being fixed."

That's what happens when you have 16,000+ reporters and only a couple hundred fixers. You'd be more confident about the product if we limited bug reporting to a sufficient degree that fixers could keep up with or outpace reporting?

"bugs must be fixed faster than they are reported to wind up with a product of reasonable quality."

I disagree. Closing the bug database to everyone but me would have the effect of causing bugs to be fixed faster than they are reported. The product doesn't get better by ignoring problems. If the total number of _known_ defects in a product is 10, you hire 1 million QA engineers to look at the product in more detail and they find 10 more bugs your quality has not been cut in half. If the number of people fixing bugs is steady and the number of people finding and reporting bugs goes up you're likely to see the reporting outpace the fixing, even in an improving product (and especially if you included requests to change or add features).

"That the browser is improving does not mean that it will be of sufficient quality to ship in a successful way any time soon."

I'd arague that is has already shipped in a successful way, and more than once. Active State's Komodo IDE is a shipping for money release. Netscape 6.1 and 6.2 are shipping releases which users and c|net reviews say it ties IE overall and there are more commercial releases coming. Mozilla has been of sufficient quality for vendors to ship for some time. Netscape 6.1 and 6.2 are proof of that.

--Asa