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

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

On Fri, May 21, 2021 at 01:38:17PM -0400, John Snow wrote:
> diff --git a/.gitlab/issue_templates/bug.md b/.gitlab/issue_templates/bug.md
> new file mode 100644
> index 00000000000..67a02a3ffcf
> --- /dev/null
> +++ b/.gitlab/issue_templates/bug.md
> @@ -0,0 +1,61 @@
> +<!--
> +This is the upstream QEMU issue tracker.
> +
> +Before submitting a bug, please attempt to reproduce your problem using
> +the latest development version of QEMU obtained from
> +https://gitlab.com/qemu-project/qemu/.

Please be specific about what "latest development version" means. I
guess it means qemu.git/master?

If we are asking them to build QEMU then it would be nice to include a
link with instructions on how to build from source.

> +
> +QEMU generally supports the last two releases advertised via
> +https://www.qemu.org/. Problems with distro-packaged versions of QEMU
> +older than this should be reported to the distribution instead.
> +
> +See https://www.qemu.org/contribute/report-a-bug/ for guidance.
> +-->
> +
> +## Host environment
> + - Operating system: (Windows 10 21H1, Fedora 34, etc.)
> + - OS/kernel version: (For POSIX hosts, use `uname -a`)
> + - Architecture: (x86, ARM, s390x, etc.)
> + - QEMU flavor: (qemu-system-x86_64, qemu-aarch64, qemu-img, etc.)

Is this necessary since we ask for the command-line below?

> +<!--
> +Attach logs, stack traces, screenshots, etc. Compress the files if necessary.
> +If using libvirt, libvirt logs and XML domain information may be relevant.
> +
> +See https://qemu-project.gitlab.io/qemu/devel/tracing.html on how to
> +configure additional QEMU logging.

This sentence can be removed. Tracing is mostly for developers and
requires knowledge of the source code. People who can use tracing
already know about it and for the rest it doesn't count as "additional
QEMU logging" because they won't be able to use it effectively.

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

  reply	other threads:[~2021-06-02  9:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 17:38 [PATCH v2 0/2] Gitlab: Add issue templates John Snow
2021-05-21 17:38 ` [PATCH v2 1/2] GitLab: Add "Bug" issue reporting template John Snow
2021-06-02  9:22   ` Stefan Hajnoczi [this message]
2021-06-02 16:09     ` John Snow
2021-06-03  8:43       ` Stefan Hajnoczi
2021-06-03 13:42         ` John Snow
2021-05-21 17:38 ` [PATCH v2 2/2] GitLab: Add "Feature Request" issue template John Snow
2021-06-02  9:25   ` Stefan Hajnoczi
2021-05-27 19:55 ` [PATCH v2 0/2] Gitlab: Add issue templates John Snow

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=YLdN4OcxSD0fJOvD@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.