Bug 189813
Summary: | Extend RHAT Bugzilla to Upstream Projects | ||
---|---|---|---|
Product: | [Community] Bugzilla | Reporter: | Andy Green <andy> |
Component: | Bugzilla General | Assignee: | Jeff Fearn 🐞 <jfearn> |
Status: | CLOSED WONTFIX | QA Contact: | Kevin Baker <kbaker> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | devel | CC: | aleksey, chkr, cra, ineilsen, rdieter, scottt.tw, tromey, tuju |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-21 06:54:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 452962 | ||
Bug Blocks: |
Description
Andy Green
2006-04-24 20:31:22 UTC
IMO, it's OK to file the bug(s) in *both* places, and mention upstream reports in comments here or add a link to it in the "External Bugzilla References" section. Either way, I doubt this can truly be considerred a bug in bugzilla (as it is currently submitted). I couldn't find how to mark it as an RFE, which is what it actually is.
> IMO, it's OK to file the bug(s) in *both* places, and mention upstream reports
> in comments here or add a link to it in the "External Bugzilla References"
> section.
Yes it is OK. Just filing upstream is okay, but that is not the problem being
addressed by the suggestion, which involves user perception of abandonment and
shoulder-shrugging by Fedora. The concept is to allow the user to feel that he
still reports inside the Fedora distro, while binding upstream to the report in
a single action somehow.
Maybe to turn it around another way, when filing a bug you select the package
first, and you are redirected right then to a Bugzilla -- which may be a slice
of the RHAT one -- most appropriate for that project. So in that concept all
kernel-related bugs go on the kernel.org Bugzilla, tagged as coming from Fedora.
The Fedora responsibles are assigned and cc'd as before. Likewise if SuSE have
the same system then SuSE-user kernel bugs come to the same place, in front of
the kernel devs. It would cause politcal problems from issues coming out of
vendor patches, but if Bugzilla allowed to filter on bug report source people
who hated that could just not see those reports.
One thing that would convenient is to have a "report upstream" button, to automatically create a bug report in the upstream bugzilla that mirrors the fedora bug. Ideally this would set things up so that upstream changes are noted in the fedora bugzilla. Sounds like a great solution. Being able to connect the bug to the upstream Bugzilla -- if there is one -- manually would avoid burdening the up upstream folks with distro-specific problem noise. Ubuntu bugzilla already seems to grok bugzilla.gnome.org. I don't think b.g.o knows anything about ubuntu, but the logic is sufficient for a downstream bug to be able to report the current status of the connected upstream bug. See, for example: https://launchpad.net/distros/ubuntu/+source/gnome-pilot/+bug/25653 Some old notes are here http://article.gmane.org/gmane.linux.redhat.fedora.devel/79936 and http://article.gmane.org/gmane.linux.redhat.fedora.devel/98332 (In reply to comment #3) > One thing that would convenient is to have a "report upstream" button, > to automatically create a bug report in the upstream bugzilla that mirrors > the fedora bug. Ideally this would set things up so that upstream changes > are noted in the fedora bugzilla. Especially when in most cases that would appear to be DUPLICATE, the upstream should be able to somehow signal the bug id change back to downstream so that the referring bug id would be updated. related bug 452962 Adding upstream bug reference. (In reply to comment #3) > One thing that would convenient is to have a "report upstream" button, > to automatically create a bug report in the upstream bugzilla that mirrors > the fedora bug. Ideally this would set things up so that upstream changes > are noted in the fedora bugzilla. Primitive version of this (just prefills upstream enter_bug.cgi form with the content of the current bug) is already implemented in bugzilla-triage-scripts (https://fedorahosted.org/bugzilla-triage-scripts/) for further details ask me (mcepl on Freenode). As part of the recent Bugzilla 4.2 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team. As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team. Closing inactive bugs are part of Bugzilla cleanup. |