From: Thomas Huth <thuth@redhat.com>
To: John Snow <jsnow@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: Gitlab Issue Tracker - Proposed Workflow
Date: Wed, 5 May 2021 10:49:32 +0200 [thread overview]
Message-ID: <c278c5cb-f9d2-081f-3451-9ae38cd33bcf@redhat.com> (raw)
In-Reply-To: <166fe72a-c209-fd08-5f31-db15e4f3a8b9@redhat.com>
On 04/05/2021 20.33, John Snow wrote:
[...]
> - Gitlab will automatically close issues that reference the gitlab issue
> tracker from the commit message, but it won't apply the "Merged" label, so
> it's at risk of falling out of sync.
>
> Closed issues retain their "Workflow::" labels, but won't show up in the
> issue search by default unless you ask to include closed issues as well.
>
> I think we can likely just drop this label, and have bugs go directly from
> whatever state they're in to "Closed". The issue board will look cleaner and
> there's less custodial work for maintainers.
>
> - Similarly to the above concern, "Released" is extra paperwork for us to
> maintain.
Others replied already, but I wanted to add some of my personal views here,
too: Hunting down the issues to close them after we published a new release
was a very tedious and time consuming task. Most people simply forget to
close tickets that they've opened or solved. So I was always doing most of
the dirty work here, using a script to hunt down bug URLs in commit messages
and looking for bugs that were stuck in "Fix committed" state - but
honestly, I feel like I've also got better things to do in my spare time.
So from my point of view: Let's close bugs automatically with the
"Resolves:" keyword in the commit messages. I think users are smart enough
to realize that the fix will then be available with the next release. So we
really don't need a "Merged" and "Release" state anymore and I vote for
dropping them.
Thomas
next prev parent reply other threads:[~2021-05-05 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 18:33 Gitlab Issue Tracker - Proposed Workflow John Snow
2021-05-04 18:52 ` Daniel P. Berrangé
2021-05-04 21:33 ` John Snow
2021-05-04 20:24 ` Peter Maydell
2021-05-04 21:39 ` John Snow
2021-05-05 8:49 ` Thomas Huth [this message]
2021-05-05 16:18 ` 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=c278c5cb-f9d2-081f-3451-9ae38cd33bcf@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).