Re: An interesting read when discussing what to do about our bugs...

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

 



On Sat, 2008-01-19 at 20:36 -0900, Jeff Spaleta wrote:
> On Jan 19, 2008 9:23 AM, nodata <lsof@xxxxxxxxxxxx> wrote:
> > I'm talking about closing the bug and telling the reporter to report
> > upstream, i.e. "go away".
> 
> 
> As a package maintainer, what would you like me to do in situations
> where I need the reporter to talk to upstream?
A reporter should never be supposed to talk upstream, because he is
reporting an issue a problem with the product (your package) you are
supposed to be responsible for, not against the product an upstream
ships to you (the source tarball).

>   Should I just pat you
> on the head and promise to fix it, even though I can't?
What prevents you from simply telling the truth?

>   If I can't
> even reproduce the problem with my hardware, or its a feature request
> that needs to be discussed as part of an upstream development what
> exactly are the better choices than encouraging you to take your case
> to upstream?
Communicate such issues upstream and provide upstream a link to the
original issue, such they can investigate?

Ralf



-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux