Altought I don't like your tone, I second that. I also had some nasty
issues on versions 1.4.14 to 1.4.17, specially 1.4.16.1.
The main problem is the incredible number of deadlocks it causes. My
clients often called more than once a day to complain that the PBX
wasn't making and receiving
Altought I don't like your tone, I second that. I also had some nasty
issues on versions 1.4.14 to 1.4.17, specially 1.4.16.1.
The main problem is the incredible number of deadlocks it causes. My
clients often called more than once a day to complain that the PBX
wasn't making and receiving
Altought I don't like your tone, I second that. I also had some nasty
issues on versions 1.4.14 to 1.4.17, specially 1.4.16.1.
The main problem is the incredible number of deadlocks it causes. My
clients often called more than once a day to complain that the PBX
wasn't making and receiving
David Boyd wrote:
I have followed several threads of late on various projects that seem to
be coming to a head on the methods and processes that make up an open
source project. As we are a development company that embraces the open
source concepts and ideas, we have begun exploring what makes
Bob wrote:
This fails to answer what the release process is.
I'm actually offering some test facilities here if I knew what to test.
If only it were that easy. Test facilities are not the issue. Knowing what to
test is. There is no obvious answer to that question given that Asterisk is a
On Mon, 2008-01-14 at 08:35 -0500, David Boyd wrote:
Maybe Digium doesn't care if they lose community support as they have been
successful in bringing in investment that will carry them forward as they
deploy more commercial product
Absolutely not. Digium cares *very deeply* about the
