Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Adam Williamson <awilliam <at> redhat.com>
Subject: Re: Moving away from reporting to RH bugzilla and adopting pure upstream reporting mantra.
Newsgroups: gmane.linux.redhat.fedora.testers
Date: Wednesday 25th September 2013 02:31:04 UTC (over 3 years ago)
On Mon, 2013-09-23 at 21:49 +0000, "J├│hann B. Gu├░mundsson" wrote:
> Greetings you all
> 
> After bit of irc discussion there is a compelling reason to move 
> entirely away from Red Hat bugzilla as well as away from concept of 
> hosting our own.
> 
> Now it pretty much boils down to this.
> 
> 1. Generic attitude of many maintainers is that reports either go to the 
> correct place ( upstream ) or they get their bugzilla ignored.
> 2. More often than not downstream maintainer as in packager does not 
> know the code at all so filling the bug downstream makes no sense since 
> it brings just unnecessary latency to the process.
> 3. Hosting our own bugzilla cost resources and does not solve 1. or 2.
> 
> I personally for many years have argued against this since to an 
> reporter it might mean having thousand of accounts  but given that we 
> are going through new fase and the times are changing in the linux eco 
> system I would like to get your opinion about we stop reporting 
> altogether in Red Hat bugzilla and report only directly upstream as in 
> kernel bugs to the kernel community, Gnome bugs to theirs, KDE to their 
> etc.
> 
> The obvious benefit of doing this is that our bugs might actually get 
> look at,dealt with as well as all that being done in a shorter time
frame.
> 
> Thoughts and comment.

Well, that's going a bit far.

I don't know, none of this really seems like news to me. Whenever I'm
about to file a bug, I ask myself if it's more appropriate to file it
upstream or downstream, and then file it at the appropriate place.
Neither filing all bugs upstream or filing all bugs downstream is the
best way to go about things. As others have pointed out, we really need
a Fedora bug tracker for bugs that really are bugs in *Fedora* -
packaging bugs, bugs in patches we carry, 'this package needs updating'
bugs - and for various tracking purposes (release blockers, mass
rebuilds...)
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net



-- 
test mailing list
[email protected]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
 
CD: 3ms