My Test::JSON currently has 2 failures out of 106 test reports sent. One failure appears to be a messed up Perl installation, but the one I received yesterday is due to the JSON module being updated in a non-backwards compatible way. Apparently, there was a deprecation period of a whopping twelve days (going by the date of the first release of the new API to 2.0). I had not heard that there was going to be a new API and the author has made it clear that he won't support the old API.
Now I'll have to get a new release of Test::JSON out the door. Do I go through the trouble of allowing it to support the older JSON module in addition to the new API? I might. Frankly, I'm frustrated to be caught completely off guard by such a radical change in this important module, though I realize I'm not the first. But a twelve day deprecation period is ridiculous. And was this even at least announced anywhere? I might even look to switching to a different JSON module with an author who is less likely to pull the rug out from under me so quickly.