From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [warning] the bug queue has 89 bugs
Date: Fri, 27 Feb 2015 06:07:22 +0300 [thread overview]
Message-ID: <20150227060722.6cbf4f664743fd9b6325c36c@gentoo.org> (raw)
In-Reply-To: <20150226220004.05EB05818E@linuxized.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Thu, 26 Feb 2015 14:00:04 -0800 (PST) Alex Alexander wrote:
> Our bug queue has 89 bugs!
>
> If you have some spare time, please help assign/sort a few bugs.
>
> To view the bug queue, click here: http://bit.ly/m8PQS5
BTW, maybe this process can be partially automated? In most cases
we have to look for category/package in a bug title and add/cc
mails from metadata.xml to this bug. Of course, in some cases bug
may have references to several packages or no valid references at
all; false assignments are also possible as well as not properly
submitted bugs (e.g. missing build logs and so on) . But in general
such tool should reduce workload greatly.
Another approach will be to allow users to assign bugs themselves.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-27 3:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 22:00 [gentoo-dev] [warning] the bug queue has 89 bugs Alex Alexander
2015-02-27 3:07 ` Andrew Savchenko [this message]
2015-02-27 10:49 ` Diego Elio Pettenò
2015-02-27 17:03 ` [gentoo-dev] " Duncan
2015-03-13 19:50 ` Jeroen Roovers
-- strict thread matches above, loose matches on Subject: below --
2017-02-09 22:00 [gentoo-dev] " Alex Alexander
2017-01-23 22:00 Alex Alexander
2016-07-04 21:00 Alex Alexander
2015-05-01 21:00 Alex Alexander
2013-11-06 12:00 Alex Alexander
2013-11-06 16:08 ` Tom Wijsman
2013-11-06 16:17 ` Alex Alexander
2011-10-02 11:00 Alex Alexander
2011-07-01 11:00 Alex Alexander
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=20150227060722.6cbf4f664743fd9b6325c36c@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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