Malone should send a reminder by mail to check validity of bugs

[Sebastien Estienne]

i think that malone could send every month a mail report to the people that opened bugs to ask them to check the validity of it.

It would help us to clear bugs that are not revelant any more.

[Matthew Paul Thomas (mpt)]

On the other hand, it would penalize the *reporter* for the *developers* being slow to respond, which might not be such a good idea.

[Sebastien Estienne (sebest)]

so maybe not each month, but for bugs that are older thanx N months (eg 2 or 3).

Btw, it's another "wishlist", but having some statistics and graphics about malone like:
 * a graph of the number of open/closed bug
 * histogram of number of bugs per age of bug
 * number of bugs per team , package

This would help us to see trends:
 * is the number of bug decreasing or not, are we getting more stable or not
 * what kind of package/hardware/drier is "problematic"
 * which team needs help to fix bugs

I would be happy to work on such thing, but does malone/launchpad provide these data, in a way or another (xml-rpc, soap) ?

Maybe i should open a specific "wishlist" for this

[Christian Reis (kiko)]

Yes, it should be reported as a separate bug. Thanks!

[Brad Bollenbach (bradb)]

On Thu, 2006-03-30 at 05:13 +0000, Matthew Paul Thomas wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/36025
>
> Comment:
> On the other hand, it would penalize the *reporter* for the *developers*
> being slow to respond, which might not be such a good idea.

I agree. To not penalize the reporter for developers being slow to
respond, I'd suggest an approach focused on encouraging triagers to do
their job.

We could have a report aimed specifically at triagers and others who
want to contribute to the bug tracking effort. This report could include
stats with links to their respective bug lists like:

* Number of bugs filed but not yet assigned to a package

* Number of bugs that have not yet had any response

* Number of bugs that were filed by you, and are set Needs Info

* Number of bugs that are > 30 days old and have not yet had any
response

* Number of critical bugs not yet targeted to a release

* etc.

What do you guys think?

[Sebastien Estienne (sebest)]

i have created a specific bug/wishlist for a statistic/graph module:
bug #37344

i think it would also bring some fun to try to make the number of open bug decreasing, in the same spirit as karma.

[Sebastien Estienne (sebest)]

the reminder could be manual.

for example, there is a lot of open bugs about network-manager, but a lot of them are no more valid because they were opened with nm 0.5.x and we now have 0.6.2 that may have fixed a lot of issues.

so i guess the developper that take care of nm, would like to have an option to "tick" all the bugs that he'd like the repoter to check the validity. And then automatically send a mail to the people that report the bug.

A bonus would be to have 2 links in the mail: "Bug fixed" , "Bug still present". So you just have to push the link to answer.

[Sebastien Estienne (sebest)]

On a side note, i think this "wishlist" is related to bug #30658 .

eg: when a new version of a package is out, a reminder should be sent to bug report made against older released of the said package.

If not automatically, displaying in color the bugs that may not be revelant anymore would be a great information to help developers cleaning the oldest bugs.

If you look at the oldest bugs, you'll notice that most of them have question like "is this still revelant?", so it seems to be a frequent question/action.

[Björn Tillenius (bjornt)]

Something like this has been under discussion recently.