public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: x11 <x11@gentoo.org>
Subject: [gentoo-dev] Better way to direct upstream bugs upstream?
Date: Sat, 29 Aug 2015 12:53:53 -0700	[thread overview]
Message-ID: <CAEdQ38F0y76kHiaZnQBYBmBVGcmekr1t7X3ZKgmJ6jec9w-tXg@mail.gmail.com> (raw)

In April I closed out ~100 bugs assigned to x11@ that the X11 team
never had any realistic ability to fix ourselves (see most bugs about
x11-drivers/ati-drivers). Most of these were fleeting driver bugs
affecting a particular piece of hardware and a (often now old)
particular version of the driver -- now long obsolete but still
cluttering our bugzilla and making triaging actually solvable bugs
more difficult.

We often direct reporters to file bugs upstream (being a middle-man
for a driver bug is extremely inefficient), but even when that happens
the Gentoo bug remains open, often long after the upstream bug is
fixed and closed.

Worse, users sometimes file bugs in our bugzilla that we don't have
time to respond to for a while during which time they're waiting on
people without the ability to help them.

Is there a better way of directing reporters to file bugs upstream? Of
course it's not always clear whether a bug is an ebuild bug or
something easily patched in Gentoo vs a driver bug that requires an
upstream developer...

Maybe some text on https://bugs.gentoo.org/enter_bug.cgi asking users
to direct bug reports upstream under some to-be-decided-upon
circumstances?


             reply	other threads:[~2015-08-29 19:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-29 19:53 Matt Turner [this message]
2015-08-30  7:03 ` [gentoo-dev] Better way to direct upstream bugs upstream? Kent Fredric
2015-08-30  7:20   ` Daniel Campbell
2015-08-30  7:54     ` Kent Fredric
2015-08-30  7:59       ` Daniel Campbell
2015-08-30  9:37   ` [gentoo-dev] " Duncan
2015-08-30 10:02     ` Kent Fredric
2015-09-02 19:17       ` Paweł Hajdan, Jr.
2015-09-03  9:32         ` Jason Zaman
2015-09-03 11:28         ` Kent Fredric
2015-09-03 20:16           ` Andrew Udvare
2015-09-07 19:51             ` Paweł Hajdan, Jr.
2015-09-07 23:47           ` Alec Warner
2015-08-30 12:15   ` [gentoo-dev] " Peter Stuge
2015-08-30 12:38     ` Kent Fredric
2015-08-30 17:59 ` [gentoo-dev] " Chí-Thanh Christopher Nguyễn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEdQ38F0y76kHiaZnQBYBmBVGcmekr1t7X3ZKgmJ6jec9w-tXg@mail.gmail.com \
    --to=mattst88@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=x11@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox