MozillaZine

Mozilla 0.9 Released!

Monday May 7th, 2001

mozilla.org today released milestone 0.9, which moves us a big step closer to a 1.0 release. The 0.9 release contains some of the largest changes in quite some time, with rewrites of the imglib, memory and disk cache, message view in mail, bookmark manager, Personal Security Manager 2 (PSM2), and the help viewer. Many of these rewrites have helped greatly enhance Mozilla's performance since 0.8.1, with the Mail front end rewrite and PSM2 being two of the largest improvements. For those of you who use Java, the JVM is now loaded on first use, rather than when you first start up, leading to much quicker startup.

Builds are currently available for Linux, Windows and Mac, on mozilla.org's download page. Expect other platforms to show up by the end of the week.

The next planned milestone is 0.9.1, for which the tree will close on May 23, and will be released a week or so following that date. Any milestone from this point forward has the possibility of becoming 1.0, and everyone is working hard to get the bug count down to make that happen.


#27 Good release, but ...

by NilsE

Tuesday May 8th, 2001 8:32 AM

You are replying to this message

A lot of nice things have been said about 0.9. It really is a good step forward. But I'm concerned about the project management. Mozilla is huge and complex, so bugs are often difficult to find and it seems that the number of open bugs steadily increases.

Different component groups continue with big code landings while even the basic browser functionality has lots of bugs. So rather than getting the basic stuff really good, more bugs are being indroduced. Do new users really care about a nifty feature in PSM2 while they encounter lots of bugs in imglib2, bookmarks, frame-focus, keybindings and other areas? My experience is: no, they don't.

I've seen quite some people turned away from Mozilla because during a first try, simple browsing was quite buggy (even with post-0.9 daily builds). Therefore, I would call for a kind of feature freeze or a similar measure (at least for some central components) to catch up on bugs. How do other people think about this?