Abou Al Montacir <abou.almonta...@sfr.fr> writes: > Does improve distribution means hiding issues? I don't think it is.
You keep using this term, but I have no idea what you mean by it. What information do you feel like we're hiding? Maybe you feel like closing a bug is always wrong unless the problem is fully resolved? That's a philosophy about bugs that, I'm afraid, is only possible for small projects or projects with vast bug triage teams. (If you peruse the numerous articles on-line about backlog grooming, you'll find that not closing unactionable bugs is widely considered a huge *problem*, and experts in project management spend a lot of time telling people to be much more aggressive about closing bugs than they want to be.) "My Debian system froze" is not useful information for anyone, unfortunately, without a lot of additional work put into the problem. You say that you don't know how to do that work; I'm completely sympathetic, since frequently I don't either. However, not knowing doesn't change anything about the situation, nor does it mean someone else is responsible for helping you or I debug such problems. That's just how volunteer projects work. Not listing that line item in a bug page basically no one looks at isn't "hiding information" in any meaningful sense that I can see. Basically, you're attributing to the Debian project considerably more resources, expertise, data management, bug classification, and analysis capabilities than we actually have, and then (apparently) getting angry and frustrated that we we're (from your perspective) somehow withholding those capabilities from this bug specifically. But that's not what's happening at all! We have only a tiny fraction of the resources that you seem to think we have, and we're just trying to be explicit about what we can and can't do rather than having people's bug reports quietly disappear with no response. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>