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.
On October 1, 2020 at 3:55:19 PM, Joshua C. Colp (jc...@sangoma.com) wrote:
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.
For a 2 year strategy I think it would go as such:
1. Minor releases receive change to indicate that module is to be deprecated in
a future major release
2. Module is marked deprecated and defaultenabled no in standard release (19),
which carries over to next LTS release (20)
3. Announcement and documentation for each includes notice of deprecated modules
4. Standard release after this it is removed (21), which carries over to next
LTS release (22)
5. Announcement and documentation for each includes notice of removed modules
A wiki page would still be kept to keep track of modules in process of being
removed.
Note that I'm just putting this out there so people see in comparison to the
other one what the process would be like.
--
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
--
_____________________________________________________________________
-- 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
