On Fri, Sep 16, 2016 at 09:42:07AM -0700, stan wrote: I really like Stan's idea. The root of this problem lies in the historical fact that most packages just did not have issue tracking, so Fedora and Bugzilla stepped in to orchestrate it on a distribution level. This works splendidly, if God's willing and creeks don't rise: I have a personal experience of submitting a bug, then a fix, and seeing a fixed package enter the main distribution repository within a week or so, fixing the problem for the entire world including myself. That's why I still believe that Bugzilla is the default place to report the issues, followed by coordination with the upstream, of course.Wouldn't it make more sense to have a way for package maintainers to decide if a bug was local or upstream, and a button they could push to automatically send it upstream? On the other hand, if the submitter and/or the Fedora packager can't deliver the fix, the issues will linger; in that case upstream is really where they should migrate to. On 09/16/2016 01:19 PM, Zbigniew Jędrzejewski-Szmek wrote: Automatically? If I receive a bug upstream, I want to receive it without the distribution's embellishments: I want to know what *upstream* version of the software was used, how I can reproduce the bug using generic installation from sources, and not using the distro package, etc. Also, I don't want to read the full history on the distribution bugtracker, I want to see a concise summary of findings. I want to see an explanation why the bug is an upstream bug, not a distro-specific thing. The person who is forwarding bugs has to all of this by hand, and doing this automatically is infeasible.The better is the enemy of the good. You're right that it would be ideal if upstream got a cleaned up report along the lines you suggested, but the automatic upstream report could essentially link to the Bugzilla entry, which hopefully contains basic setup and reproducibility information---at the very least it registers the issue and establishes communication channel between the upstream developer and Fedora-based reporter. When I run into issues, I tend to follow the original Bugzilla entry with a second comment that at least provides a stack dump showing the crash environment (e.g. https://bugzilla.redhat.com/show_bug.cgi?id=1359395 ); abrt does this automatically. I believe this is helpful to the upstream developers, as they sometimes explicitly confirm. The downside of course is we don't want to firehose upstream with an endless stream of reports, but Stan's idea involves a manual step and therefore should keep that under control. |
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
