You goal is one whe should all strive for, but I have been in the computer business long enough to realize that bugs will happen. I place them in two different categories. The first are those that I know are the software package and just plain bad code and inefficient testing. The other bugs are related to the computer environment changing around the package. You cannot program for furture changes in the world of computing expecially if you created the package when Windows XP was not even in existance.

Keep up the good work.

>>>However, we have decided not to make any announcments ahead of time, partially because we are not going to ship before we think it is ready. And with that I mean:
>>>
>>>1) Product is bug free and feature complete.
>>
>>You will be the first to accomplish this. :)
>
>Well, yes, granted, no product is ever bug free. So we are going to make it our goal to ship with at least 4 or 5 of them. :-) Perhaps I need to talk to Eric so he can put some back in... :-)
>
>Seriously though: I think so far Voodoo has been doing quite well as far as bugs go. There was one unfortunate release that broke Netscape compatibility (damn them! :-) ), that we had to post a fix for.
>
>And of course, there were lots of things that people wanted to do that we had to provide enhancements for. But there were very few things that were fundamentally wrong or misbehaved. In fact, to date, we have not had to make any fixes to the core rendering engine since the very first beta version.
>
>But of course, we are talking about a very complex environment, with an engine that does non-trivial things, in an environment that is somewhat unpredictable. For instance, this new version we are talking about has problems with the Opera 7 browser that we had to fix. They were caused by Opera identifying itself as IE6, yet at the same time it behaves different from IE6. So is that a bug? I guess so.
>
>It's just not fair... :-P
>
>Markus