<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body><div style="font-family:Helvetica,Arial;font-size:13px; "><br></div> I’d personally be OK with this. The more I think about this, two years is really long enough. With your approach below, someone would have an entire LTS release cycle to make any necessary integration changes that come as a result of a module that is removed. If someone complains about defaultenabled no in the LTS release of which it is set that way, it seems to me that it is unlikely that same person would pay attention to any other documentation telling them that they had an integration issue to address even if they had two more years to do so. <br> <br><p class="airmail_on">On October 1, 2020 at 3:55:19 PM, Joshua C. Colp (<a href="mailto:jcolp@sangoma.com">jcolp@sangoma.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div><div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div>From the development side we certainly can. The question is really - is it fair to the Asterisk user base, will they they accept it, will there be substantial backlash? The answer could be its fine. I don't really have a concrete answer though at this moment and likely wouldn't until put into action.</div><div><br></div><div>For a 2 year strategy I think it would go as such:</div><div><br></div><div>1. Minor releases receive change to indicate that module is to be deprecated in a future major release</div><div>2. Module is marked deprecated and defaultenabled no in standard release (19), which carries over to next LTS release (20)</div><div>3. Announcement and documentation for each includes notice of deprecated modules</div><div>4. Standard release after this it is removed (21), which carries over to next LTS release (22)</div><div>5. Announcement and documentation for each includes notice of removed modules</div><div><br></div><div>A wiki page would still be kept to keep track of modules in process of being removed.</div><div><br></div><div>Note that I'm just putting this out there so people see in comparison to the other one what the process would be like.</div></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-family:tahoma,sans-serif"><font color="#073763">Joshua C. Colp</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Asterisk Technical Lead</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Sangoma Technologies</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Check us out at <a href="http://www.sangoma.com" target="_blank">www.sangoma.com</a> and <a href="http://www.asterisk.org" target="_blank">www.asterisk.org</a></font><br></div></div></div></div></div></div></div></div></div></div></div>
-- <br>_____________________________________________________________________<br>-- Bandwidth and Colocation Provided by http://www.api-digital.com --<br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> http://lists.digium.com/mailman/listinfo/asterisk-dev</div></div></span></blockquote></body></html>