Mozilla 1.4 to Feature Reorganised Release Notes

Thursday June 26th, 2003

Asa Dotzler has announced that the Mozilla Release Notes are to be reorganised and given a partial rewrite. Referencing Zach Lipton's recent thoughts on the matter, Asa describes how the release notes will be divided into several files, including a what's new document, an installation guide and a list of known issues. A lot of the older and less important information will also be removed. It is hoped that these changes will be made in time for the release of Mozilla 1.4 on Monday.

#6 Re: Re: Re: What's New section needs improvement

by asa <>

Saturday June 28th, 2003 12:51 AM

You are replying to this message

"there are plenty of people that want to know what changes between betas"

That's exactly how it works. Major changes happen in alpha and beta. Few changes happen in the final (and rc) cycles. The what's new section highlights _some_ of the important features or major bugfixes that were landed between, for example, 1.3final and 1.4alpha <>, and 1.4alpha and 1.4beta <> . The 1.4final release notes, what's new section, will highlights the impoortant or high-visible changes (mostly features) that happened between 1.3final and 1.4final <…ozilla1.4/README.html#new> .

This isn't a changelong. If it was it would be nearly 2,000 items long. If you want that you can ask bonsai or bugzilla.

"and who are all these people that are just using the "final" releases?"

You could just as well have asked "Who are these people using alphas and betas when nightly builds are where the real effort happens." or "Who are all these people testing nightly binaries when the real work comes from people that build themselves."

Who are they? They are hundreds of thousands, maybe millions of people that want to download the Mozilla suite of applications. They provide invaluable feedback through bug reports, talkback and comments on weblogs like MozillaZine and Slashdot. Mozilla benefits immensely from all of the feedback we get at all levels from people making their own builds, to nightly build testers to users of milestones, alpha, beta and final. The better job we do expanding all of those pools and building even better feedback mechanisms, the better Mozilla gets.