[arch-dev-public] Handling of upstream bugs in our bug tracker

[Florian Pritz]

Hi,

We currently have around 70 open linux bugs, most of which we likely
won't fix ourselves. I know some of you think we should keep them open
for reference until upstream fixed the bug, but I think this just
clutters our bug tracker. Given the amount of duplicates I've seen, I
also doubt users use the search feature or google so they don't find to
reference bugs anyway.

Linux bugs are just an example, but there are certainly more and I think
we should just tell the reporter to go to upstream and close our bug. If
upstream is dead or doesn't have a mailing list/bug tracker, we can keep
the bug, but in that case we should think about dropping the package. If
it turns out to be a packaging bug we can still reopen it later.

-- 
Florian Pritz -- {flo,bluewind}@server-speed.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-dev-public/attachments/20120213/c39ba897/attachment.asc>