Full Article Attached Classic Mac OS Build Likely to be Retired and Removed from Tree

Thursday January 9th, 2003

We've previously reported that the Classic Mac OS build of Mozilla is transitioning to port status but now it looks like the build could be removed from the tree altogether. In a posting to netscape.public.mozilla.seamonkey, Asa Dotzler has announced that no maintainer for the Mac Classic port has been found. If nobody steps forward by next Wednesday, the Classic Mac OS build will be removed from CVS.

In related news, is also moving the Mac OS X nightly and milestone builds from FizzillaCFM to FizzillaMach. This change will reap several performance benefits and will also make the builds easier to maintain. It is hoped that this transition will be complete in time for the release of Mozilla 1.3.

#18 Fantastic news!

by jensend <>

Friday January 10th, 2003 11:14 AM

You are replying to this message

This is great news. Mac OS Classic has always been the odd one out in crossplatform development; this will allow Moz devs to concentrate on things other than the build system and to have a more unified development front. If in 1998 Cygwin/MinGW had been at the level of quality it is now and Moz devs hadn't had to worry about Mac Classic, I have have little doubt we would have had a considerably faster, slimmer Mozilla 1.0, and it would have been released quite a bit earlier. The announcement that they will concentrate on the Win32, Unix, and Mach builds gives extra hope for the quality of 2.0.

In addition, to the poster who complained that Mozilla is dropping 80 percent of Mac users, I reply that the people who haven't upgraded to OS X are the least likely to be changing their browser to Mozilla. I think I saw a figure that said that OS X accounts for about 3/4 of the Mac Mozilla downloads. Moz developers have been spending a very disproportionate amount of effort on that other 1/4.

I do think, however, that they really should maintain the 1.0.x branch for Mac Classic. Mac Classic users deserve their bugfixes too (esp security bugfixes), and promising that the 1.0.x series will remain a very steady base to do cross-platform development work on and then dropping a platform in the middle of the series seems rather strange.