MozillaZine

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.


#34 Re: ouch

by asa <asa@mozilla.org>

Monday April 5th, 2004 6:56 PM

You are replying to this message

"Why release a half-assed API"

Where was your criticism for the "half-assed API" in the 1.4 branch? Where was your whining about the half-assed APIs of the 1.0 branch? Can you even name a single API that you consider half-assed in the 1.7 codebase that's worse than what we shipped and supported in 1.4 or 1.0? Can you list the frozen (or even non-frozen but critical) APIs of the 1.0 and 1.4 releases and describe with any coherence how the full set of APIs for 1.7 is "half-assed" compared to the full set of APIs that were supported in 1.0 or 1.4?

When you're delivering gecko to millions of users and you've got a specific list of APIs that don't meet the needs of the application you're shipping, and you're offering up the resources that would facilitate our maintaining stability branches for both the mozilla.org apps and your embedding app, then come back with your protests, and those resources in tow. Short of that, how about letting up with the uninformed accusations, some appreciation for the people that are actually being asked to do the work to ship gecko to millions of users, and some acknowledgment that while we don't have the resources to please everyone, we're working hard to do the most with what we do have.

Or, you can go on whining about "half-assed API" that you're not even taking the time to thoughtfully describe or criticize but don't expect me to sink any time into replying.