MozillaZine

Drivers Update

Friday March 29th, 2002

The mozilla.org Status Reports was updated, and included some information on what drivers@mozilla.org are up to, and what's coming up:

"drivers@mozilla.org approved checkins for over 240 bugs this last week. We've taken a few more big-ticket items and have a couple to go. drivers will be ramping down this next week and actively soliciting fixes that we need to branch and have a Release Candidate 1 sometime (hopefully) late next week. We need to get RC1 out there quickly and get feedback on all the changes we've taken since 0.9.9 and at the same time we need the release to stand up so that users will put enough hours on it to give meaningful feedback. Please help us to get the builds into good shape over this next week with particular attention to recent regressions and topcrash+ bugs."


#41 Re: Re: Re: Let's all put our heads in the sand

by choess <choess@stwing.upenn.edu>

Monday April 1st, 2002 1:16 PM

You are replying to this message

Look, this isn't that complex. Adobe used an method from an interface in their plugin. The interface was NOT frozen. Frozen interfaces are clearly denoted in the source. Interfaces that are not frozen are subject to change at any time. That interface *did* change, as Darin fixed the last important bugs before it froze for 1.0, so the plugin was no longer binary-compatible and stopped working. Looking at the scope of the changes, it looks like there is not an extensive "rewrite" to be done on the plugin; probably some minor tweaking and a recompile.

We can't halt the development process and freeze interfaces prematurely because someone decided to use them before they were done. If you still don't get why the responsibility is with Adobe to fix this problem, I again suggest that you cease complaining about it and the Mozilla developers, because it's just making you look silly and ignorant.