From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Alistair Francis" <alistair23@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Migrating to the gitlab issue tracker
Date: Mon, 9 Nov 2020 10:10:56 +0000 [thread overview]
Message-ID: <20201109101056.GC684242@redhat.com> (raw)
In-Reply-To: <CAFEAcA_dT_RQ8Pmk_S=zCSu1tUbptuP0+rtrsS55tEg+XD=S2Q@mail.gmail.com>
On Sun, Nov 08, 2020 at 11:58:28AM +0000, Peter Maydell wrote:
> On Sun, 8 Nov 2020 at 09:01, Thomas Huth <thuth@redhat.com> wrote:
> > I agree with Daniel. Please let's not clog the new bug tracker right from
> > the start with hundreds of bugs - that only makes it harder to focus on the
> > tickets that are really important. Let's use the migration instead to start
> > as clean as possible again.
>
> I really don't like doing this kind of thing. It basically
> tells bug reporters "we don't care about your reports".
> We ought to at least triage them. Certainly for arm a
> lot of the reports in LP are real bug reports which we
> shouldn't just drop on the floor.
Mostly it is just a reflection of the reality we find ourselves in where
we have more bug reports than we have willing maintainer time to investigate
and resolve. Regardless of whether the bug are open or closed, there are a
large number we clearly don't consider important, otherwise someone would
have already looked at them.
This isn't a comment on whether the bugs are valid or not, just on whether
the bugs look important/critical enough to be worth spending time on, and
unfortunately most come up short.
If we accept this, then I think bulk closing old bugs is a good solution.
It makes it clear to users sooner than the problem they face is unlikely
to be ever resolved, and so they can stop waiting in vain for something
that will never happen and focus on working around the problem they hit.
We will certainly close many valid bugs in doing this. Some of those may
in fact turn out to be things we will fix, or want to fix but that's OK.
We can still fix them even if the bug is closed. Or if we notice a bug
being closed that's important, we can re-open it.
IMHO on balance it is still better if we blindly auto-close the 261
expired bugs in Thomas' dashboard, and then manually re-open perhaps
15-20 that might have been valid, than to manually triage all 261 bugs.
This will leave more time to spend on the masses of other non-stale bugs
which are more likely to be useful to our current users.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-11-09 10:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 16:01 Migrating to the gitlab issue tracker John Snow
2020-10-29 16:30 ` Daniel P. Berrangé
2020-10-29 16:41 ` Cornelia Huck
2020-10-29 16:49 ` Alistair Francis
2020-10-29 17:12 ` John Snow
2020-10-29 17:36 ` Kashyap Chamarthy
2020-10-29 19:55 ` Thomas Huth
2020-10-29 20:27 ` John Snow
2020-10-30 9:23 ` Daniel P. Berrangé
2020-10-30 10:03 ` Peter Maydell
2020-10-30 10:10 ` Daniel P. Berrangé
2020-10-30 10:57 ` Peter Maydell
2020-11-05 0:06 ` John Snow
2020-11-05 6:14 ` Thomas Huth
2020-11-05 9:54 ` Daniel P. Berrangé
2020-11-05 15:44 ` John Snow
2020-11-05 15:50 ` Daniel P. Berrangé
2020-11-08 9:00 ` Thomas Huth
2020-11-08 11:58 ` Peter Maydell
2020-11-09 8:04 ` Thomas Huth
2020-11-09 10:10 ` Daniel P. Berrangé [this message]
2020-11-09 10:14 ` Peter Maydell
2021-01-21 10:57 ` Thomas Huth
2021-01-21 16:20 ` John Snow
2020-10-30 10:26 ` Alex Bennée
2020-10-30 12:53 ` John Snow
2020-11-08 8:57 ` Thomas Huth
2020-10-29 18:04 ` John Snow
2020-10-29 20:33 ` Cornelia Huck
2020-10-30 9:16 ` Stefan Hajnoczi
2020-10-30 15:39 ` John Snow
2020-11-02 13:57 ` Laszlo Ersek
2020-11-02 14:26 ` Daniel P. Berrangé
2020-11-02 14:42 ` Eric Blake
2020-11-04 17:10 ` Laszlo Ersek
2020-11-04 17:03 ` Laszlo Ersek
2020-11-04 17:19 ` Daniel P. Berrangé
2020-11-06 15:37 ` Laszlo Ersek
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=20201109101056.GC684242@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair23@gmail.com \
--cc=cohuck@redhat.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).