On Wed, 12 Jan 2011 13:27:23 +0000 (UTC), Sune Vuorela
<nospam@vuorela.dk> wrote:
>On 2011-01-11, brian m. carlson <sandals@crustytoothpaste.net> wrote:
>> I've noticed a trend lately that I am often asked to forward the bugs I
>> report to the Debian BTS upstream, either by the maintainers or
>> automatically by a bug script. I believe, and I continue to believe,
>
>I have considered to take this one step further. Close bugs reported in
>Debian BTS with a severity of important or less that is a bug that
>should primarily be fixed upstream.

This attitute of the Qt/KDE team has stopped me from repoting bugs in
KDE packages completely.

>Currently, the debian Qt/KDE team has around 800 open, non-forwarded
>bugs reported against their packages. I would guess that maybe 20 of
>them is packaging issues. But we can't find them.

Just usertag the non-packaging issues and filter them out in your
queries.

>The rest of the bugs (780 open-non forwarded (and 300 forwarded)) is
>pure upstream issues.

They're still issues present in current Debian.

Greetings
Marc
--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: E1Pe94q-0005Yg-Pj@swivel.zugschlus.de">http://lists.debian.org/E1Pe94q-0005Yg-Pj@swivel.zugschlus.de

Hi

After reading this thread, I've got a strange thought.


So teams maintaining important projects in Debian can't handle the load
caused by bug report stream.

Large presentange of bugs actually as upstream bugs. If so, upstream should
be interested in that information non less than in any other information
about bugs in their software.

Also, upstream should be interested in having their software in
distributions in as good shape as possible - distributions are *the*
channel how most users get upstream's software.

Then, maybe explicitly request upstream - at appropriate forums and in
appropriate polite wording - to help debian team(s) to handle the bug
report stream?

Sure this will cause requests to put bug report into upstream trackers.
Situation with this has been described within this thread, and this
information - in brief form - could be presented to upstreams.

I think this method could attact additional resource into solving the
problem being discussed in this thread.


Just wanted to share my thought.

Nikita

On Wed, Jan 19, 2011 at 9:27 AM, Nikita V. Youshchenko <yoush@debian.org> wrote:
> Then, maybe explicitly request upstream - at appropriate forums and in
> appropriate polite wording - to help debian team(s) to handle the bug
> report stream?

I think upstream has the same problem in some cases: too many bug reports.
So I doubt upstream has time to look at yet another bug tracker.


--
Olaf


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTinq4teDJy6JCw_M0dMjxKz8pvtCydoEOVpErBA1@mail .gmail.com">http://lists.debian.org/AANLkTinq4teDJy6JCw_M0dMjxKz8pvtCydoEOVpErBA1@mail .gmail.com

Hi, Olaf:

On Thursday 20 January 2011 09:51:27 Olaf van der Spek wrote:
> On Wed, Jan 19, 2011 at 9:27 AM, Nikita V. Youshchenko <yoush@debian.org>
wrote:
> > Then, maybe explicitly request upstream - at appropriate forums and in
> > appropriate polite wording - to help debian team(s) to handle the bug
> > report stream?
>
> I think upstream has the same problem in some cases: too many bug reports.

That I had always problems to believe. I think that usually translates
to "too many bugs".


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201101201132.38570.jesus.navarro@undominio.net">ht tp://lists.debian.org/201101201132.38570.jesus.navarro@undominio.net