On Wed, May 30, 2007 at 04:50:47PM -0400, David Boyd wrote:
Not trying to start a flame war, however the issues that I see with 1.2
and 1.4 are very similar to the issues relating to Redhat and Fedora.
Redhat didn't want to continue supporting the open source model and
convinced? the end user
2007/5/31, Eric ManxPower Wieling [EMAIL PROTECTED]:
And Asterisk 1.2.18 STILL has show stopping bugs. This does not make me
feel all warm and fuzzy about moving to 1.4.x. In fact, the idea of
moving to 1.4.x right now scares the hell out of me. I don't like
crashing PBXs. I don't like
-Original Message-
From: [EMAIL PROTECTED] [mailto:asterisk-users-
[EMAIL PROTECTED] On Behalf Of Michael Collins
Sent: Tuesday, May 29, 2007 1:42 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [asterisk-users] *End Of Life ASTERISK 1.2.X
On 5/30/07, Steve Totaro [EMAIL PROTECTED] wrote:
I do hope that when they find major security bugs like the recent SIP
bug for example, that affected both 1.2.x and 1.4.x, they backport the
fix. At least if the code base has not changed all that much and it is
only a few lines of code.
Yes,
Wieling [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 6:18 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was:
INSTRUCTIONSFORTHE ASTERISK COMMUNITY - PLEASEREAD NOW *
Tzafrir Cohen wrote:
On Tue, May 29, 2007 at 01:06
The problem with this is that if 1.2 has a bug that is making it unstable,
it should be fixed to make a stable project, rather then steam rolling ahead
to the next release. Further, I have seen on several occassions a security
patch cause stability issues in Asterisk.
On 5/30/07, Jared Smith
Matt wrote:
The problem with this is that if 1.2 has a bug that is making it
unstable, it should be fixed to make a stable project, rather then steam
rolling ahead to the next release. Further, I have seen on several
occassions a security patch cause stability issues in Asterisk.
These
2007/5/30, Matt [EMAIL PROTECTED]:
The problem with this is that if 1.2 has a bug that is making it unstable,
it should be fixed to make a stable project, rather then steam rolling ahead
to the next release. Further, I have seen on several occassions a security
patch cause stability issues in
On Wed, 2007-05-30 at 21:54 +0200, Olivier wrote:
2007/5/30, Matt [EMAIL PROTECTED]:
The problem with this is that if 1.2 has a bug that is making
it unstable, it should be fixed to make a stable project,
rather then steam rolling ahead to the next release. Further,
On 5/30/07, Lee Jenkins [EMAIL PROTECTED] wrote:
These are my hopes as well. In addition to security related bugs, I
would like to see any stability bugs quashed as well. New features, I
can live without for now, but bugs affecting the stability of the
product should be implemented IMO.
It
Jared Smith wrote:
Now, let's do some quick math... Asterisk 1.2.0 was released in
November of 2005. That means almost 18 months since the feature
freeze for the Asterisk 1.2 branch. (In reality, it's longer than
that because there was a feature freeze on the 1.2 branch before 1.2.0
was
Except that for some users 1.2.18 is NOT stable. I've had to roll
back
to 1.2.15 on my production servers in order to prevent core dumps at
least once per day. No, I am not willing to turn my production
servers
into testing servers to solve this. Doing so would make me a former
consultant
Sent: Tuesday, May 29, 2007 1:08 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was:
INSTRUCTIONSFORTHE ASTERISK COMMUNITY - PLEASEREAD NOW *
Well i guess you just need a good look on logs for why and when you are
getting core
13 matches
Mail list logo
