<div class="gmail_quote">On Wed, Dec 28, 2011 at 4:33 PM, Danny Nicholas <span dir="ltr"><<a href="mailto:danny@debsinc.com">danny@debsinc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I understand the "end of life" issue. What I fail to understand is that if<br>
1.8 is the "Cadillac" of Asterisk, why did they make 10.0 and why does 1.8<br>
have so many bugs (just what I read here, not from my actual experience)?<br></blockquote><div><br>Once released a version will only have bug and security fixes. New features go into trunk to be included in the next version. Asterisk has long term support releases like 1.4 and 1.8 and standard releases like 1.6 and 10. This model is no different than other software like Ubuntu.<br>
<br>Even though a series only has bug and security fixes I have found regressions occur between point releases. Just make sure to test thoroughly before putting a system in production. I tend to stick with a version until I need the features in a newer version or back porting a security fix becomes overly involved.<br>
<br>I have been running 1.8.7 with a few fixes back ported from the 1.8.8 release candidate for the last 2.5 months. The system processes around 4,000 calls per day over PRIs for 250 Polycom phones.<br><br>Previously I was running 1.6.1.18 with a bunch of back ports for fixes and features. Overall it was stable but every few months I had an issue where a channel would get hung. When this happened core show channels would crash the console and I would eventually have to restart Asterisk.<br>
<br>Ryan<br></div></div>