From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Thomas Huth <thuth@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [qemu-web PATCH] add Thomas's bug reporting dos and don'ts
Date: Wed, 26 Jul 2017 07:28:43 -0500 [thread overview]
Message-ID: <0faa2a79-fd07-f4e3-9237-563e9e8d277d@redhat.com> (raw)
In-Reply-To: <20170726121913.GJ7620@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
On 07/26/2017 07:19 AM, Daniel P. Berrange wrote:
> On Wed, Jul 26, 2017 at 01:57:35PM +0200, Thomas Huth wrote:
>> On 26.07.2017 13:44, Paolo Bonzini wrote:
>>> We don't want the page to become too long, but these are good suggestions.
>>>
>>> Also tone down the sentence about using the latest release or latest git
>>> tree, though we do prefer those.
>>
>> Well, sometimes people still report bugs against QEMU 2.1 or so ... so
>> I'd say everything that is older than the current version - 2 has a very
>> high chance to be ignored completely. So maybe we should ask people to
>> use at least one of the versions that is mentioned on the front-page of
>> www.qemu.org ?
>
> The biggest reason people would be using old versions of QEMU is if they
> are running a distro's build. Such people should really file bugs in
> their vendor's bug tracker, rather than against upstream directly.
>
> IOW, it would be worth having a bit of text on the bug reporting page
> to suggest people should preferrentially use their vendor's bug tracker,
> if they are using a 3rd party build of QEMU.
Which was what the patch included:
> -Bugs can be filed at our [bug tracker](https://bugs.launchpad.net/qemu/), which is hosted on Launchpad.
> +Bugs can be filed at our [bug tracker](https://bugs.launchpad.net/qemu/), which is hosted on Launchpad. If you've got a problem with how your Linux distribution packages QEMU, use the bug tracker from your distro instead.
Although maybe the wording can be improved to mention that ALL bugs
about qemu packaged downstream, and not just the packaging, should be
referred to the downstream vendor (the vendor may then forward the bugs
upstream).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-07-26 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 11:44 [Qemu-devel] [qemu-web PATCH] add Thomas's bug reporting dos and don'ts Paolo Bonzini
2017-07-26 11:52 ` Eric Blake
2017-07-26 11:52 ` Peter Maydell
2017-07-26 12:14 ` Paolo Bonzini
2017-07-26 11:57 ` Thomas Huth
2017-07-26 12:12 ` Paolo Bonzini
2017-07-26 12:19 ` Daniel P. Berrange
2017-07-26 12:28 ` Eric Blake [this message]
2017-07-26 12:30 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0faa2a79-fd07-f4e3-9237-563e9e8d277d@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).