Re: Mantis package bombs

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

 



Charles Curley wrote:
> On Sun, Aug 26, 2007 at 02:35:01PM -0400, Todd Zullinger wrote:
>> Perhaps it doesn't end with an updated package for the version you
>> reported the problem in, but it often means that the bug is fixed
>> so future version won't have the same problem.
> 
> Then the maintainer should close the report and specify the
> resolution. That way the reporter knows what's happened. If Aaron's
> going to go to the effort of preparing a good bug report, answering
> questions, performing experiments, etc. he at least deserves that
> courtesy.

I don't know the details of the reports Aaron was talking about.  He
did say that there was a lengthy exchange asking for info, which leads
me to believe that the maintainer tried to get the needed info.

But yes, I agree that bug reports should be acknowledged and closed
with some reason, even it's "can't reproduce" or something.

> You and Rahul seem to want to make things as easy as possible for
> the maintainers. I think that's a fine idea. But it's a two way
> street: the maintainers can acknowledged reports, work with the
> reporters, and resolve the bugs. A "Won't fix" with an explanation
> of why is better than leaving it hanging.

Of course.  I hope I didn't give the impression that reports should be
ignored.  What I do think it worth noting is the sheer number of
reports and the limit on hours per day.  Most maintainers aren't paid
to work on Fedora packages, so it seems quite reasonable to expect
that a user wanting a bug fixed be patient and understanding if their
bug doesn't get the attention they would like.

I only recently started to maintain a few packages so I don't have
piles of bug reports to deal with as some maintainers do.  I certainly
intend to reply to every bug report that is filed on any of my
packages, but I know that other maintainers with heavier workloads may
not be able to do that.  What can really help in those cases are
volunteers to do some triaging of bugs to weed out duplicates and ask
for more info from reports that lack enough detail to enable proper
debugging[1].

Basically, since this is a mostly volunteer effort, I get a little
defensive when anyone has too many expectations from the volunteers.
(I'm not saying that you do, so please don't take that personally. :)

[1] http://fedoraproject.org/wiki/BugZappers

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Things in our country run in spite of government, not by aid of it.
    -- Will Rogers

Attachment: pgpwOUHwlx6c0.pgp
Description: PGP signature

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[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