Sometimes (often if you are writing a cloud appliation) there are strange errors or some kind of functionality simply did not work. As an old and experienced programmer I have no problem if there are errors within a product. It's simply the normal case. But what I am missing is a bug list (possibly with suggestions to get around the problem). Such a list would save hours of searching for a problem. Without a bug list you will try hundreds of steps to find a solution (or to find the real reason for the problem) often without success.
So like Rolf, on top of my wish list is a product without new features but with old problems solved and a buglist.
By the way. What's the meaning of a missing buglist? It didn't mean "there are no bugs" but it really means either "we have no idea about the bugs because we did not have a fully functional tracking system" or it means "we are not willing to help our customers". I know, this is an incisive wording, but our customers would kill us if we would do it the same way. Possibly this is because most of our customers are lawyers and such customers are very intolerant to failures. This is different if a customer is a technican...
