public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tomáš Chvátal" <scarabeus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Quantity of open bugs
Date: Wed, 16 Mar 2011 10:46:47 +0100	[thread overview]
Message-ID: <4D808707.8080104@gentoo.org> (raw)
In-Reply-To: <20110310202510.45627780@athlong2.kevquinn.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Kevin,
open bugs alone are never the issue.
We can have millions of them open and still being able to manage things
in sanely manner.

So if the issue is not open bugs as whole, what it can be?
Open bugs for specified area. Imagine you work on KDE, you fire up your
bugzilla and start watching whats going on. Currently we have around 200
open bugs, which is manageable. But at one point we got nearly to 500
where we really lost any track of what the heck is happening.

The goal should be that projects itself should focus and try to lower
their bug count or introduce simple queries for their members to have
reduced number of the bugs in their list.

Open bugs are good, they are reminder that we should look to issues,
even if it just means testing and stating that the things were fixed in
meantime. Closing them would not solve anything.

Only problematic parts of the bugzilla are unmaintained areas (herds) of
the tree where the bugs have tendency to grow. The fix itself is not to
close those bugs, but motivate some guys to work on that area and became
developers so that bug number effectively became manageable.

Cheers

- --------
Tomáš Chvátal
Gentoo Linux Developer [Clustering/Council/KDE/QA/Sci/X11]
E-Mail          : scarabeus@gentoo.org
GnuPG FP        : 94A4 5CCD 85D3 DE24 FE99 F924 1C1E 9CDE 0341 4587
GnuPG ID        : 03414587

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2AhwcACgkQHB6c3gNBRYerUQCeIGkQg3hbEwdUCBMNqb6gTPlq
Xo0AmgPF7zUHAkC0Lv8TdHTOU39mONAw
=QSOi
-----END PGP SIGNATURE-----



      parent reply	other threads:[~2011-03-16  9:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110307130425.3C1ED1C042@pigeon.gentoo.org>
2011-03-10 20:25 ` [gentoo-dev] Quantity of open bugs Kevin F. Quinn
2011-03-10 21:03   ` [gentoo-dev] " Duncan
2011-03-10 21:33   ` [gentoo-dev] " Chris Richards
2011-03-11  4:46   ` [gentoo-dev] " Ryan Hill
2011-03-11  8:07   ` [gentoo-dev] " Alec Warner
2011-03-11  8:25   ` George Prowse
2011-03-11 14:13   ` Thomas Kahle
2011-03-12 14:45   ` [gentoo-dev] " Diego Elio Pettenò
2011-03-12 17:09     ` Donnie Berkholz
2011-03-12 17:16       ` [gentoo-dev] " Diego Elio Pettenò
2011-03-16  4:17     ` [gentoo-dev] " Jeroen Roovers
2011-03-16  9:46   ` Tomáš Chvátal [this message]

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=4D808707.8080104@gentoo.org \
    --to=scarabeus@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