On Thu, Sep 4, 2008 at 6:36 AM, Barbie <[EMAIL PROTECTED]> wrote: > However, I think I can go even better than that, if my brainwave this > morning isn't faulty. Doing the mailer after the database gets updated, > means that rather than sending the author a mail for every report, with > the contents of the report, we can send them an aggregated mail of all > the FAILs for all their distributions since the last update. But instead > of including the report content, we simply include a link to the current > NNTP copy. This can later be updated to allow them to retrieve the > report for the CT2.0 storage. > > The upshot is that instead of a flood they get 1 mail, with everything > in. They then have the option to review it or junk it.
Sounds like a workable option and it sounds like you have a lot of the necessary tools written already. Are they on a repository somewhere so other can contribute? Also, I think the author issue isn't just the volume of mail -- but the repetitious nature of it. Sending a daily report that lists that Foo-Bar-1.23 failed on Win32 Perl 5.10.0 isn't so useful if they got a similar report yesterday. That's why I think the notification should be only once per dist-perl-archname tuple. Whether that is an email digest with other tuples is a secondary concern in my view. -- David
