Here's the skinny:
We'd put together a Wiki page here:
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States
that notes for Deprecated items:
"The module will remain in the tree, but there is a better way to do it. After two release cycles, issue that have been deprecated for some time will be listed in an e-mail to the Asterisk-Dev list, where the community will have an opportunity to comment on whether a deprecated module: still compiles, works sufficiently well, and it still being utilized in a system where there is a justification for not using the preferred module."
...
The result of that is that when something comes up for discussion and everyone says "it's broken, no one uses it, pull it," it'll get pulled. When it comes up and everyone says "it's fine, everyone uses it, leave it," it'll stay. And, when it comes up and the message is mixed - some for, some against, and some use it - it'll stay.
We don't want to drag along code that's horribly broken or that's totally unused. But, where it's working, and someone's using it, we don't want to negatively impact their use.
So, for something like the MySQL bits in addons/. where they're commonly used and they work, I don't think they'd get yanked...not unless everyone who uses FreePBX answered the future Asterisk-Dev list posting (that's still years off) said "nah, we don't use them anymore, and they're broken anyway."
Yes, no, nuts?
We'd put together a Wiki page here:
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States
that notes for Deprecated items:
"The module will remain in the tree, but there is a better way to do it. After two release cycles, issue that have been deprecated for some time will be listed in an e-mail to the Asterisk-Dev list, where the community will have an opportunity to comment on whether a deprecated module: still compiles, works sufficiently well, and it still being utilized in a system where there is a justification for not using the preferred module."
...
The result of that is that when something comes up for discussion and everyone says "it's broken, no one uses it, pull it," it'll get pulled. When it comes up and everyone says "it's fine, everyone uses it, leave it," it'll stay. And, when it comes up and the message is mixed - some for, some against, and some use it - it'll stay.
We don't want to drag along code that's horribly broken or that's totally unused. But, where it's working, and someone's using it, we don't want to negatively impact their use.
So, for something like the MySQL bits in addons/. where they're commonly used and they work, I don't think they'd get yanked...not unless everyone who uses FreePBX answered the future Asterisk-Dev list posting (that's still years off) said "nah, we don't use them anymore, and they're broken anyway."
Yes, no, nuts?