MozillaZine

Whither M14?

Thursday February 17th, 2000

M14 is being handled a little differently than previous Milestone builds, according to this news post from Jim Roskind. Instead of building a solo M14 branch, and stabilizing that, they are going to continue to squash PDT+ and Beta flagged bugs, and will flag some daily builds this week as potential M14 candidates.

Jim also talks a bit about Netscape's beta plans. Their list of "beta blocking" bugs is shrinking quickly, but they haven't yet reached a point where Netscape feels comfortable doing a "beta" branch for stabilization. Jim says that he hope that happens "in short order".

We have to wait, but if some of the improvements over the past week are any indication, it will definitely be worth it.


#11 Re: CSS and correctness of Gecko?

by sacolcor

Saturday February 19th, 2000 9:29 AM

You are replying to this message

I would agree that the volume of bad HTML out there will probably slow Mozilla's penetration. However I don't think that that should be Mozilla's concern. Mozilla isn't a commercial browser, and shouldn't be driven by a need to grab market share. Mozilla is an open source project designed to implement the W3C standards properly, and once it's accomplished that goal, and reached an acceptable threshold of stability and responsiveness, it's ready for release. If Netscape (or anyone else) then wants to put in the effort to extend their branded versions to address commercial concerns, that's up to them...Mozilla can independently move on toward adding support for CSS2 and XSL.

If MS releases an IE6 that is fully W3C-compliant, I'll consider Mozilla to have been a resounding success for raising awareness of the issue. My goal is to see a web where a web developer can write a page to W3C specs and expect it to work.