[asterisk-dev] Which enviroments are supported, really?

[George Joseph]

On Mon, Jan 22, 2018 at 3:03 AM, Alexander Traud <pabstraud at compuserve.com>
wrote:

> I am not about the bugs themselves. I am going to fix and/or report them.
> I fixed already several of them. And more are coming. However, I am
> interested which environments are supported.
>
> After a mayor release like Asterisk 15, I would have expected that someone
> does a cross-check before the 15.1 release, at least before the 15.2
> release. Those eight steps are automatic stuff. All one has to do is to
> setup a new virtual machine, with a vanilla installation. Then, the actual
> work is to double-check the results (of configure, make, and make install).
> Obviously, nobody does this. Even those who do the ports, either do not
> understand the result of configure correctly or ignore it without
> reporting. For example, in BSD, the external library libedit is the
> default, no need to build the internal one of Asterisk. However,
> ./configure of Asterisk fails to find it and (tries to) build its own one.
> That is an issue since commit 7d4ccea (summer 2012).
>
> I was so surprised about the number of issues. One can learn so much by
> doing interoperability tests. And in this case, this learning is near to
> free.
>
> > Ubuntu 16.04 LTS (x86_64)
>
> That is great news (for me), because that is my main platform.
> Consequently, I do not have to consider to move.
>
> > ... Fedora ...
>
> ASTERISK-27598, for more details see ASTERISK-27599
> That was reported in May 2017: ASTERISK-26981.
> Actually, the first report was in December 2015: ASTERISK-24597.
>
> > ... GNU bash ...
>
> ASTERISK-27606
>

>From a distribution perspective, Ubuntu (Josh, Kevin and Richard) and
Fedora (myself and Ben) are what the Digium dev team uses for their own
development desktops so those are going to get the most daily testing.  As
Corey mentioned though, we also test on CentOS7, both 32-bit and 64-bit
builds.  Havingf said that though, while I think we do a pretty good job
testing building and running Asterisk on those distributions, we could
probably do a better job of testing the development and production
environment setup process, especially install_prereq.  Maybe we could set
up a weekly periodic Jenkins job to start with a clean official docker
image from each of the 3 distros and do an environment setup from scratch
just using the tools available in the asterisk tarball.

Testing FreeBSD poses other problems however.  None of us really work with
BSD based distributions so it would take more time that we have available
to do any serious testing there.


>
>
>
> --
> _____________________________________________________________________
> -- 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
>



-- 
George Joseph
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20180122/26d761a4/attachment.html>