MozillaZine

Full Article Attached Towards Mozilla 1.0

Tuesday June 26th, 2001

Gervase Markham recently posted his feelings on what a 1.0 release of Mozilla would be. Gerv has sent us the follow-up to that posting, including much of the feedback he received. To read it, click the full article link. Once you have read through it, we welcome you to post your feelings on what you think a 1.0 release would have. [As Gerv says, please don't post your favorite list of bugs, only the criteria for choosing what bugs to fix.]


#17 Re: [INSERT TITLE HERE]

by asa <asa@mozilla.org>

Wednesday June 27th, 2001 2:22 AM

You are replying to this message

"There should be zero crasher bugs in the main components themselves."

Not gonna happen. Not worth even shooting for. I'm not gonna hold mozilla 1.0 because one bug crashes one AIX user one out of every 50 times she accesses one particular site. a little exaggerated but do you see my point. Mozilla compiles on more than a dozen platforms today and may compile on even more by the time we get to 1.0. Even if it only built on one platform I think that zero crashers is simply unrealistic. It becomes even more unrealistic when you consider that anyone can file a crasher bug in Bugzilla any day. I could compile my own build for Mac OS X and not being very sophisticated in the build process I could leave something out or pull on a red tree producing a build that crashes on startup. Would it be reasonable to hold 1.0 because I file a bug the day it's scheduled to be released saying my OS X build crashes on startup? I know these are a little exaggerated examples but the point is that zero crashers just isn't realistic. Maybe something like zero crashers which have been confirmed to affect some significant (what's the number here?) percentage of Mozilla users might be a little more realistic. Even that seems a little extreme. A crash might affect all platforms but not unless the user followed some really exotic/unlikely series of actions. I think it would need to take into account how many users could be affected and how often they are likely to be affected.

--Asa