Full Article Attached Mozilla 1.0 Released!

Tuesday June 4th, 2002

Mozilla 1.0 is here! The final 1.0 builds, representing four years of development work by the open source community, are now available for download. The release of Mozilla 1.0 makes an important statement: now believes that the goals specified when the project began (and since enshrined in the Mozilla 1.0 Manifesto) have been met.

Mozilla 1.0 also represents maturity and dependability. Many of the Mozilla APIs, such as XUL, have now been frozen, providing guaranteed compatibility for developers building on the Mozilla toolkit. In addition, will continue to maintain the 1.0 branch as a stable and long-lived baseline on which vendors and other distributors may work. Further additive changes (mainly critical fixes) will be released from the 1.0 branch as 1.0.1 and 1.0.2 etc.

Mozilla 1.0 is available for download from's web site and FTP server. The Mozilla 1.0 Release Notes have also been updated.

MozillaZine would like to thank all the developers, testers, bug reporters, documentation writers, vendors and community members who have helped to make Mozilla such a success. We are proud of our years of service to the Mozilla community and intend to continue providing our growing audience with the latest in Mozilla news and advocacy for years to come.

[Mozilla 1.0 MZ Homepage]

#196 Re: Re: Re: Re: Re: Re: Moz 1.0 branches vs. Moz 1

by asa <>

Friday June 7th, 2002 11:21 AM

You are replying to this message

That's not happening. What is happening is continued development on the Mozilla trunk (the branch that will eventually become 2.0) and continued development on the 1.0 branch (from where we'll see 1.0.1, 1.0.2, 1.0.3, etc. releases). On the trunk we'll be taking high risk changes, new features, refactoring/rewriting of components, etc. We're going to try to limit these high impact changes to the 1.1alpha, 1.2alpha, 1.3alpha, etc. cycles so that we can recover in the 1.1beta, etc. cycle with a good 1.xfinal release coming about once a quarter. On the 1.0 branch we will be taking safer, lower risk fixes with the goal of never destabilizing the branch such that an organization intending to do a release from the branch should be able to pull code regularly and not have it be broken (that won't be the case with the trunk, especially during the alpha and beta cycles.) There is no need for a 2.0 branch.