public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matti Bickel <mabi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Is Gentoo dying?
Date: Sat, 03 Apr 2010 18:24:48 +0200	[thread overview]
Message-ID: <4BB76BD0.4080607@gentoo.org> (raw)
In-Reply-To: <n2jb41005391004030903n7364ad84i2f9f5cb9e129c352@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

Alec Warner wrote:
> The above are all pretty easy to do with the data in the tree.  Some
> other useful ideas might be:
>  - compare open bugs for the package, when was the last bug for a
> package closed (bugs data kinda sucks for this)

An additional search: last touched by assignee between never and now-30
days.

I also just discovered that awesome query interface our bugzilla has.

Can we publish a data set query where new bugs are plotted against
closed bugs (maybe add already open bugs) for each herd? I'll try to
come up with a query if no one else is faster with this.

If the difference between new and closed bugs in a 30 days time period
is over a given threshold (say 15% of the current open bugs), this might
be a herd that needs help.

Maybe we can come up with more insightful bugzie searches. And maybe
something like that exists already and i've failed finding it.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2010-04-03 16:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03  9:16 [gentoo-dev] Is Gentoo dying? Tobias Scherbaum
2010-04-03  9:26 ` "Paweł Hajdan, Jr."
2010-04-03 10:12   ` Tobias Scherbaum
2010-04-03 11:36   ` hardened-sources development (was: Re: [gentoo-dev] Is Gentoo dying?) Thomas Sachau
2010-04-03  9:37 ` [gentoo-dev] Is Gentoo dying? Brian Harring
2010-04-03 10:10   ` Tobias Scherbaum
2010-04-03  9:38 ` Petteri Räty
2010-04-03 19:12   ` Jacob Godserv
2010-04-03  9:40 ` Robin H. Johnson
2010-04-03  9:46   ` Robin H. Johnson
2010-04-03  9:46 ` [gentoo-dev] Is Gentoo a Phoenix? Patrick Lauer
2010-04-03 10:19   ` Tobias Scherbaum
2010-04-03 11:33     ` Richard Freeman
2010-04-03 11:50       ` Petteri Räty
2010-04-04 18:09       ` Denis Dupeyron
2010-04-05 15:33         ` Richard Freeman
2010-04-05 17:21           ` Denis Dupeyron
2010-04-04 20:19       ` Zeerak Mustafa Waseem
2010-04-05  4:24         ` [gentoo-dev] " Duncan
2010-04-03 12:40     ` [gentoo-dev] " Magnus Granberg
2010-04-03 12:18   ` [gentoo-dev][Gentoo Phoenix] " Ben de Groot
2010-04-03 14:40 ` [gentoo-dev] Is Gentoo dying? Roy Bamford
2010-04-03 14:59   ` Tobias Scherbaum
2010-04-03 16:03     ` Alec Warner
2010-04-03 16:24       ` Matti Bickel [this message]
2010-04-03 23:52       ` Sebastian Pipping
2010-04-04 20:48     ` Roy Bamford
2010-04-06  6:24       ` Sebastian Pipping
2010-04-04  1:48 ` Joshua Saddler
2010-04-04  2:40   ` Alec Warner
2010-04-04  4:50     ` Dale
2010-04-05  0:28       ` Jorge Manuel B. S. Vicetto
2010-04-04  8:22   ` Tobias Scherbaum
2010-04-04 10:07     ` Joshua Saddler
2010-04-04  8:25   ` Petteri Räty
2010-04-04  8:44   ` Patrick Lauer
2010-04-04  9:56     ` [gentoo-dev] " Duncan
2010-04-04 10:21       ` George Prowse

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=4BB76BD0.4080607@gentoo.org \
    --to=mabi@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