<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Mon, Aug 26, 2013 at 6:17 AM, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net" target="_blank">oej@edvina.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div>26 aug 2013 kl. 13:04 skrev Jaco Kroon <<a href="mailto:jaco@uls.co.za" target="_blank">jaco@uls.co.za</a>>:</div>
<div><div class="h5"><br><blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF">
<div><font face="Helvetica, Arial,
sans-serif">Hi,<br>
<br>
</font>On 26/08/2013 08:17, Olle E. Johansson wrote:<br>
</div>
<blockquote type="cite">
<pre>25 aug 2013 kl. 20:36 skrev Sean Bright <a href="mailto:sean.bright@gmail.com" target="_blank"><sean.bright@gmail.com></a>:
</pre>
<blockquote type="cite">
<pre>On 8/25/2013 3:49 AM, Olle E. Johansson wrote:
</pre>
<blockquote type="cite">
<pre>I am grateful this happened and look forward to the 12 release - a developer pre-release of all this new code.
</pre>
</blockquote>
<pre>I'm confused - This is a standard release or some kind of technology preview release? What does "a developer pre-release" mean exactly?
</pre>
</blockquote>
<pre>What I'm saying is that I don't expect version 12 to be put in production anywhere. There's so many big changes that I personally see this as a pre-release for all third party developers to test and adapt their software to it, for all admins to test with their configurations and all of us to test and report and fix bugs, mistakes and add the missing parts. Because there will be issues with it. It's a whole new Asterisk.
Even parts like to old sip channel has gotten major changes in transfers and other parts. Don't expect any call to not touch new code.
We all need to work with this and make sure that we use it to build a great second generation Asterisk. Did you notice the large "2" in Matt's commit message? :-)
With "all" I mean the great Asterisk community - not only the Digium dev team. They did the bulk job building this, now all of us should contribute with testing, documentation, bug fixing and coding.
I'm hoping my customers will support me in this. Make sure you get time allocations during the fall to spend time on 12!</pre>
</blockquote>
Some of us are in the southern hemisphere!<br></div></blockquote></div></div>:-)</div><div class="im"><div><br><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF">
<br>
Can we expect a tagged release and archive in the form of an rc1
anywhere?<br></div></blockquote></div><br></div><div>We've just created a branch. Tagged releases will come :-) Have patience!</div><span class=""><font color="#888888"><div><br></div></font></span></div></blockquote>
<div><br></div><div style>To echo what Olle said, the goal of Asterisk 12 was to give people a platform to start the engineering of their next generation of communications applications. It's been our experience that people don't do this with Asterisk trunk - either for perception issues or due to it being too much of a "moving target" - so we put as much bang for the buck into Asterisk 12 as we could fit. With the scope and scale of the changes that were made in Asterisk 12, a lot of extra care and testing should be applied to it. It is definitely *not* a Long Term Support release. The focus was not on improving stability or the end user experience - it was on setting up the architecture to make Asterisk the right engine for communications for the next 10 years. There's a lot of work to do to make it both stable and usable enough to be called an LTS, and I'm looking forward to talking about those things at AstriDevCon this year.</div>
<div style><br></div><div style>None of that is to say that, after reviewing and _extensively_ testing Asterisk 12, you wouldn't decide to deploy it in some particular fashion. Some people certainly deployed Asterisk 10 in a similar fashion (dedicated fax gateways come to mind). It's just to say that you should approach it with the full knowledge of what it is, what changed in it, and what the risks are.</div>
</div><div><br></div><div style>Matt</div><div style><br></div>-- <br><div dir="ltr"><div>Matthew Jordan<br></div><div>Digium, Inc. | Engineering Manager</div><div>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA</div>
<div>Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a></div></div>
</div></div>