Juha, o Juha Heinanen on 08/28/2013 09:22 PM: > raphael, stefan, > > i'm lost regarding the different sems branches (rco/tcp-trsp, > sayer/1.4-spce3.0) and what is the fate of next stable sems release > 1.6. as Raphael already explained, sayer/1.4-spceX.Y are the SEMS versions which are the base for the SPCE from sipwise. We have done some developments specifically requested and sponsored by Sipwise (again many thanks to them by the way!), and all functionality was supposed to go also into master for inclusion to SEMS releases. This only has not happened yet with the two latest additions (UAS auth & 3891 through sbc), mostly because of the differences in the SBC.
> > is there some plan when 1.6 is released? will next stable release > include the above mentioned branches or are they part of some private > work? my intention is to do a 1.6 release in the next 1-3 months. all functionality from 1.4-spce3.0 will be included. apart from the above mentioned two items what is still also missing is to expose some sbc functionality to be usable through profile options, and documentation (though I think that real documentation could also come after the release; I'm fine with short pointers for the .0 release). Stefan _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
