MozillaZine

Mozilla 1.2.1 Coming Soon

Friday November 29th, 2002

Asa Dotzler writes: "We've discovered a bug in Mozilla 1.2 that can cause DHTML on some sites to fail. We've got a fix and will be releasing a 1.2.1 shortly.

"Also, the 1.2 release tag was not complete so builds created from that tag may have additional problems. If you're building Mozilla you can pull the tip of the branch or wait for the 1.2.1 tag to get the correct files.

"Sorry for the inconvenience."


#24 Re: Re: top-voted bugs

by asa <asa@mozilla.org>

Sunday December 1st, 2002 4:37 PM

You are replying to this message

"Developers know [bugs] are there but there are not enough qualified people to fix them."

Have we ever had enough qualified people to fix all the bugs that developers know about in the timeframe we'd like? No. Have developers been moving on to other projects (via new jobs or new interests) leaving bugs unfixed since the beginning of the project? Yes. Do I expect either of those trends to change? Not any time soon. Does that prevent Mozilla from getting better all of the time? Nope.

"Possibly as AOL moves more of the mozilla.org developers over to work on their proprietary AOL Communicator suite this problem will get worse."

AOL is moving developers that were contributing to Mozilla over to AOL Communicator? Like who? When?

I'm personally not as concerned with the quantity of developers as I am with the quality of the code going in the tree. mozilla.org has been gaining and losing contributors from the beginning but I think the code quality, especially in key areas, is getting better. All projects have turnover; Mozilla is no exception. With Mozilla this is true of organization and individual contributors. There has always been a shortage of people qualified to work in certain areas of the codebase and, yes, that is true today.

But we've got a lot of great new talent coming into mozilla.org. Individuals and massive corporations both. We've also lost some talent. It's nice that we have a number of corporate contributors and lots of individual contributors so that we're not completely dependent on the contributions of any one organization. Some of the most qualified engineers on the project in the more difficult areas aren't Netscape employees and many areas are developed almost completely independently of Netscape. Netscape may currently be the largest employer of developers contributing code to mozilla.org but they are not the only large contributor. Sun, for example has been ramping up development over the last year or so and their team is getting quite large. And there are contributors from RedHat, OEOne, IBM, Worldgate and other corporations as well.

We can always use more developer contributions. If you're concerned about manpower and you or your employer have engineering talent then step up with some code or encourage your employer to step up with resources. I'll be glad to help get you "plugged in" to our process and tools.

--Asa