Re: Bug triage resulting in no fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bruno Wolff III wrote:
> On Mon, Jan 18, 2010 at 10:35:11 -0500,
>   Bill Davidsen <davidsen@xxxxxxx> wrote:
>   
>> I note that bugs are being marked as duplicates without regard to 
>> anything but age. This results in blocked bugs never getting fixed:
>>   abrt reports a bug, like crashes in metacity
>>   bug is reassigned to pulseaudio
>>   PA asks for glibc version
>>   bug is marked as NEEDINFO - and if the submitter doesn't respond there 
>> it dies
>>   abrt reports a bug from another submitter
>>   2nd report gets request for glibc version
>>   2nd submitter provides same
>>   triage comes along and marks 2nd bug DUP of 1st and closes
>>   now both reports, and any subsequest reports are hung on the 1st
>>     
>
> If the first bug was closed because of a lack of response to needinfo,
> then when the dup was assigned to it, it should have been reopened. And
> if it was clear to the triager that the same infomation was going to be
> needed by the new reporter, a needinfo request to them should have been made.
>
>   
I don't know how to put this any better, the 1st bug is in NEEDINFO, the 
2nd bug actually has the info, and what happens is that the 2nd bug is 
marked DUPLICATE, while the 1st remains NEEDINFO. New bugs with active 
reporters will be marked DUPLICATE, no progress is made.
>> Suggestion:
>>   do not mark anything as a dup of a bug which is in NEEDINFO status
>>     
>
> This isn't a good solution to the problem. You really want one bug for each
> problem.
>
>   
And currently you can have that one bug blocked until the next version 
comes out and the bug is closed for lack of response. As long as the 
oldest bug is NEEDINFO having two bugs is better than one which will not 
move forward to a solution.

I agree my proposed solution is not optimal, but having a path which 
leads to a bug not only not moving but blocking all other reporters is a 
sure path to not getting bugs fixed. If a NEEDINFO hasn't been answered 
in a few days, the reporter is unlikely to move forward.

Anyway, I made the suggestion, laptops are not productive in text mode only.

-- 
Bill Davidsen <davidsen@xxxxxxx>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux