<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Makes sense to me!<br><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Nov 9, 2020, at 8:24 AM, Joshua C. Colp <jcolp@sangoma.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">On Tue, Oct 13, 2020 at 7:55 AM Joshua C. Colp <<a href="mailto:jcolp@sangoma.com" target="_blank">jcolp@sangoma.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hey all,</div><div><br></div><div>I just wanted to drop an email and say that this hasn't been dropped or anything. A 2 year option just isn't something I want to rush into without thinking through all the ripples, which since we're approaching AstriDevCon and AstriCon is something that occurs here and there at the moment. :D</div></div></blockquote><div><br></div><div>I'm back, back again. Josh is back. Tell a friend.</div><div><br></div><div>After giving further thought to things and the opinions presented I think we can safely try a 2 year approach since we have a notification mechanism in the form of a standard release and notice in minor releases with the ability to receive feedback from the community. This means the process would be:</div><div><br></div><div><div>1. Minor releases receive change to indicate that module is to be deprecated in a future major release<br></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 be kept to keep track of modules in process of being removed, as well as history to show when things were actually removed.</div></div><div><br></div><div>Since this is the first real time formalizing this once all the things are in place (process documented on wiki, deprecation list created from existing state of things) I'll likely send out an email to -users and also post on the community forums so people are aware.</div><div><br></div><div>Sound good to everyone?</div></div><div><br></div>-- <br><div dir="ltr"><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>
<span>-- </span><br><span>_____________________________________________________________________</span><br><span>-- Bandwidth and Colocation Provided by http://www.api-digital.com --</span><br><span></span><br><span>asterisk-dev mailing list</span><br><span>To UNSUBSCRIBE or update options visit:</span><br><span> http://lists.digium.com/mailman/listinfo/asterisk-dev</span></div></blockquote></body></html>