reporting bugs

Reindl Harald h.reindl at thelounge.net
Sat Nov 5 19:32:13 UTC 2011



Am 05.11.2011 20:18, schrieb Kevin Kofler:
> Reindl Harald wrote:
>> yes - because most maintainers are having bugzilla-accounts upstream
>> and reading the uptream-mailing-lists and are much more cooperative as
>> the KDE SIG, especially Kevin Kofler
> 
> Yes, we have Bugzilla accounts upstream. But as I explained, upstream wants 
> to talk to the actual person experiencing the bug, not to a middleman. Plus, 
> we get many bug reports, it'd be very time-consuming for us to forward them 
> all upstream, whereas you as a user (hopefully) have much fewer bug reports 
> to deal with. It's not our job to play "stille Post" for you (a game which 
> necessarily loses information with every middleman you introduce).

most maintainers see this different and only the fact that fedora-packages
are mostly patched makes it not useful throw all upstream first

the sense of a distribution for users is have a centralized source for
packages and problems, if your standard-answer is "report upstream"
you are damaging the benefits of a distribution for users

i have filled MANY bugreports in the last years and really often
some hours later there was a new version on koji, maintainer aksed
to try this, confirmed as "works now" and the maintainer submitted
his patch upstream and included it as long iht was not fixed upstream
in the fedora-packages - this way users start to love fedora, the
maintainers and all peopole from users, maintainers to upstream
developers are happy - your way of handling bugreports is the
exactly oppiste of this

>> if you than report a bundle of new introduced bugs upstream you are
>> told in the case of KDE yous hould file for every piece a seperate
>> bugreport

https://bugs.kde.org/show_bug.cgi?id=236025 is the best example that
this is not useful - in this case some random guy decided to replace
a whole io-subsytem from scratch without any knowledge what he is
doing for POSSIBLE get better performance sometimes later which
is not true in exactly this case because the limit is the network
and not the kio-slave

after such a useless, not needed replacement force users open
a bunch of bugreports instead revert the whole changes and
release them if they are finished and useable is the wrong way

anyways: fact is that if you punsih users how to report bugs in
such ways the result will be for MANY of them stop reporting bugs


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20111105/d368d7dd/attachment.bin 


More information about the devel mailing list