Re: PEAR Bug Summary Report

Helgi Þormar wrote:

Yeah probably, but that means I'd have to store the whole array serialized in database and diff against it, and for me it seems like whole lot of unnecessary resource usage, but I'll keep it in mind for later date when this has proven it self, I'd rather like to make this into "one email per dev, not per package", then be doing the diff thing. Or even have a changelog thing in the bug system similar to say Whups (that's the only Bug system I've looked somewhat into beside PEAR one) then this diff stuff should be no problem and wouldn't take much resources in doing. Ok, Helgi,

Not joking, a long list is difficult to interpret. So, some kind of diff should be more understable, as say: Please refer to http://pear.php.net/bugs/stats.php We stay on some 452 total not closed. Thanks devs, that went minus:

ID   Status                    Summary (98 down this month)

======================[QA-pckg]================== xxx -Open+Assigned Helgi, you forgot to say "Joyeux Noël!" ... (Followed by:) Bad for devs, that went +: ID Status Summary (grown 27 this month) ======================[QA-pckg]================== yyyy Open I tried to reach Sancta Klaus there ptp://clouds.in.sky/, no answer ... Long lists are not to be read, just proceeded. Thru this equinox, bye. -- bertrand Gugger