#1888: Deprecations as data
----------------------+-----------------------------------------------------
Reporter: dukeleto | Owner:
Type: todo | Status: new
Priority: normal | Milestone: 2.11
Component: none | Version: 2.10.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: all |
----------------------+-----------------------------------------------------
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.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1888>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
