Hello,
using v4.0.0 for the next major release was proposed and debated at previous development IRC meeting. First was about the addition of a new transport layer (websockets) along with other important new features.
During the debate was touched the completion of kamailio-ser integration (no more duplicated modules) as another milestone for increasing the first digit (which was finished just before the end of last year). Now we also have the IMS modules, pushed in the GIT master branch few days ago.
It seems that there are lot of good reasons for numbering the next major version 4.0.0. Other comments, opinions?
Have a great and happy year ahead, Daniel
On 1/2/13 10:19 AM, Juha Heinanen wrote:
It seems that there are lot of good reasons for numbering the next major version 4.0.0. Other comments, opinions?
4.0 sounds good to me. what is the freeze date?
The plan is to freeze on Monday, next week, January 7. We can prolong development for few days if it is needed. I want to add internal hash table to track MSRP connections, hopefully I should be able to do it in time.
Cheers, Daniel
2 jan 2013 kl. 10:15 skrev Daniel-Constantin Mierla miconda@gmail.com:
Hello,
using v4.0.0 for the next major release was proposed and debated at previous development IRC meeting. First was about the addition of a new transport layer (websockets) along with other important new features.
During the debate was touched the completion of kamailio-ser integration (no more duplicated modules) as another milestone for increasing the first digit (which was finished just before the end of last year). Now we also have the IMS modules, pushed in the GIT master branch few days ago.
It seems that there are lot of good reasons for numbering the next major version 4.0.0. Other comments, opinions?
I agree with using 4.0.0 for the next release.
/O