Full Article Attached Major Roadmap Update Centers Around Phoenix, Thunderbird; 1.4 Branch to Replace 1.0; Changes Planned for Module Ownership Model

Wednesday April 2nd, 2003

In the most radical change to the Mozilla project since the late 1998 decision to rewrite much of the code, today announced a major new roadmap proposal that will see Phoenix and Thunderbird (also known as Minotaur) becoming the focus of future development. According to the roadmap, 1.4 is likely to be the last milestone of the traditional Mozilla suite and the 1.4 branch will replace the 1.0 branch as the stable development path. is also proposing changes to the module ownership model including a move towards stronger leadership and the removal of mandatory super-review in some cases. Please click the Full Article link to read the full analysis.

#22 Re: That sounds bizarre.

by spage

Wednesday April 2nd, 2003 3:17 PM

You are replying to this message

Your fears seem mostly unfounded.

> Currently, if I have moz, and you have moz, we can be reasonable certain that our functionality is highly similar. It sounds like wants to get away from this, and this is a bad thing.

Not if you're exchanging documents. HTML and XHTML will work identically in a standards-compliant way between any Mozilla variations. But yes, from a support aspect it could be a problem. It sounds like your company is a candidate for a suite based on Mozilla that has the configuration you want. (The obvious answer is to take the time you waste reading MS licensing policies and spend it building your own distro with the extensions enabled that make sense for your company. :) The Mozilla project has always struggled with delivering an end-user product vs. open source project, a corporate product is yet another variation.

> Having less tightly coupled applications is likely to have a higher correlation with increased bugginess with interaction between them.

Yes, but what amazing integration is there between the current Mozilla Mail and Browser windows? And if done right separate apps will really shake out and improve the Toolkit and Runtime layers in a way that a monolithic app doesn't.

> Bloat is a ridiculous argument

Re-read the roadmap, it only mentions bloat once in the context of improving Gecko. The roadmap is an argument about project organization and focus.

> Grab bag of componentry

Re-read the roadmap. "we will likely ship with all of the popular extensions installed but disabled, so that they can be easily turned on by those who wish to use them, and uninstalled by those who don't." Sounds like a win to me, and a lot easier for Mom to deal with than the current Mozilla.