All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Peter Krempa" <pkrempa@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template
Date: Thu, 3 Jun 2021 12:52:19 +0100	[thread overview]
Message-ID: <YLjCc37t9meGQZ1q@stefanha-x1.localdomain> (raw)
In-Reply-To: <YLie2HCFd5asHyga@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2742 bytes --]

On Thu, Jun 03, 2021 at 10:20:24AM +0100, Daniel P. Berrangé wrote:
> On Thu, Jun 03, 2021 at 09:45:43AM +0100, Stefan Hajnoczi wrote:
> > On Wed, Jun 02, 2021 at 08:11:28PM -0400, John Snow wrote:
> > > Based loosely on libvirt's template, written by Peter Krempa.
> > > 
> > > CC: Peter Krempa <pkrempa@redhat.com>
> > > Signed-off-by: John Snow <jsnow@redhat.com>
> > > ---
> > >  .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
> > >  1 file changed, 63 insertions(+)
> > >  create mode 100644 .gitlab/issue_templates/bug.md
> > > 
> > > diff --git a/.gitlab/issue_templates/bug.md b/.gitlab/issue_templates/bug.md
> > > new file mode 100644
> > > index 00000000000..9445777252b
> > > --- /dev/null
> > > +++ b/.gitlab/issue_templates/bug.md
> > > @@ -0,0 +1,63 @@
> > > +<!--
> > > +This is the upstream QEMU issue tracker.
> > > +
> > > +Before submitting a bug, please attempt to reproduce your problem using
> > > +the latest development version of QEMU, built from source. See
> > > +https://www.qemu.org/download/#source for instructions on how to do
> > > +this.
> > 
> > It's likely that those unfamiliar with QEMU, especially non-developers,
> > won't be able to do this:
> > 
> > The wording requires the reader to figure out that "latest development
> > version of QEMU" is none of the big 6.0.0, 5.2.0, etc download links at
> > the top of the page but the small text "The latest development happens
> > on the master branch" sentence below the fold. Then they need to look
> > around the page to find out how to download the master branch and build
> > from source.
> > 
> > I suggest referring directly to the build instructions instead of
> > requiring the reader to make several connections in order to do what
> > we're (indirectly) asking:
> > 
> >   Before submitting a bug, please attempt to reproduce the problem with
> >   the latest qemu.git master built from source. See the "To download and
> >   build QEMU from git" section at https://www.qemu.org/download/#source
> >   for instructions.
> 
> I do wonder if this will discourage people from submitting  a bug report,
> if they're unable to actually do this. We have a fairly frequent stream
> of users who seek help trying to build QEMU - usually they fail to even
> get the right depedancies installed.
> 
> Perhaps word it so it doesn't come across as such a strict sounding
> requirement ? I'm not entirely happy with the below text, but something
> more forgiving like:
> 
>    If you are able to, it will facilitate QEMU bug triage if an attempt
>    is made to reproduce the problem with the latest qemu.git master
>    built from source. ...etc..

Sounds good.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-06-03 11:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  0:11 [PATCH v3 0/2] Gitlab: Add issue templates John Snow
2021-06-03  0:11 ` [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template John Snow
2021-06-03  5:15   ` Thomas Huth
2021-06-03  7:26   ` Philippe Mathieu-Daudé
2021-06-03 19:11     ` John Snow
2021-06-03 20:35       ` Daniel P. Berrangé
2021-06-03  8:45   ` Stefan Hajnoczi
2021-06-03  9:20     ` Daniel P. Berrangé
2021-06-03 11:52       ` Stefan Hajnoczi [this message]
2021-06-03 14:12         ` John Snow
2021-06-03 14:44       ` John Snow
2021-06-03 14:57         ` Daniel P. Berrangé
2021-06-03  0:11 ` [PATCH v3 2/2] GitLab: Add "Feature Request" issue template John Snow
2021-06-03  5:16   ` Thomas Huth
2021-06-03  7:15 ` [PATCH v3 0/2] Gitlab: Add issue templates Philippe Mathieu-Daudé

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=YLjCc37t9meGQZ1q@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pkrempa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.