<br><br><div><span class="gmail_quote">On 4/15/06, <b class="gmail_sendername">Steve Underwood</b> <<a href="mailto:steveu@coppice.org">steveu@coppice.org</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> so (and with a little competition from projects like freeswitch) -<br>> it's getting better, but is still way too painful (unless you are<br>> already used to the pain of trying to get a arm patch into glibc, for
<br>> example). There are a bunch of out of tree modules that are<br>> effectively unowned now (format_mp3, chan_bluetooth) and a few worthy<br>> ones (like steve's fax work) that need some love from asterisk central
<br>> and more testers...<br><br>Nothing that matters to the majority of users, and fills the mailing<br>lists and IRC channels with problems - things like:<br> - robust echo control<br> - robust jitter management for all media streams
<br> - proper codec dependent handling of PLC, plus use of my generic PLC<br>by all media stream<br> - robust carriage of FAX across the PSTN interfaces<br> - T.38<br><br>really appear anywhere significant on the Asterisk development radar,
</blockquote><div><br><br></div></div>sure, quibbling over infinite loop syntax is like shifting deck chairs on<br>the Titantic (perversely I say why not just #define FOREVER for(;;) ?)<br><br>and making modules better is fairly trivial when there are way bigger fish to fry like jitterbuffers and plc.
<br><br>The amount of useful traffic on this list is at an all time low, and it's very painful reading the bugtracker...<br><br>Perhaps the new concall thing (<a href="http://www.asterisk.org/developers/conferencecalls/april-18-2006">
http://www.asterisk.org/developers/conferencecalls/april-18-2006</a>) will make things better.<br><br>I have some patience with where asterisk is at because it's still young as projects go and still breaking new ground everyday, and:
<br><br>A) I've been through things like the XFree86 -> <a href="http://x.org">x.org</a> transition, the linux kernel mess->bitkeeper->mess->git transition, and the glibc svn transition. All of which sucked heavily. I turned my back on graphics in 2003 entirely.
<br><br>B) I don't have any major patches of my own in the asterisk queue, and am not willing to try for any that I care about as that would raise my blood pressure significantly.<br><br>C) Most of the patches that I need are in test-this-branch. Olle's been very responsive.
<br><br>I'd be happiest with the 1.4 release date if it were based more on a quality metric than a date metric.<br><br>things like:<br><br>the paid-for features in the release (which I assume are things like jingle)<br>the top 90% of support questions by volume resolved by this release
<br>world class sip/rtp support (jitterbuffer/plc/fax)<br>clear roadmap for the missing bits (sip tcp for example)<br>cleaned up process for stability fixes<br>test scripts and test tools incorporated into the release<br>
people using oprofile/etc to improve scalability<br><br>-- <br>Mike Taht<br>PostCards From the Bleeding Edge<br><a href="http://the-edge.blogspot.com">http://the-edge.blogspot.com</a>