That is why I don't like to see these kinds of complaint sessions here on comp.arch.fpga.
1) Antti would have received his answer through the hotline, but as he is an frieend of a friend, things were done to get a response back faster than it would have otherwise.
This may have been a mistake. With 250,000 active seats of software out there making designs, we have to support all of them, and try to do so with the same high level of quality. As much as I feel for Antti's situation, I can't respond to everyone. Peter and I would make a terrible hotline response team.
Instead, he and I act as "quality assurance" to make sure our responses are meeting the mark, and succeeding.
2) It opens the door for everyone who ever had an issue to add their two cents.
Of course we test the new software. In fact, we are adding test cases, and whole new test requirements with every service pack that goes out. Are we absolutely perfect? Not yet (one can hope). Is our software getting more, or less buggy? I think in goes in cycles. Virtex 4 added 100 (that we talk about) new features and capabilities. All of those had to get supported. That is a significant development of new software. For every X lines of code written there is a bug. For every Z bugs fixed, there is a new bug created.
Best thing you can do for software is stop adding new features to it, but unfortunately, we can't do that. Moore's Law has three of four more turns of the wheel left in it (in its present form - as far as we can see), so we must continue to do what has made us so successful, innovate.
(After 10 nm, no one really knows where we go, but we are certain that programmable logic becomes more valuable, not less, regardless of the technology. Carbon nanotube, organic self assembly, etc. are merely the means to implement the FPGA.)
I am not providing you with an excuse, just letting you know what the reality is. We test, and we test a lot. But, with new products, and new features, we can't be perfect, and we provide the fixes on a very timely basis (usually every bug found is fixed in the next service pack, or sooner by a tactical patch).