[asterisk-dev] Plans for legacy APIs in Asterisk ?
Matt Fredrickson
creslin at digium.com
Wed Oct 4 13:57:19 CDT 2017
Welcome! Reply is inline.
On Wed, Oct 4, 2017 at 9:42 AM, Hans Petter Selasky <hps at selasky.org> wrote:
> Hi,
>
> I maintain an external channel driver called chan_capi for ISDN4BSD (not
> the same like chan_capi for Linux). Every time there is a new major release
> of Asterisk I need to update my channel driver, because some APIs have
> changed. My question is how can I avoid this?
>
> 1) Are there any plans for long-term APIs in Asterisk?
>
Not specifically. There are APIs in Asterisk that have existed for long
periods of time, but no APIs that self guarantee their existence for some
specific period of time.
2) How can I get my channel driver into Asterisk itself to have the
> Asterisk developers do this work whenever there is a significant API change?
>
The usual path for that is contributing it via the code review process on
gerrit.asterisk.org. This in and of itself does not mean that it will be
taken care of for you but it does increase the likelihood that its
existence will be weighed in API change decisions and potentially have
internal API migrations also occur to the channel driver.
Best wishes.
--
Matthew Fredrickson
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20171004/2da8be59/attachment.html>
More information about the asterisk-dev
mailing list