Allow any particular update to be suppressed

Forgive me if this has been discussed before, and I have missed it. Also: I've put this as 7.x-dev, realising that it's too late for a feature request in 7.0, but I'm unclear if that means I should have put 8.x-dev or if this is the kind of feature that gets written into later 7.x releases.

Recently, on the nodewords issue queue, there has been a long discussion about a release (6.x-1.7) that was flawed and actually corrupted data on some sites. Having rolled back to its predecessor, I was not interested in installing 6.x-1.7 again, but I still got e-mails telling me that one or more modules had a new release available. I ignored those e-mails, knowing that they referred to Nodewords, and that I did not want to install the update that the update module referred to.

However, ignoring those e-mails is both risky and unhelpful for me. It is risky, because there may be a new release for a different module, and I should keep other modules up to date even if I didn't wish to update Nodewords. It is unhelpful, because Nodewords 6.x-1.7 was unstable, but 6.x-1.8 is not (AFAIK). So: I didn't actually want to ignore those e-mails forever - only until 6.x-1.8 was released or until a different module was updated.

So: Here's the feature request. How about the UI gives the option to flag a particular updated release as unwanted. No further e-mails about new releases will be sent out until one of 3 things happens:

• The module whose release was flagged as unwanted issues a subsequent release with a higher version number.
• A different module releases a new version.
• The updated release I flagged as unwanted is subsequently flagged as a security issue and therefore as a high-priority update. Possibly, I should be allowed to flag it as unwanted a second time, but I should still receive an e-mail to warn me that the stakes are now higher.

Just a thought on how the update e-mails could be more useful to a site administrator...