I was hoping you'd pipe in again Jared! Thank you!
On Fri, 2 Oct 2020, 20:20 Jared Smith, wrote:
> On Fri, Oct 2, 2020 at 11:50 AM Dan Jenkins wrote:
>
>> sorry, I thought I was agreeing with you :) we need to engage package
>> maintainers to potentially help ease the shift - if packages are a
On Fri, Oct 2, 2020 at 11:50 AM Dan Jenkins wrote:
> sorry, I thought I was agreeing with you :) we need to engage package
> maintainers to potentially help ease the shift - if packages are a
> thing but as far as I'm concerned most package managers have out of
> date versions of Asterisk, or
Hi Olle,
sorry, I thought I was agreeing with you :) we need to engage package
maintainers to potentially help ease the shift - if packages are a
thing but as far as I'm concerned most package managers have out of
date versions of Asterisk, or don't have things you want so you end up
building
I think you misunderstand me. I am not against deprecation and deletion. I just
want us to find a way to
try to get through to a larger group of users when we do this. For the SIP
channel case, I don’t think anyone has
missed it - it’s been far too long with two channels, which is confusing.
The
Ultimately whats stopping package maintainers from releasing
"asterisk-full" which still has all the deprecated modules enabled and
"asterisk" which follows the defaults? Nothing Other packages get
released in such a way so why not asterisk? I'm 100% not qualified to talk
about it because I
Hi!
I like adding product management and actually removing stuff that the company
can’t keep maintaining - and don’t wan’t to.
Compared with years ago a lot of users never bother building asterisk any more
and don’t interface with the project,
they just run “apt-get install asterisk” and they ar