On 11/26/20 10:23 AM, Peter Krempa wrote:
Gitlab allows projects to define templates for filing issues [1].
Libvirt didn't have them yet. We can use them to encourage users to
file better bug reports and feature requests.
You can test-drive the proposed templates in my test repo:
https://gitlab.com/pipo.sk/test/-/issues/new?issue%5Bassignee_id%5D=&...
Any suggestions on how to improve them further are very welcome.
They look good. Couple of suggestions:
- in the bug-qemu template: either add a 'host OS' or a 'host kernel'
field in the 'versions and environment' section. Having to know the
kernel version the user is rocking to determine the cause of a QEMU bug
is not uncommon. Most of the cases knowing the host OS suffices to
get the kernel version, so any of those works;
- for all templates: if the bug happens in an non-x86 arch we want to know
about it. I'd say that a text in the "Versions and environment" section
with something akin of:
"If the bug happens in an architecture other than x86_64, please inform it
below"
will not annoy x86_64 users while also contemplating that other archs are
also supported.
Thanks,
DHB
[1]
https://docs.gitlab.com/ee/user/project/description_templates.html
Peter Krempa (3):
gitlab: Add issue template for reporting a generic bug
gitlab: Add issue template for a feature request
gitlab: Add issue template for filing a bug in libvirt's qemu driver
.gitlab/issue_templates/bug-qemu.md | 56 +++++++++++++++++++++++++++++
.gitlab/issue_templates/bug.md | 55 ++++++++++++++++++++++++++++
.gitlab/issue_templates/feature.md | 26 ++++++++++++++
3 files changed, 137 insertions(+)
create mode 100644 .gitlab/issue_templates/bug-qemu.md
create mode 100644 .gitlab/issue_templates/bug.md
create mode 100644 .gitlab/issue_templates/feature.md