Full Article Attached Mozilla 1.7 to Become New Long-Lived Stable Branch

Friday April 2nd, 2004

In a newsgroup posting, Asa Dotzler has announced that the Mozilla 1.7 branch will become the new long-lived stable branch, replacing 1.4. The stable branch is intended to act as a baseline for developers building Mozilla-based products, with critical bugs fixed on the branch as well as the trunk.

Mozilla Firefox 1.0, a new milestone of Mozilla Thunderbird, a new Camino release and several third party Mozilla based products will be based on Mozilla 1.7, so the Foundation is making efforts to ensure that it is high quality. To do this, the branching of 1.7 from the trunk has been delayed by a week to Friday 9th April and the final release of Mozilla 1.7 has been moved out a month to mid-May. Between the branching and the final version, three release candidates of Mozilla 1.7 will be made available, much like there were for Mozilla 1.0 and Mozilla 1.4. These release candidates will ensure that the 1.7 branch gets more testing and QA work.

While most welcome the fact that the aging 1.4 branch is to be replaced by something more modern, some developers have expressed concern that the decision to use 1.7 has been made so late in the release cycle.

#20 Ouch!

by jedbro

Saturday April 3rd, 2004 9:22 AM

You are replying to this message

I would like to hear ASA's opinion on the API problems that are facing the 1.7 release. Sure, 1.7 is important for Firefox/TB/Camino but what about the 200million users of Sun's Java Server to be released in China?

What about extension developers and other devs who base their work (which feeds them and their family) off of products and the stable "long-lived" release?

Personally I feel like Asa and "drivers" are giving us the middle finger. I thought these problems had been delt with in the past. 1.6 was an awesome product, and 1.7 will be too. But you are WAY too late announcing 1.7 as a long-lived release.

I have a novel idea! Why not continue with this new plan of delaying 1.7 to mid march and shooting for 1.8 to be the stable-branch. That way, Fx/TB/Caminoa/etc. will all get the exact same "stable release" from 1.7. And yet other vendors will be able to decide if they shoudl wait for 1.8 or dive into 1.7 "knowing the risks". That would keep everyone happy, and let the devs be devs.

Boris: Please don't let this reflect on your involvement in mozilla/gecko/etc. There is still time for this to be corrected.