All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: GitLab issue tracker at inbox 0 (for unlabelled issues ;-)
Date: Fri, 22 May 2026 17:32:30 +0100	[thread overview]
Message-ID: <87zf1rl80x.fsf@draig.linaro.org> (raw)


Hi,

I've finally finished working our way through the backlog of un-tagged
issues in the tracker. This has been done with an AI agent following the
"qemu-issue-triage" skill from my recent agent skills series:

  Message-ID: <20260515163055.1792262-1-alex.bennee@linaro.org>
  Date: Fri, 15 May 2026 17:30:43 +0100
  Subject: [RFC PATCH v3 00/11] AGENTS.md and associated skills

I've been sampling the results as I've gone along and am pretty happy
with how the agents have performed. If you do find the agent has gone
off on one can you tag me or the agent in a comment on the bug in
question and we can try and improve the triage skills.

We currently have 1271 open issues in the tracker. Of those:

  124 are tagged Needs Info
  50 have patches linked
  151 are Feature Requests
  71 have TestCases attached
  16 are identified as Regressions
  ...
  and many more

A lot of the older issues ended up with Needs Info because they are
reported against older versions of QEMU outside the support range.
Daniel did suggest maybe we should think about having
"triage::outdated-version" and "triage::distro-package" states. However
maybe it is enough to stick with Needs Info and just auto expire bugs
that have stayed in that state for long enough (6-12 months?).

Of course triaging is only the first step, I encourage maintainers to go
check their labels and see if any bugs have been missed. I have found
adding tabs to the Work Items view with interesting sets of labels has
helped in sorting through the noise.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


                 reply	other threads:[~2026-05-22 16:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87zf1rl80x.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.