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

[Joshua C. Colp]

On Thu, Oct 1, 2020 at 7:46 PM Joshua C. Colp <jcolp at sangoma.com> wrote:

> On Thu, Oct 1, 2020 at 7:01 PM Dan Jenkins <dan at nimblea.pe> wrote:
>
>> Completely agree with Sean on the "what's going to be deprecated"
>> question months before a cut. And I like the laid out plan that would be
>> involved for 2 year process of deprecation,default enabled no and then
>> remove.
>>
>
> I think as soon as the LTS branch is cut from master and master
> transitions to being the development branch for the next standard release -
> it's fair game up until the point that the standard release is cut from
> master so essentially during that development cycle if someone thinks of
> another it can be discussed. As part of cutting the LTS branch a reminder
> can be sent and a discussion can be done, as well as before "feature
> freeze" of master for the next standard release. If someone thinks of one
> even outside of that window we can add it to the wiki page and those can
> form the start of the discussion.
>

Er I actually meant a reminder can be sent alongside the reminder about
upcoming feature freeze. That spaces things out a bit neater time wise so
we can have two planned discussions, with any unplanned ones in between.

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