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.

#26 Reply

by Dizzle

Saturday April 3rd, 2004 7:10 PM

You are replying to this message

Here is where the mistake lies:

>We did poll those people in November, and again in December and again in January, >and again in February, and again in March. In November, it looked like 1.7 or 1.8. In >January it looked like 1.7 or 1.8. In February, it started to look more like 1.7, but 1.8 >was still a possibility. In March, 1.7 won out. - quoted from Asa

If in November it looked like 1.7 or 1.8 and you knew that 1.7's release date would be near 1 year after 1.4 then you should have made a plan in November to make 1.7 the next stable release. If you told the other camps this information in November they probably would use the 1.7 branch even if their releases landed around 1.8 time. Did you not think to yourself "What happens if they branch of a non-api-stable 1.7 for FireFox 1.0"?

If people in charge want to pay me to build long term plans, I'm more than willing to offer my services.

If Firefox 1.0 becomes a crappy release (like Netscape 6) you may as well flush all the efforts we've made since Mozilla 1.0 down the drain.