[GRASS5] Dealing with old bug reports: new GRASS 6 bugtracker?

[Markus Neteler]

Hi,

just a comment on how to deal with old bug reports in our
bugtracker:

In the QGIS project old reports are automatically closed if
the reporter doesn't answer a comment in n days:

---------------- snip Example ----------------
>Comment By: SourceForge Robot (sf-robot)

Date: 07/21/05 19:00

Message:
Logged In: YES 
user_id=1312539

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 45 days (the time period specified by
the administrator of this Tracker).

---------------- end snip ----------------

I would appreciate to have such a feature for us. A few days ago
I spent some time on cleaning up reports in RT and came across
a couple (many) reports which are untouched for years and will
remain untouched for other years. IMHO we shouldn't make RT a museum
of old reports about bugs in old GRASS versions which aren't used
any more by the majority of users. 

Some stats:

# total open bugs:
./htmltable_extractor.pl bugs.html | tr '\n' ' ' | tr '[' '\n' | grep ' #' | wc -l
    452

out of these:

# GRASS 6 bugs:
./htmltable_extractor.pl bugs.html | tr '\n' ' ' | tr '[' '\n' | grep grass6 | wc -l
     64

# GRASS 6 wishes:
./htmltable_extractor.pl bugs.html | tr '\n' ' ' | tr '[' '\n' | grep wish6 | wc -l
     40

# bugs older than 1 year
./htmltable_extractor.pl bugs.html | tr '\n' ' ' | tr '[' '\n' | grep yr | wc -l
    156

# bugs older than 2+ years
./htmltable_extractor.pl bugs.html | tr '\n' ' ' | tr '[' '\n' | grep '[2|3|4] yr' | wc -l
     96

In summary: The 452 bug reports do NOT reflect the current that of GRASS 6. It's
simply misleading. 

Other suggestion: We set up a separate bugtracker for GRASS 6.


Markus

PS: I used http://www.devshed.com/c/a/Perl/Web-Mining-with-Perl/2/