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.

#9 Re: CSS and correctness of Gecko?

by sacolcor

Friday February 18th, 2000 3:19 PM

You are replying to this message

I completely disagree with the idea of Netscape continuing to support the mistakes of the past (Bugward compatibility, as it is commonly termed). Doing so would probably add another year onto the ship time, and an extra meg or two to the size of the distribution, and the only 'benefit' gained would be to allow/encourage web designers (and web authoring tool designers) to continue writing sloppy code.

On the other hand, I completely agree with the rule of not shipping until HTML 4.01 and CSS1 are tested and known to be completely and precisely supported. Netscape and Mozilla have committed to this publicly for a long time, and it is, IMHO, Mozilla's major selling point. Breaking those promises and releasing with /any/ HTML or CSS bugs outstanding would greatly diminish Mozilla's reception, and I don't think anyone involved in the release decision would want such a thing.