Package: qa.debian.org Followup-For: Bug #1039563 X-Debbugs-Cc: debbug.1039...@sideload.33mail.com
>> This is an example of different opinions about bug >< feature. > … > Trying to pick apart the example is an unhelpful distraction to the > discussion of whether the Debian project should have a procedure for > tracking mishandled bugs. I should elaborate further. The “bug vs. feature” bug suppression tactic is so effective and common that it has become a knee-jerk response by anyone looking to refuse a bug report, or those just looking for a quick and dirty way to push bugs out of the triage effort. Bug 1026922 demonstrates an abuse of the bug-feature bug-swatting technique. So actually the “bug vs. feature” debate is relevant to 1039563 in the sense that it showcases an irrational action-- one that solving bug 1039563 mitigates. That is, if bugs reach the wontfix stage as a consequence of a bug-vs-feature tactic, it could be marked as such. The quality of Debian packages can then improve by isolating these cases and counting them. If it’s happening often enough, the QA team could draft a criteria which would distinguish the more genuine bug-vs-feature cases from the irrational ones like that of bug 1026922.
