[OpenSIPS-Users] [RELEASES] Planing OpenSIPS 1.11.0 major release

[Bogdan-Andrei Iancu]

Hello all ,

We made a new evaluation of the thinks we plan to have ready for 1.11 
and time is not enough. In order to get a valuable and consistent 
release, the decision was to delay the 1.11 release for mid March - this 
will allow us to complete the ongoing tasks and have a really good set 
of features for 1.11

If there are any comments to this, please let us know.

Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 04.11.2013 19:58, Bogdan-Andrei Iancu wrote:
> Hi all,
>
> I would like to start a discussion about the next OpenSIPS major release
> - and in this discussion anyone is welcomed with options, ideas, critics
> and other. Your feedback is important to drive the project into a
> direction that reflects the user's needs!.
>
> So, I will list here the starting points, for both release planing and
> release content.
>
>
> Content
> -------
> What was done:
>          http://www.opensips.org/About/Version-1-11-0#toc2
> What is planned:
>          http://www.opensips.org/About/Version-1-11-0#toc9
> Planned items have priorities (for being addressed); it is a must to
> have all items done for the next release, as we need to fit into a time
> frame. Whatever is not done, will be left for the next release (1.12 ?)
>
> Additional thinks (not listed on web) we are considering are:
>      - new "call queuing" module
>      - new SMPP module
>      - async operations at script level (doing async db ops, exec, rest
> queries)
>      - dropping avpops module (and replacing with dbops module)
>      - simplify scripting/logic by dropping the usage of AVPs (defined as
> module params) in favor of explicit func. params
>      - better handling of UAC transactions (being able to set failure
> routes for them, to fire new requests from script)
>      - Quality routing in Dynamic Routing
> Also we target so work in the RTPProxy area (still under heavy planing)
> like restart persistence, replication and statistics .
>
>
> Planing
> -------
> Release candidate:
>      second half of January 2014, depending on the progress with the
> items to be done.
> Testing phase:
>      1 month allocated (it may be extended if critical problems show up)
> Stable release:
>      second half of February (after the testing phase is done).
>
>
> Once again, your feedback on these matters is important to us.
>
>
> Best regards,
>