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.]


#13 Modularity, clean installs, and upgrade paths.

by Waldo

Wednesday June 27th, 2001 1:40 AM

You are replying to this message

Gerv says:

"Modularisation. It has long been a goal of mozilla.org's to get the Mozilla codebase into a state where each component could develop independently and you could pull and build the "latest stable" release of each component to make a stable browser. This can only happen when APIs freeze. I would therefore suggest that this reorganisation be the key priority in the immediate post-1.0 period."

The idea that you can pop modules in and out of Mozilla in order to upgrade or extend it is a big deal and I think important to get right so that upgrading to 1.1 doesn't mean another full 11 meg (or more) download. Ideally after 1.0 you'll be able to pull just a new renderer or a new UI or whatever, right?

Will Mozilla be able to do any kind of "smart upgrade" to take advantage of the modularity? I haven't heard of this...is this something we should see in a 1.0 release?

Also, maybe 1.0's installer should come with some kind of "sweeper" for everyone who's been using nightlies and betas and netscapes and stuff that deletes old registries and stuff so that people are sure to be getting a nice fresh clean install that can then be updated cleanly to 1.5 and 2.0 and onward.

W