[asterisk-dev] Module Deprecation, Default Not Building, and Removal

[Joshua C. Colp]

On Thu, Oct 1, 2020 at 2:18 PM Corey Farrell <git at cfware.com> wrote:

> Yes I'm suggesting documenting that it is deprecated in minor releases.
> Ending support in a minor seems bad unless support already doesn't exist.
> Could we add AST_MODULE_SUPPORT_CORE_DEPRECATED and
> AST_MODULE_SUPPORT_EXTENDED_DEPRECATED to `enum ast_module_support_level`?
> Then a module would get one of those support levels in a minor,
> AST_MODULE_SUPPORT_DEPRECATED in master.
>

We could, but just so I'm clear - it would be stated as "to be deprecated
in future" essentially in minor releases and then marked as deprecated in
master?

-- 
Joshua C. Colp
Asterisk Technical Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20201001/e62a4897/attachment.html>