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

Allan McRae allan at archlinux.org
Mon Feb 13 15:02:03 EST 2012

On 14/02/12 02:45, Florian Pritz wrote:
> 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.

I personally like keeping these bugs open.  Provided I make sure they
all have links to the upstream bug report, it means all my bugs to
follow are gathered in the one place.

So I say leave it to the maintainer to decide.


More information about the arch-dev-public mailing list