The Bunny is correct - I also work in the software industry (a major technology solution company you all know) and I have never seen a product that is completely 100% bug free - I don't think it exists...
We categorize the defects into priorities that are set by the stakeholders - which are not the developers, or QA teams or community specialist or even customer services - the priorities are set by upper management bean-counters, many of whom never even looked at our products and their word is LAW!!!!
The categories roughly goes as follows:
P1 = Things that blow up - catch fire and causes death and dismemberment - these get fixed 1st or no product.
P2 = Functionality and major or primary features - These get fixed 2nd - or no product.
P3 = Secondary features - as time allows but will release with known defects - to be address in updates.
P4 = Things we are prepared to live with and may address in updates - very rarely are P4 bugs addressed.
P5 = Wish list - things everyone would like to work on, develop or fix - but will never get a green light - ever.
Known issues (P3) are signed off by the stakeholders -and P4's are signed off by customer services as they are the ones who have to deal with it.
If it was up to the Dev and QA teams to sign off on release - you would never get a product to market because they would worry the thing to death and strive for the "perfect" product - which does not exists.
We have a deadline that is a little flexible - We (the dev teams) can hold back release if P1 and P2 defects are causing us trouble... but at some point - they will not continue to throw good money after bad - and will with out a second thought wipe the whole project, which always results in head chopping and layoffs.
As far as P3's goes - Sometimes a strong Dev manager can stall the stakeholders if there is some promising results and they can show a firm benefit to holding back a release - but more often than not if all your bugs are P3's and P4's - it's go time and they push for release...
You must understand that even on a simple project there can be 100's of P1 and P2 issues - 1000's of P3's.
Complex projects can be overwhelming - make no mistake - LOTRO is a complex project.
Often when you fix something other things in that feature set risks getting broken - often - even if the fix is simple - they will not risk a fix in a feature set or trunk of code that has been stabilized.
P4's are pretty much here to stay - and are the things that get worked out on the next product version if still relevant. (often features and technology changes between products so old P4 issues may not even exist in the next version)
Yeah - bugs are annoying - but unavoidable and better than the alternative - no product.
Take Care,
D.
[URL="http://forums.lotro.com/showthread.php?496094-The-Brief-Mr.-Bako-Bongo-In-Soup-Du-Jour."]My LOTRO Comics and Fan-Fiction[/URL]