Re[2]: [DISCUSSION] REST/SOAP API break, version bumping

+1 "There is one huge drawback: current SOAP API being used by plugins will be broken" I think it's a small price to pay . Thanks! --- С уважением, Алексей Терехов. +7 926 076 15 20 >Воскресенье, 1 ноября 2015, 13:12 +06:00 от Maxim Solodovnik >: > >No votes

Re: [DISCUSSION] REST/SOAP API break, version bumping

No votes against this, so I'll do the changes Thanks! On Wed, Oct 28, 2015 at 5:22 PM, Vasiliy Degtyarev wrote: > Hello Maxim. > > Go ahead! > I will try to help you. > > Thanks, > Vasiliy > > > On 28.10.2015 11:56, Maxim Solodovnik wrote: > >> Hello All, >> >> I would like to

RE: [DISCUSSION] REST/SOAP API break, version bumping

of a cloud company Hunan Yun Zhong Man Bu Information Technology corp.Ltd 湖南云中漫步信息技术有限公司 Mobile phone: +86-13687359517 Fax: +86-731-88716009 From: Maxim Solodovnik Sent: 2015年11月1日 15:13 To: Openmeetings user-list Cc: dev Subject: Re: [DISCUSSION] REST/SOAP API break, version bumping No votes against

RE: [DISCUSSION] REST/SOAP API break, version bumping

ompany > Hunan Yun Zhong Man Bu Information Technology corp.Ltd > 湖南云中漫步信息技术有限公司 > Mobile phone: +86-13687359517 > Fax: +86-731-88716009 > > > > > > > *From: *Maxim Solodovnik > *Sent: *2015年11月1日 15:13 > *To: *Openmeetings user-list > *Cc: *dev > *Sub

Re: [DISCUSSION] REST/SOAP API break, version bumping

Hello Maxim. Go ahead! I will try to help you. Thanks, Vasiliy On 28.10.2015 11:56, Maxim Solodovnik wrote: 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

Re: [DISCUSSION] REST/SOAP API break, version bumping

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 wrote:

Re: [DISCUSSION] REST/SOAP API break, version bumping

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

[DISCUSSION] REST/SOAP API break, version bumping

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)