<div class="gmail_quote">On Thu, May 5, 2011 at 4:07 PM, Paul Belanger <span dir="ltr"><<a href="mailto:pabelanger@digium.com">pabelanger@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 11-05-05 12:30 PM, Ira wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
At 07:56 AM 5/5/2011, you wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So how can we fix this? How can we get more people involded? What<br>
makes projects like FedoraTesting[3] and DebianTesting[4] popular? How<br>
can the Asterisk project reproduce their success?<br>
</blockquote>
<br>
Well, it's not a lot of people willing to run beta software on their<br>
phone system. Phones need to work and for most people they need to work<br>
perfectly all the time. I'm one of those oddities that will always run<br>
beta software if given the chance but my experience is that quite rare.<br>
<br>
</blockquote></div>
I am not saying using production servers to test, rather reproducing your production setups in a test environment. You would then create test plans or test cases of the features you use in Asterisk. Once documented, for each and every RC of Asterisk you go through the steps outlined in your test plan / case, confirming this work as expected and then documenting the results.<div class="im">
<br><br></div></blockquote><div>Not everyone has spare dahdi hardware / analog T circuits, but I agree.</div></div>