qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: 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 13:19:13 +0100	[thread overview]
Message-ID: <20170726121913.GJ7620@redhat.com> (raw)
In-Reply-To: <9e187829-fc01-8140-22f0-7cf67fc294bd@redhat.com>

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.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  parent reply	other threads:[~2017-07-26 12:19 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 [this message]
2017-07-26 12:28     ` Eric Blake
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=20170726121913.GJ7620@redhat.com \
    --to=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).