MozillaZine releases Mozilla Milestone 0.9.4

Friday September 14th, 2001 today released Mozilla Milestone 0.9.4. New to this release is the ability to disable the JavaScript method during page load and unload events. You can find more information on what's new at the release notes.

Builds are available on's download page(or go right to the FTP directory).

A recent post to the Mozilla builds newsgroup explains that Netscape will continue to check into the 0.9.4 branch. Work continues on the trunk toward Mozilla 0.9.5.

#140 Re: Why I'd like a 1.0

by asa <>

Tuesday September 18th, 2001 11:32 PM

You are replying to this message

>>Asa, I really think it is important to have a 1.0 mozilla release. Here are my reasons, I am sure others would agree with me:

Not the people that started this whole thing. From the original release mission statement: "So, Mozilla is a set of technologies, but not a specific (in biologic terms, Mozilla is a genus; a particular product is a species)."

>>1) I have no intention of using Netscape 6.x. I like Mozilla and I use it for all my day to day browsing.

No one is going to stop you. What's wrong with Netscape or Beonex?

>>2) I still use NS 4 for email, because I can't afford even the slightest risk of losing email messages. My business depends on it.

I've been using Mozilla mail (I'm an extreme user with tens of thousands of emails in dozens of folders, multiple accounts and a lot of traffic with hundreds of mails a day) exclusively since M10 (or maybe M9 or M11, can't remember now) about two years ago and I've never lost a single message.

>>3) I'd like a version of mozilla that has all the debugging stuff removed, which is rock solid as far as the mail app goes, which can support java and helper apps properly, is optimised as far as possible without more major codebase changes, and which has a stable api for third party developers to use. When this happens, it should be called 1.0

>>Those wants are not out of line with my 1.0 thinking either. I would like the codebase to be rock solid, support java and helper apps, optimized as far as possible (including major codebase changes if necessary), and stable/frozen APIs. The difference here is that I'm talking about code any you're talking about binaries. Mozilla isn't in the binary business and probably won't be anytime soon.

>>4) Once 1.0 is released I will remove NS 4 completely from my system and replace it with Mozilla 1.0. I'll still continue testing nightlies of mozilla, but 1.0 will be the benchmark with which to determine if something works or if it is broken.

Great. I'm not going to try to discourage you. If you want a 1.0 based product without debug and QA menus, however, you're going to have to build it yourself, hack those items out with userChrome.css or get it from someone else like Netscape or Beonex.

>>5) 1.0 is a psychological point for Mozilla. It says to people: the mozilla project has achieved something really solid. It says that Netscape are basing their new browsers on a stable product. It says to companies that they can develop third party extensions without worrying about having the rug pulled from under them. It validates the open source development model. It will be a great headline on Slashdot (I'm not joking). Finally, it might encourage more people to dip into the code and find out how it works. I am willing to bet you that sourcecode downloads for a mozilla 1.0 would go through the roof. All of these things would surely be of benefit to the mozilla community.

I agree completely (I think, unless you said something about end user binaries in there).