Full Article Attached Roadmap Update: Mozilla Application Suite will be Sustained

Friday January 16th, 2004

Brendan Eich has updated the Mozilla Development Roadmap, adding a note that the Mozilla Foundation has no plans to retire the Mozilla Application Suite in the near future and will continue to release updates to the program, also known as SeaMonkey. This means that users of the Mozilla Application Suite will continue to benefit from changes made to core components such as the Gecko rendering engine and the Necko networking library. However, no major updates are planned for the frontend user interface, as the Foundation still wants to focus innovation in this area on the standalone applications, such as Mozilla Firebird and Mozilla Thunderbird. Sustaining the Mozilla Application Suite will benefit enterprises and other organisations that have standardised on Mozilla 1.x, as well as providing a smooth upgrade path for users of the discontinued Netscape browser and other derivatives of SeaMonkey.

Brendan Eich's newsgroup posting has more details about the Roadmap revision. A major Roadmap overhaul, outlining the path to Mozilla 2.0 and the future of the open Web, is planned for later this month.

#31 Reply

by Malc

Sunday January 18th, 2004 2:51 PM

You are replying to this message

Yes. If you don't like it, fork the tree. Maintain it yourself or with a group of like-minded people. If you want to share the results, organise your own servers and bandwidth too.

I want a Suite too. I want a better Suite. This means ditching the single process implementation in favour of a multi-process one. Mozilla Foundation's stated aim is to move the suite to the *birds. Thus the days of the single process implementation are already numbered. I want to hasten that and make the transition as soon as possible, for the final solution will be far better. Forcing a complete freeze on features on the monolithic implementation will either drive people away, or (the hopeful result) encourage them to place their efforts where the results will be more meaningful: bringing the multi-process implementation of the suite up to scratch more quickly.

You want to submit patches or new features, add them to the *birds instead of wasting your energy on the current implementation. Furthermore, by adding features to the current monolith, I would guess you increase the amount of work required to make the final transition and delay it further.