Problem/Motivation
Just a placeholder for now but we need to send emails
Probably in at least 3 cases
- When a cron update fails
- #3285491: Send an email when a cron update succeeds
- #3316611: If unattended updates are enabled, send an email when status checks start failing
- Maybe when the installed version is about to go out of support. This maybe should part of #3275883: Warn if cron updates are enabled and the site is on an unsupported branch then we won't need special email logic for this
This will probably be multiple issues, probably not all of them will be Stable Blockers but some will.
We should make a detailed plan and determine what is and what is not a blocker before we start working on these
Comments
Comment #2
phenaproximaThis seems like a good idea on its face, but how do we prevent it from becoming a torrent of spammy emails? I guess we could set a state flag that says "we entered an invalid readiness state, and warned about it", clear that flag when the readiness checks come back green, and not send the email unless the last known state was good...
Comment #3
phenaproximaOf the stuff I see in the issue summary right now, I'd say that our only actual hard stable blocker, right now, is to send an email when a cron update fails. The rest are nice-to-haves, maybe even critical post-stable features, but I don't personally think they block a stable release.
Comment #4
phenaproximaOur first stable release need not include email support, so this is no longer a stable blocker. See #3284443: Enable unattended updates.
Comment #5
phenaproximaComment #6
tedbowComment #7
tedbowComment #8
tedbowComment #9
tedbowWe have done all these!