New translation import notification system is wrong on many levels

I got 39 emails for ktorrent alone. :(

I would also prefer failure notifications only.

I would even prefer if it just sent one email listing all the successful imports, and separate ones for the failures. (Or maybe just one email for all the failures?)

Thanks for the report. The notifications themselves are not new, they've just been activated for Ubuntu packagers (upstream uploaders already got them, though only once for every file: packages have a problem like described in bug 333772).

Colin was seriously bit (and is likely still being bitten) by the import notifications (it should not have been that bad) because of what seems to be a package building issue (bug 336063), and he got some extra karma (bug 337313).

Number of failures will be further reduced when bug 331094 is fixed, and it seems to be a general consensus that no success notifications should be sent out (bug 337658). Please make sure to indicate in that bug what type of notifications you'd like (explained in the comment on that bug), so there are no more surprises.

My plan for fixing this is to:
 • Fix 331094: remove useless failure notification messages.
 • Fix 337658: do not send out success notifications.

This should bring the number of emails you get to only a few (times the number of architectures, due to bug 333772, which is hard to fix, but I hope that will not be a problem once the number of sent out messages is below 3 in most cases, and with packages with no problems, zero).

My preference would be for none as I have no idea what I would do with a
failure message if I got one. I can see sense in notifying on failure
though, but no more than once per source package since that's the level of
granularity developers work with for uploads.

I think https://bugs.launchpad.net/soyuz/+bug/336063/comments/7 is actually relevant to this bug as bug 336063 is about a specific Soyuz issue. 13,000 emails doesn't strike me as something that should ever happen.

It seems the importer started up again this morning, and I had recieved about 4 to 5 thousand more emails before I stopped into #launchpad on freenode to get a hand.

Marking this as 'Invalid' since we've got bugs for all the smaller steps that need carrying out (and the most important of them is already done). This is not really an 'Invalid' request, but is too broad for the way we organize our work. If any particular issue bites you very hard, please go to the appropriate bug as indicated in my previous comment.

Thanks, and sorry for causing so many problems for you guys.