Reporting bugs upstream

nodata fedora at nodata.co.uk
Tue May 30 13:07:17 UTC 2006


> On Tue, 2006-05-30 at 15:01 +0200, nodata wrote:
>> > On Tue, 2006-05-30 at 08:47 -0400, Horst von Brand wrote:
>> >> Michael Schwendt <fedora at wir-sind-cool.org> wrote:
>> >
>> >> > As a user, being confronted with "just another feature-overloaded
>> bug
>> >> > tracker" which contains many new and poorly named and
>> insufficiently
>> >> > described "products" and "components" and hundreds of open bug
>> >> reports, it
>> >> > is a very frustrating experience to spend time on _trying_ to help
>> by
>> >> > reporting something upstream only to learn that the report is
>> ignored
>> >> or
>> >> > closed as duplicate or closed as NOTOURBUG or not been looked at
>> for
>> >> > many months.
>> >>
>> >> Why not adopt some packages, and help out by keeping an eye on
>> bugzilla
>> >> for
>> >> them, trying to reproduce bugs, and kick them upstream as needed?
>> That
>> >> way
>> >> you don't have to learn about many upstream bug trackers, just a few.
>> >> --
>> >
>> > If anyone is interested in that,
>> > http://fedoraproject.org/wiki/BugZappers
>> >
>> > Rahul
>>
>> Isn't this a workaround for bugzilla lacking an easy way to move bugs
>> upstream? Wasn't the XML RPC interface meant to solve this?
>
> Upstream projects use different versions of bugzilla and various other
> bug tracking systems.

So if upstream uses bugzilla (like kernel and Gnome do), is this possible?

> There isnt a universal method of doing it
> automatically. In some cases XML RPC does help.
>
> Rahul

So I guess this is being worked on?




More information about the fedora-devel-list mailing list