Deprecations as data

[dukeleto]

All of our deprecations should be stored in a file in the Parrot git repo. The format of the file isn't important, whichever is the simplest is probably best. YAML or JSON or CSV are probably the top contenders for a format.

This file is very important because then we can build tools that use this deprecation data to generate code, or helpful instructions to HLL devs when they are "paying an upgrade tax". For example:

A script that looks at the source code of an HLL and then spits out which deprecated features are being used and the dates/versions when they are eligble to be removed and a wiki page link for how to use whatever is replacing the deprecation.

[dukeleto]

We need a spec for what information we want to store about a deprecation and a script that will transform DEPRECATED.pod into DEPRECATED.yaml

[tadzik]

I made it DEPRECATED.json, lives in a branch  https://github.com/parrot/parrot/commits/tadzik/deprecated-json

[tadzik]

It's now YAML, pushed to master, and @parrot-dev is notified. May need some docs (DEPRECATED.README?) so editors of the file will know how is it formatted and why.

[dukeleto]

This file is now called api.yaml and there are two tools to interact with it: tools/dev/show_deprecations.pl shows current deprecations and tools/dev/show_experimental.pl shows current experimental features.