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.


#110 Re: Re: you obviously haven't been paying attentio

by asa <asa@mozilla.org>

Wednesday September 12th, 2001 11:48 AM

You are replying to this message

"You could fix that by having AOL throw a little money and a few resources at the problem"

If this is true it is also true that you could fix that by having your company throw a little money and a few resources at the problem. Why don't you convince your comany to toss in half a million dollars.

"citing a bunch of "products" that have gone nowhere in the market is irrelevant."

I disagree that these products have gone nowhere. I don't think that market share is a fair measure of quality either. There are plenty of superior products which never become market leaders.

"you can't evaluate your defect curve because there aren't enough people to look at the incoming bugs"

Your proposition that the only measure of the quality of a product is a defect curve is wrong. Your suggestion that our quality has gone down because the number of known issues has gone up is wrong.

"I've discussed regression rate before. Try this: (LINK)"

You don't even know what that means. Reopened Status is not equivalent to regression. A significant percentage of those bugs are reopened for continued work. Unfinished work does not equal regression. You want us to change our catagorizations so that they fit your definitions so that you can more effectively criticize the progress we're making? Do you really believe that the codebase is of lesser quality than it was a month ago or 6 months ago or a year ago? Strange how everyone else disagrees with you.

" Dirty little secret about open source: it subsists on handouts, and gives nothing back."

Then why are you still involved? Just can't get enough of the one way street?

"It's expensive to pay for all those developers and AOL is in an ongoing cost-cutting regime."

I'm sure you have more insight into AOL than I do so there isn't much I can say here except that AOL is a major contributor to the project I work on and it would be a shame to see those contributions end. I hope they don't but I did't start working on this project because of AOL's contributions and I won't stop working on it if those contributions come to an end.

I'm done arguing with you. You obviously have a chip on your shoulder and it's a waste of my time discussing this with you since your only specific proposal seems to boil down to tossing out open source and magically creating half a million dollars for bug triage. That's not likely to happen so if you're sitting around waiting for it then get a comfortable chair because you're gonna be sitting for a long time.

--Asa