>
>These are all the same factors that any software developer should look at when reviewing a bug report! If we were all to analyze our apps, I'm sure we can all say that there are some known bugs in our system but we just don't have the resources to address each one .. especially the very obscure ones. And I'm sure most of us would also have to say that we don't "publish" a list of these bugs to our clients!!!!
>

Just to play devils-advocate here, generally, if our customers e-mail us a bug we eventually get back with them to confirm it, or offer a workaround. I think the main complaint is that the current implementation leaves developers hanging, with no feedback whatsoever. Great, you looked at it and confirmed it as a bug, and decided it wasn't serious enough to do anything about it. How about letting the developer that submitted it know that? Your customers would expect the same from you, wouldn't they?