Links Toolbar Landed
Wednesday October 3rd, 2001
Gervase Markham writes: "The Links Toolbar from bug 87428 has finally landed, bringing us ever-closer to full support for HTML 2.0. You'll see it in this morning's builds. The auto-show is still in development over in bug 102832. Good places to try it out are Bugzilla buglists, the W3C, htmlhelp.com and many machine-generated manuals or documents, such as the GNU Make manual."
#100 Re: Re: Re: Re: Re: Cool, but ...
Friday October 5th, 2001 11:25 PM
You are replying to this message
"Netscape people manage the source, and they let this checkin happen during feature freeze"
strauss, you've been critiquing this project for sufficient time to have at least accidentally picked up some information about how it works. Netscape people do not manage the source. mozilla.org manages the source. mozilla.org is not Netscape. Some (about half) of the people that coordinate this project (<firstname.lastname@example.org>) are paid by Netscape but in no way does Netscape "manage the source". You're just flat wrong on this.
Your're also wrong when you claim that there was a feature freeze. There was a Milestone code freeze. This freeze is not a "feature freeze" it's a "code freeze" during which we only approve fixes that are of high value to the Milestone. This feature landed _BEFORE_ the freeze on 10/2. You're just plain wrong again.
But you couldn't stop. You were on a roll with incorrect statements like "a bunch of Netscape people spending a ton of time". There were no "bunch of Netscape people". One Netscape developer who had an interest in the development of this feature spent some time helping the developers of this feature work out fixes for it. In reality the "bunch of people" during the last few days were non-Netscape developers helping Netscape developers fix other bugs that are important to the Milestone.
This software project has had many stable releases. See ActiveState's Komodo, Netscape 6.1(more stable than 4.x), Bloomburg client, Galeon, and a lot more. You don't follow the process or projects close enough to make all these claims and even if you did you've made your bias and hopes for Mozilla failure well enough known that I wouldn't trust your claims even if you were better informed.