MozillaZine

Update on 0.9.4

Friday September 7th, 2001

We asked Asa for a quick status on 0.9.4's status, which was for release this weekend, and here's what he had to say:

"Mozilla 0.9.4 daily branch builds are looking good. The mozilla.org Drivers have decided to get some additional coverage on the new "-turbo" mode, and we have added a few days to get it turned on by default in the win32 installer builds (don't worry, you can still uncheck the checkbox in the install routine). This and a few other late fixes have us targeting early to the middle of next week for the release. We're hoping for a good round of builds Monday, and barring any unforeseen problems, release soon after. Any help testing "-turbo" over the weekend and on Monday is greatly appreciated (you all have Bugzilla accounts, right?). The sooner we can find any problems or prove it's working the sooner we'll have our Milestone release."

Preliminary testing is showing -turbo to be a very solid new feature, so with a small amount of testing over the weekend, it should be good to go anywhere from Tuesday on.


#37 Re: Re: A vote against "turbo"

by niner

Sunday September 9th, 2001 8:46 PM

You are replying to this message

> 1) On which stone tablet is this written? Haven't you heard of TSR programs under DOS, and daemons under Unix? Who are you to cry that it's the Wrong Way?

But I am using this programs. If I have a deamon running, that there is a reason for it, like cron is doing things from time to time.

My personal reason against -turbo is, that it does not solve the problem of long starting time. It just hides it. And maybe programmers will not try to reduce starting time cause there is still the -turbo which is more convenient and maybe Mozilla will never get as good as it could be. So -turbo is a nice short to middle term feature but no long term solution in my personal eyes.

>2) Mozilla is turning on -turbo by default because it requires more testing, and Mozilla milestones are about testing Mozilla features. It does not necessarily mean that it will be on by default in Mozilla builds for ever.

If you ask me, it will. It gets more testing, thus getting stabler and better and when it's perfekt why should they turn it off? I think no one will want to lose this convenient way (at least for programmers) of getting Mozilla to start faster.