On 07/22/2013 03:05 PM, Fernando Cassia wrote:
First of all, I have, in fact, included reproduction steps in all of the bugs we're discussing here. I am dissatisfied with the way those bugs were handled exactly because the maintainer closed them with INSUFFICIENT_DATA despite the fact that reproduction steps were provided. In short, your interpretation of the events in question is factually incorrect.It seems to me like you don't know how to report bugs. Bug reports should include STEPS TO REPRODUCE, ALWAYS, it is not "OPTIONAL". Second, reproduction steps are not the only way that a bug can be tracked down. ABRT bugs, for example, include a stack trace and a bunch of other information intended to allow the maintainer to try to track down the bug even if the user doesn't know exactly what caused the crash. This is, after all, the whole point of all that data that ABRT uploads. The maintainer we're talking about closed an ABRT bug with INSUFFICIENT_DATA seemingly without bothering to look at any of the ABRT data. Then when I added information to the defect about what caused that same crash for ME, he ignored it and did not reopen the bug. Even if you were right that I had reported bugs without providing reproduction steps, that would not justify the package maintainer treating me or any other user rudely and not even bothering to put a comment in the defect asking for the additional required information. Maintainers are expected to act like grown-ups and treat users, even clueless users, with respect. From BugStatusWorkFlow: "Bugs can be closed as INSUFFICIENT_DATA by a triager or maintainer if it seems impossible or very unlikely that the reporter will be willing or able to provide sufficient information." That is hardly a determination that can be made by the maintainer when he hasn't even asked the reporter for the missing information.Including the steps after the fact doesn't pardon you for the incorrect reporting to begin with. Oh, and there's this too: "The needinfo flag is added by bug triagers or maintainers when adequate information is missing to move the bug towards resolution." *That* is what the maintainer of a package is supposed to do when the reporter does not provide sufficient information. jik |
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
