Ticket #1888 (closed todo: done)
Deprecations as data
|Reported by:||dukeleto||Owned by:||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.