[asterisk-dev] Asterisk 19: res_adsi built although deprecated?

Joshua C. Colp jcolp at sangoma.com
Wed Aug 25 14:10:46 CDT 2021

On Wed, Aug 25, 2021 at 3:58 PM Alexander Traud <pabstraud at compuserve.com>

> > Please create an issue for this on the tracker.
> There, we go:
> <https://issues.asterisk.org/jira/browse/ASTERISK-29617>
> The current maintainer of that module contacted me off-list. Because
> res_adsi has a maintainer, it is not going to be removed and is not
> "deprecated" but "extended" actually. Anyway, as you can see, since
> Asterisk 16 LTS there are more and more infos, warnings, errors even on a
> vanilla installation with the default samples.
> Although those messages are trivial, a new user of Asterisk has to
> understand that those particular ones can be ignored. This is quite hostile
> for starters and might waste their time.
> My ideas: Either
> (A) deprecated modules are not built on default. Or
> (B) the loader gets changed not to give a warning but a notice. Or
> (C) the sample configuration (module.conf) gets changed not to load those
> deprecated modules on default.
> Anyone, with a plan D (perhaps even for some of the other messages)?

 We're in a transition period of time between when there wasn't really a
policy that was followed and a policy in place. Touching the existing LTS
branches and changing deprecated things to not build by default is not
acceptable there. That's a breaking change in the middle of them. I think
changing the sample configuration should theoretically be okay, but
additional input from others would be good. Going forward when a module is
deprecated it will be set to not build by default.

The res_adsi module and other modules that use it are still marked as
deprecated despite having a maintainer as the rest of the Asterisk
developer community does not want to support it, and keeping it deprecated
allows it to be removed easier if the existing maintainer steps away. It
can be set to not build by default in 19.

The loader messages went in as a warning to inform people of the state of
those modules, and to be aware that they can/will likely go away. I can see
both sides of warning and notice. Whether it's a warning or notice really
depends on who is reading it. If you aren't using them then it's a notice,
if you are using them then it's a warning. Additional input in this from
others would be good too.

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/20210825/eec8186a/attachment.html>

More information about the asterisk-dev mailing list