>I'm with Mike on this. You can never remove all bugs. Do you spend time fixing a bug that affects a handful of users or adding functionality that affects thousands of users, given that each take the same effort?
I think I'd try to deliver a finished product, not one that wasn't finished.
>
>The other problem is there isn't one team. Here are the teams I can think of. I'm sure I'm missing some
>
>- C++
>- Languages (all other languages)
>- Shell
>- Compiler (could be different team for each language)
>- CLR
>- DLR
>- Help
>- Editor
>- Data Tools
>- WPF
>- WCF
>- ASP.NET
>
>Plus the subteams in each, for example, VB, C#, F#, IronPython, IronRuby, etc.
>
>It's likely that integration issues will arise with the number of components that must be integrated.
>
>>It would be nice if they worried about making a release not buggy rather than just tossing out another new, unfinished, buggy product with cool sounding stuff in it.
____________________________________
Don't Tread on Me
Overthrow the federal government NOW!
____________________________________