1) it will be 3.1.0, no 3.0.7+. 3.1.0-RELEASE will have junit tests for
JSON/SOAP and will be compatible with public PHP API :)
2) Actually WebRTC will be 4.0.0, it is parallel task, we are currently
working in this direction :)

On Wed, Oct 28, 2015 at 5:13 PM, Peter Dähn <da...@vcrp.de> wrote:

> Hi Maxim,
>
> two Questions and Comments:
>
> 1. We won't get a 3.0.8? This means for us we will stay at 3.0.7 (+) till
> we get a working SOAP API that plays with OpenOLAT again. We could life
> with that right now. We will try to contribute, at least with testing new
> versions. By now we learnt a bit about the interaction between OpenOLAT an
> OpenMeetings. If we find time probably we can do a bit more here.
> 2. What does this mean for the development of OM with WebRTC? We would
> like to get rid of Flash asap... ;-) If it helps here, go ahead...
>
> Greetings Peter
>
>
>
> Am 28.10.2015 um 06:56 schrieb Maxim Solodovnik:
>
>> Hello All,
>>
>> I would like to propose
>> 1) create new branch 3.1.x based on 3.0.x
>> 2) change version of the trunk to 4.0.0-SNAPSHOT
>> 3) merge all API changes made in trunk to branch 3.1.x
>>
>> Why I think it is good:
>> 1) The code in trunk and branch 3.1.x will be closer (this will simplify
>> the development)
>> 2) We can get rid of unsupported Axis2 in favor of CXF
>> 3) We will get JSON REST API for free
>>
>> There is one huge drawback: current SOAP API being used by plugins will be
>> broken
>>
>> I'll fix publically available PHP API and Moodle plugin.
>>
>> What do you think?
>>
>>


-- 
WBR
Maxim aka solomax

Reply via email to