MozillaZine

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, mozilla.org 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. mozilla.org 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.


#23 Re: why God why?!<RANT>

by astrosmash

Wednesday April 2nd, 2003 3:18 PM

You are replying to this message

> 1.- How can we prevent 'Phoenix' (the new moz browser) from going > the same route as mozilla went with undecisive UI decisions?

I agree. It seems to me that, at least from the outside, reasonably sane and simple UI modifications take forever to plow through the traditional Mozilla bureaucracy. Now that Phoenix is becoming Mozilla, I hope there will be a new Baby-Mozilla project that can act like a UI incubator in the same way Phoenix did. UI concepts need to be tested, just like everything else...

> 2.- In context to GRE, what will prevent ONE crash by GRE to ot take > down all my applications that are running off of it?

The GRE just means that multiple applications will share some common code.

Each application is isolated in its own process, so the crashing one doesn't affect any other, regardless of the code they may share (every Win32 application shares at least some code, provided in DLLs like COMCTL32.dll, COMDLG32.dll, GDI32.dll, KERNEL32.dll, etc)

Compare this with the way Netscape Communicator and Mozilla have historically done things: Mozilla isn't clever enough to share a single profile between multiple processes, so the browser, composer, and mail client must all execute within a single process, Mozilla.exe. Because of this single-process problem, a bug in Mail/News will bring down every browser window, and visa-versa.