Re: Maintainer Responsibilities

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

 



2009/6/4 Kevin Kofler <kevin.kofler@xxxxxxxxx>:
> Michal Hlavinka wrote:
>> Yes, but how will you notice reporter needs (your) help if bug is closed
>> upstream?
>
> By CCing ourselves on the upstream bug when we close ours.
>
>        Kevin Kofler

Speaking as a semi-frequent reporter of Fedora KDE bugs, I can say
that the process works pretty well for me. Of course, I'm probably
somewhat more engaged in the process than average (e.g., I maintain a
few packages myself, and I've had an account at bugs.kde.org for
years). I do occasionally wish that I didn't have to do the upstream
report myself, but I can see the reasons for it.

MEF

-- 
Mary Ellen Foster  --  http://homepages.inf.ed.ac.uk/mef/
ICCS, School of Informatics, University of Edinburgh

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

-- 
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