[asterisk-biz] Recent REMOTE CRASH BUG

[shadowym]

Good points all around and healthy discussion IMHO.

I have found in my 2 years of working with Asterisk and open source in
general is you have to approach it a bit differently than commercial closed
source stuff.  You gotta put in the time to throughly test a specific
version to make sure it does what you need it to do.  Usually a version that
has been out for awhile so that it has lot's of users contributing lot's
technical knowledge and is known to not have any major gotcha's in it.
Never ever cutting edge releases IMHO.

 

-----Original Message-----
From: Peter Bowyer [mailto:peter at bowyer.org] 
Sent: Saturday, March 03, 2007 2:09 PM
To: Commercial and Business-Oriented Asterisk Discussion
Subject: Re: [asterisk-biz] Recent REMOTE CRASH BUG

On 03/03/07, Matt <mhoppes at gmail.com> wrote:
> EXACTLY MY POINT!!!   There shouldn't be that many bugs.   Look at QMail
for
> an example of ONE PERSON who is writing software that is secure and 
> bug free as well as free and open source.

And totally devoid of any new functionality in.... maybe 8 years?
Actually I just went to look, it's 9 years. DJB isn't writing it, and hasn't
done since 1998. All the new functionality QMail has acquired since then has
been by way of a tangled web of third-party patches,

DJB is an excellent theorist, and has written very tight and bug-free code.
It has an admirable security record. It is also amost completely
comment-free, and not maintained in any way at all.

If you want Asterisk to stay still for 9 years, he's definitely your man.
Me, I'd prefer it to keep up with the times. The consequence of the 'release
early and often' principle of Open Source development is that stability
isn't always as good as it might be. You pay your money and take your
choice. And as with any Open Source project, we're all part of the team.

Peter

--
Peter Bowyer
Email: peter at bowyer.org