sbp commented on issue #382: URL: https://github.com/apache/tooling-trusted-releases/issues/382#issuecomment-4489107090
There are a couple of reasons why we're strongly considering implementing retries in ATR instead: * **It doesn't make sense to alert the user when reminders are being sent.** The purpose of reminder emails is to alert a user who is not logged in that the vote is over. We are also planning other autonomous emails such as reminding binding voters not to vote on the mailing list if they do so in Trusted vote mode. It doesn't make sense to fail these with a message in the notification system in ATR; they simply _must_ work through email in order for them to be effective in their intended purpose. * **We fork email send tasks immediately, so we cannot give immediate feedback.** We could wait until a message has been sent, and then say "oh, it wasn't sent", but then what? We would have to add a resending feature to every action where an email is sent on ATR, and the user would have to remember to retry an arbitrary number of times, with progressively longer waits. This is, of course, exactly the sort of thing that should be done in code. We should also have a queue page showing all message that have recently been sent or are pending to be sent, for each user. If, after several automated retries, a message still does not send, then we can send a message through the notification system anyway, because in that point it basically becomes a legitimate task failure. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
