[asterisk-dev] Asterisk 12 is branched

[Matthew Jordan]

On Mon, Aug 26, 2013 at 6:17 AM, Olle E. Johansson <oej at edvina.net> wrote:

>
> 26 aug 2013 kl. 13:04 skrev Jaco Kroon <jaco at uls.co.za>:
>
>  Hi,
>
> On 26/08/2013 08:17, Olle E. Johansson wrote:
>
> 25 aug 2013 kl. 20:36 skrev Sean Bright <sean.bright at gmail.com> <sean.bright at gmail.com>:
>
>
>  On 8/25/2013 3:49 AM, Olle E. Johansson wrote:
>
>  I am grateful this happened and look forward to the 12 release - a developer pre-release of all this new code.
>
>  I'm confused - This is a standard release or some kind of technology preview release?  What does "a developer pre-release" mean exactly?
>
>  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!
>
>  Some of us are in the southern hemisphere!
>
> :-)
>
>
> Can we expect a tagged release and archive in the form of an rc1 anywhere?
>
>
> We've just created a branch. Tagged releases will come :-) Have patience!
>
>
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.

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.

Matt

-- 
Matthew Jordan
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130826/250c7514/attachment.htm>