MozillaZine

AOL to Release New Netscape Update in Early Summer

Tuesday March 30th, 2004

The Inquirer is reporting that America Online is to release a new version of the Netscape browser. The upgrade will be a "'point' release based on the latest Mozilla code" and "will be made available in the very early summer timeframe." Speculation that an update was in the works began last week, when the San Francisco Bay Area's Mercury News paraphrased an AOL spokeswoman as saying that "there will be future versions of Netscape that are essentially repackaged upgrades of Mozilla."

The confirmation that a new Netscape release is on the way does not indicate that AOL is planning to provide any further development or financial support to the Mozilla project. Indeed, no AOL employees are paid to work on Mozilla and we can expect this latest version to be even more similar to Mozilla than previous releases. The more intriguing question is what made AOL change its mind about shelving the veteran browser.


#62 Re: Need help? Do it yourself

by lacostej <coffeebreaks@hotmail.com>

Monday April 5th, 2004 7:15 PM

You are replying to this message

I think the problem is not about having been discussing the plan from a long time. The problem is letting enough time between the decision and the act of freezing. If it was known that there was to be a long lived branch on 1.7 or 1.8, decisions should have been made to prioritize issues related to API stabilitization so that these issues would have been resolved before the actual long lived branch. Instead it looks like the bread is half baked.

So from an engineering perpective, I think this is a mistake. Furthermore it seems presomptuous in one way to only consider this or that project. There are many people working on extensions and in these develpers may lay the future of the project. Some of them will be future developers, many of them are making great efforts to advocate the mozilla line of tools. Not considering non-mozilla project as well, like Galeon and such is really a bad idea. If I was a non-paid developer working on one of these projects, I would be so pissed off that I would consider trying to embed IE engine on Linux instead. At least API is stable there.

I am not a mozilla developer, and as such I have nothing to say. But I am an early adopter, bug reporter and I've converted many people to the tools of the mozilla suite.

Asa, I am calling to your sense of leadership there. I may be wrong, but I think this is a mistake. This decision makes me sad, and I would be happy if it could be reconsidered.

Maybe the idea of making a short 1.8 (e.g. 7 weeks), used to implement the changes on top of the stabilizations issues fixed in 1.7 could make everybody happy?