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.

#19 This sounds bizarre

by ostiguy

Wednesday April 2nd, 2003 2:49 PM

You are replying to this message

Ugh. I am a MCSE sysadmin type, so I am on a lot of MS centric mailing lists. Just today I got a message about the panoply of licensing options (shrink wrap vs volume) and package versions of the forthcoming Office 2003: basic standard professional professional enterprise small business edition...

... you get the point. The value of Office is diminished when you are no longer certain that my version of a suite (office, mozilla), can do all the things that your installation of said suite. 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.

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

Moving to a more component oriented model is going to raise the bar for 3rd parties to package and develop on them, as keeping versions in sync will be like spinning plates - instead of testing your web site against a gecko based browser, you probably will need to test it against many more permutations, or, if you are like far too many, you'll simply decide its not worth it to deal with these OSS lunatics and their 1 user to 1 browser version ratio, and craft some javascript nuisance ware that attempts to punt away visitors to your root page.

Bloat is a ridiculous argument - look at the walmart lindows pcs - we all live in the age of having more cpu and ram than we know what to do with for short money. Its painful to see the bloat argument apparently torpedo the most "Mom ready" polished OSS software package into a grab bag of componentry.

I am definitely on the periphery of all moz development, as I am but an end user who has been kicking its tires since the .9something beta days. I just find it strange that a process that seems to have been releasing more features more quickly than IMHO any other phase of the 5 yr project is about to change things dramaticalls.

I hope my fears are unfounded.