On Thu, Mar 11, 2021 at 1:45 PM Dan Jenkins <d...@nimblea.pe> wrote: > Hi Josh, > > Thanks for this! I have a question regarding this line in your email. > > These changes allow the information regarding when a module was deprecated > and when it will be removed to be communicated to users in earlier branches. > > > Does this mean that app_foo being marked as deprecated in master (19 isnt > cut yet) will appear in earlier versions of Asterisk too? ie a new security > release of 16 gets released and the newly deprecated in master app_foo > will get applied as a warning to 16? I didnt see that explained in the wiki > article but I think thats how we talked about it working a while back >
Yes, it will get applied as a warning. Specifically in older branches (such as 16) you set additional XML (two lines) in the module for the version with the version it is deprecated in and the version it is removed in. This is then used to display to the user that it will be deprecated and removed in the upcoming versions. -- Joshua C. Colp Asterisk Technical Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
