qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Peter Krempa" <pkrempa@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template
Date: Thu, 3 Jun 2021 09:26:22 +0200	[thread overview]
Message-ID: <b9166bbc-0201-af02-d54b-af4638525ceb@redhat.com> (raw)
In-Reply-To: <20210603001129.1319515-2-jsnow@redhat.com>

On 6/3/21 2:11 AM, 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.
> +
> +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.
> +
> +If this is a security issue, please consult
> +https://www.qemu.org/contribute/security-process/
> +-->
> +
> +## 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.)
> + - QEMU version: (e.g. `qemu-system-x86_64 --version`)

I haven't reviewed earlier version, but I wonder about the "build from
sources" use case (this is not a template for distributions but for the
mainstream project), so maybe add:

  ## Build environment (in case you built QEMU from source)
  - configure script command line: (e.g. ./configure --enable-nettle
--disable-glusterfs --disable-user)
  - configure script summary output

> + - QEMU command line:
> +   <!--
> +   Give the smallest, complete command line that exhibits the problem.
> +
> +   If you are using libvirt, virsh, or vmm, you can likely find the QEMU
> +   command line arguments in /var/log/libvirt/qemu/$GUEST.log.
> +   -->
> +   ```
> +   ./qemu-system-x86_64 -M q35 -m 4096 -enable-kvm -hda fedora32.qcow2
> +   ```
> +
> +## Emulated/Virtualized environment
> + - Operating system: (Windows 10 21H1, Fedora 34, etc.)
> + - OS/kernel version: (For POSIX guests, use `uname -a`.)
> + - Architecture: (x86, ARM, s390x, etc.)
> +
> +
> +## Description of problem
> +<!-- Describe the problem, including any error/crash messages seen. -->
> +
> +
> +## Steps to reproduce
> +1.
> +2.
> +3.
> +
> +
> +## Additional information
> +
> +<!--
> +Attach logs, stack traces, screenshots, etc. Compress the files if necessary.
> +If using libvirt, libvirt logs and XML domain information may be relevant.
> +-->
> +
> +<!--
> +The line below ensures that proper tags are added to the issue.
> +Please do not remove it.
> +-->
> +/label ~"kind::Bug"
> 



  parent reply	other threads:[~2021-06-03  7:27 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é [this message]
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
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=b9166bbc-0201-af02-d54b-af4638525ceb@redhat.com \
    --to=philmd@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=stefanha@redhat.com \
    --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).