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

[Joshua C. Colp]

On Thu, Oct 1, 2020 at 1:51 PM Dan Jenkins <dan at nimblea.pe> wrote:

> Fantastic idea Corey - that would get people knowing about things earlier
> even if theyre not on a standard release.
>
> On Thu, Oct 1, 2020 at 5:46 PM Corey Farrell <git at cfware.com> wrote:
>
>> Any reason we can't "documentation deprecate" things in minor releases?
>> No runtime warnings and keep building by default but if we deprecate a
>> module in master right now it seems like the next minor release of all
>> active branches should document the status of the module.  The fact that a
>> module will still be supported on 16.14.0 doesn't stop us from telling
>> users what will happen.
>>
>>
Are you referring to marking it as deprecated in both a minor release and
master? Or are you referring to marking it as deprecated in minor releases,
then default enabled to no in master?

There's no mechanism right now to state that a module will be deprecated,
just the current support level. We'd either need to add something else, add
a different support level, or mark it as deprecated and end the support for
it in a minor release.

-- 
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/2fba8c3f/attachment.html>