<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000"><div>----- On Oct 1, 2020, at 7:56 AM, Joshua C. Colp <jcolp@sangoma.com> wrote:<br></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div dir="ltr">Greetings all,<br><div>Around this time each year a discussion always spurs (be it on IRC or at AstriDevCon) about deprecating modules, and removing them. I always find myself asking "what is our real process for doing this?" in my head and end up trying to piece it together based on some information here and there on the wiki plus past experience. I'd like to better document this and put something more concrete into place. To that end I'd like to propose the following:</div><br><div>1. All the changes listed below initially occur in standard releases - in my opinion beginning the process to remove a module is a big thing and we should gradually introduce it, gaining feedback from those who run standard releases first.</div><div>2. The first step is marking a module as deprecated and occurs for 1 standard release and 1 LTS release</div><div>3. The second step is marking a module as defaultenabled no which means it will not be built by default. This occurs for 1 standard release and 1 LTS release</div><div>4. The third step is removing the module</div><div>5. There will be a wiki page to keep track of all modules which are in the process of being removed</div><div>6. When a new LTS branch is created the master branch becomes eligible again for changing the state of modules, a reminder can be done as part of cutting the LTS branch</div><br><div>Thoughts?</div></div></blockquote><div><br></div><div>The steps outlined seem very reasonable and appropriate.</div><div><br data-mce-bogus="1"></div><div>Great job on getting this hashed out and documented.</div><div><br data-mce-bogus="1"></div><div>--</div><div>Michael Young</div><div><br data-mce-bogus="1"></div><div>(elguero)</div></div></div></body></html>