Re: [PATCH v2 1/2] GitLab: Add "Bug" issue reporting template

[Stefan Hajnoczi]

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.

signature.asc
Description: PGP signature