From: John Snow <jsnow@redhat.com>
To: 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 v2 0/2] Gitlab: Add issue templates
Date: Thu, 27 May 2021 15:55:38 -0400 [thread overview]
Message-ID: <7318536e-2199-5b8c-61bc-d5aff09c111d@redhat.com> (raw)
In-Reply-To: <20210521173818.255817-1-jsnow@redhat.com>
ping -- Any objections?
On 5/21/21 1:38 PM, John Snow wrote:
> Add "Bug" and "Feature Request" templates to the Gitlab interface to
> help improve the quality of newly reported issues.
>
> To see what this looks like, I've temporarily allowed my Gitlab fork to
> diverge with these files merged. See my fork's "new issue" page to see
> it in action: https://gitlab.com/jsnow/qemu/-/issues/new?issue
>
> These patches do not add a "default" template, the user still has to
> select one from the list. I recommend that someone with permissions
> updates the default template:
>
> 1. https://gitlab.com/qemu-project/qemu/edit
> 2. ctrl+f "Default description template for issues"
> 3. Update the default to the (suggested) below:
>
> ```
> <!-- Select "Type: Issue" and choose one of the Description templates above. -->
> ```
>
> We can use this cover letter to discuss/review the wording on that
> default template which exists outside of repository data.
>
> --js
>
> V2:
> - Updated both templates based on feedback from Peter, Daniel, and
> Thomas.
>
> John Snow (2):
> GitLab: Add "Bug" issue reporting template
> GitLab: Add "Feature Request" issue template.
>
> .gitlab/issue_templates/bug.md | 61 ++++++++++++++++++++++
> .gitlab/issue_templates/feature_request.md | 32 ++++++++++++
> 2 files changed, 93 insertions(+)
> create mode 100644 .gitlab/issue_templates/bug.md
> create mode 100644 .gitlab/issue_templates/feature_request.md
>
prev parent reply other threads:[~2021-05-27 19:56 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
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 ` John Snow [this message]
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=7318536e-2199-5b8c-61bc-d5aff09c111d@redhat.com \
--to=jsnow@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@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).