oops, yes, I made the alert general and not specific to versions prior to v0.10.2
I guess I should cancel it and generate another one
Good testing for the alert system then

I've reflected the alert on the explorer home page, but this makes me wonder if there could not be two "errors" message instead of one.
* errors: would be same as current, specific alert updates, problems with the daemon, etc.
* alerts: would hold general alert messages/messages, not specific to your daemon.
The alerts could be reflected in the explorers and websites, and be a way for the dev ( you

) to push news in a widespread fashion.
I think the priority field of the alerts is made for this purpose. It's odd that the getinfo rpc shows them as "errors" instead of "alerts", but alerts can have a start and an end time, a priority, and can be made to target specific client versions or general.
So, a low priority, general alert, could be used to push news... but for not important messages twitter is just more user friendly