Henri Sivonen wrote:
>>and HTML4 support
>>
>
> Do you mean Mozilla isn't ready for 1.0 until bug 7954 is not blocked by
> any open bug?
>
>
>>and no blocker bugs in other standards"
>>
>
> Are there blocker bugs in other standards that will come and haunt
> Mozilla if not fixed before whatever gets called "1.0". Are all such
> bugs already [HIXIE-P1]?
>
>
>>which it is perceived Mozilla 1.0 should deliver on.
>>
>
> However, each time Mozilla 1.0 is perceived as delayed (whether or not
> there has been an official date) people who don't take software
> seriously unless it has been rubber-stamped as release will think
> Mozilla is less and less relevant. This makes it more difficult to
> convince page authors that supporting standards and Mozilla is
> worthwhile, etc.
There's also a need to make contributors (or at least AOL/NS employees)
focus on less sexy work like polish. I know end-user stuff is somewhat
frowned on, but anybody that wants to ship a Mozilla-based browser is
going to need something with stable APIs and a polished UI that they can
base a product on. The powers-that-be have to bite the bullet and put
together a release sooner or later. Delaying it for further work on
areas where Mozilla isn't currently weak to begin with (standards
support, most performance characteristics, etc) doesn't seem to make sense.
>>Imagine what a terrible way of working that would be: if you beat all the
>>competition, you instantly stop innovating and improving.
Does it matter how good it is if you never ship a release users will trust?
--
http://www.classic-games.com/ http://www.indie-games.com/
I've often thought intelligence agencies should recruit idiots, as
idiots seem able to infiltrate any group in large numbers.
