Hey,
As with chad, I don't think it's revert war worthy.
I fully agree it is not.
c) deprecation bumped to version X+1 in response
Why would you do this? If an extension author has no time to update something, this should not affect deprecation policy in core. There might be exceptions, but in general this seems like a dumb thing to do.
It's not that it doesn't exist, it just seems too marginal.
I ran into it 3 times in the last 2 months and have 3 methods whitelisted in localsettings which I'll take care off later. It is not rare if you are about forward compatibility. Right now I have everything compatible with trunk except these 3. Without this whitelist I'd have to turn off warnings for 1.19 to be able to use my wiki without getting a pile of notices every time, in which case I'd not know yet about several changes I've already taken care off now. Note how the frequency of these whitelisted methods does not matter. One is enough to make you swicth to a not as good configured dev environment.
Cheers
-- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. --