The Mozilla Foundation this week changed development course with the suite, announcing that it no longer plans to release Mozilla 1.8 despite earlier betas of the update. Instead, it will end suite development with the current Version 1.7 line and instead focus on its standalone Firefox browser and Thunderbird e-mail client.
This may mean ending development of its application suite (an open-source combination of a Web browser, e-mail client and Web-authoring tool). But they have vowed to still continue providing infra-structure support to those in the community who'd like to continue developing it. The Mozilla suite had been code-named "SeaMonkey" right since its inception, and there seems a good chance of the Suite now being christened by that name. This name-change was probably necessitated to indicate that the mozilla suite is not anymore going to be officially made/supported by mozilla.org.
This eventual deprecation of the mozilla trunk, is not actually a shock, considering that it was supposed to happen all along. The firefox roadmaps clearly showed this. Where this decision might impact, though, is going to be on the newly-rejuvenated Netscape browsing suite (which relied on the mozilla trunk for code/updates). Those developing 3rd party applications based around mozilla, may not be much affected, as their base blocks of XUL interface and the gecko rendering engine, are alive and kicking in firefox andf thunderbird!
This may mean ending development of its application suite (an open-source combination of a Web browser, e-mail client and Web-authoring tool). But they have vowed to still continue providing infra-structure support to those in the community who'd like to continue developing it. The Mozilla suite had been code-named "SeaMonkey" right since its inception, and there seems a good chance of the Suite now being christened by that name. This name-change was probably necessitated to indicate that the mozilla suite is not anymore going to be officially made/supported by mozilla.org.
This eventual deprecation of the mozilla trunk, is not actually a shock, considering that it was supposed to happen all along. The firefox roadmaps clearly showed this. Where this decision might impact, though, is going to be on the newly-rejuvenated Netscape browsing suite (which relied on the mozilla trunk for code/updates). Those developing 3rd party applications based around mozilla, may not be much affected, as their base blocks of XUL interface and the gecko rendering engine, are alive and kicking in firefox andf thunderbird!
