Re: Reporting bugs upstream

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxx> 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. There isnt a universal method of doing it
automatically. In some cases XML RPC does help.

Rahul

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux