Hello Michael, According to my tests this version: https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.2.x/428/ Works much more stable, I see no errors or "blank pages" in my Moodle
Could you please check on your server? On Wed, Feb 1, 2017 at 12:40 AM, Maxim Solodovnik <[email protected]> wrote: > I was able to get "white page" > It is caused by failed WebSocket connection > Maybe you have WebSockets disabled? > Do you have any exceptions in OM logs? > > On Tue, Jan 31, 2017 at 8:39 PM, Maxim Solodovnik <[email protected]> > wrote: >> There should be no dashboard if you accessing room from Moodle >> I would appreciate any steps or maybe hints on how to configure this >> and be able to reproduce >> >> >> On Tue, Jan 31, 2017 at 4:45 PM, Michael Wuttke >> <[email protected]> wrote: >>> Hello, >>> >>> I've tested with FF and Chromium. And I enabled the OM Site in the >>> "Cookies settings". And reloaded the page. But like Peter described the >>> OM dashboard is empty, just the general chat is available. >>> >>> Thanks & Greetings, >>> Michael >>> >>> Am 31.01.2017 um 10:26 schrieb Peter Dähn: >>>> Hello, >>>> >>>> probably this one? >>>> >>>> https://issues.apache.org/jira/browse/OPENMEETINGS-1538 >>>> >>>> Greetings Peter >>>> >>>> Am 31.01.2017 um 10:12 schrieb Maxim Solodovnik: >>>>> Blank page is really weird ... >>>>> Any JS/Cookies errors in the browser >>>>> >>>>> Before latest change version should be set in 2 places (build.xml and >>>>> version.php) I see no reason to have these 2 versions, they are the >>>>> same >>>>> >>>>> On Tue, Jan 31, 2017 at 4:06 PM, Michael Wuttke >>>>> <[email protected]> wrote: >>>>>> Hello Maxim, >>>>>> >>>>>> I tested now the latest master branch and it does not work with >>>>>> moodle 3.0.8 and OM 3.2 RC1. I've got a blank page as well. I can only >>>>>> see the general chat. >>>>>> >>>>>> And what speaks against to set the version string to the version.php >>>>>> directly? >>>>>> >>>>>> Thanks & Greetings, >>>>>> Michael >>>>>> >>>>>> Am 31.01.2017 um 05:17 schrieb Maxim Solodovnik: >>>>>>> Hello Michael, >>>>>>> >>>>>>> master branch works for me with Moodle 3.0.4 >>>>>>> I have updated README with build instructions >>>>>>> Could you please check? >>>>>>> >>>>>>> On Mon, Jan 30, 2017 at 9:24 PM, Michael Wuttke >>>>>>> <[email protected]> wrote: >>>>>>>> Hello MAxim, >>>>>>>> >>>>>>>> thanks for your work, but the master branch does not work now with >>>>>>>> moodle 3.0 and OM 3.2. I've got a blank page and could only see the >>>>>>>> general chat. >>>>>>>> >>>>>>>> And please could you set the version string to the version.php for >>>>>>>> those >>>>>>>> how work only with github as code reposistory? >>>>>>>> >>>>>>>> Thanks & Greetings, >>>>>>>> Michael >>>>>>>> >>>>>>>> Am 30.01.2017 um 14:46 schrieb Maxim Solodovnik: >>>>>>>>> Hello Michael, >>>>>>>>> >>>>>>>>> I have updated plugin >>>>>>>>> master branch is updated to work with OM 3.2 >>>>>>>>> Additional branch 2.7.3.2 was created >>>>>>>>> >>>>>>>>> build was updated to automatically set version from build.xml to >>>>>>>>> version.php (with release date) >>>>>>>>> So now for these 2 branches version should be specified in one >>>>>>>>> place only >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Jan 30, 2017 at 8:27 AM, Maxim Solodovnik >>>>>>>>> <[email protected]> wrote: >>>>>>>>>> Hello Michael, >>>>>>>>>> >>>>>>>>>> plugin need to be updated >>>>>>>>>> this line [1] should be modified as follows >>>>>>>>>> -- $url = $gateway->getUrl() . "/swf?&secureHash=" . $hash >>>>>>>>>> -- . "&scopeRoomId=" . $openmeetings->om->room_id >>>>>>>>>> -- . "&language=" . $openmeetings->om->language; >>>>>>>>>> >>>>>>>>>> ++ $url = $gateway->getUrl() . "/hash?&secure=" . $hash >>>>>>>>>> ++ . "&language=" . $openmeetings->om->language; >>>>>>>>>> >>>>>>>>>> I'll create 3.2.0 compatible version later this week >>>>>>>>>> >>>>>>>>>> [1] >>>>>>>>>> https://github.com/openmeetings/openmeetings-moodle-plugin/blob/02b378e2b99504580143a6ca2c7a3dbb9e56c021/renderer.php#L123 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Jan 30, 2017 at 12:50 AM, Michael Wuttke >>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>> Hello Maxim, >>>>>>>>>>> >>>>>>>>>>> the upgrade works but the moodle om plugin not. It is possible >>>>>>>>>>> to create >>>>>>>>>>> a new room but not to enter a room. The om login page will be >>>>>>>>>>> shown always. >>>>>>>>>>> >>>>>>>>>>> Thanks & Greetings, >>>>>>>>>>> Michael >>>>>>>>>>> >>>>>>>>>>> Am 29.01.2017 um 17:00 schrieb Maxim Solodovnik: >>>>>>>>>>>> Hello Michael, >>>>>>>>>>>> >>>>>>>>>>>> Sure you can upgrade, the upgrade process is usual >>>>>>>>>>>> >>>>>>>>>>>> Backup everything >>>>>>>>>>>> Create db >>>>>>>>>>>> Restore >>>>>>>>>>>> >>>>>>>>>>>> Moodle plugin should work as expected >>>>>>>>>>>> >>>>>>>>>>>> WBR, Maxim >>>>>>>>>>>> (from mobile, sorry for the typos) >>>>>>>>>>>> >>>>>>>>>>>> On Jan 29, 2017 22:21, "Michael Wuttke" >>>>>>>>>>>> <[email protected] >>>>>>>>>>>> <mailto:[email protected]>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hello Maxim, >>>>>>>>>>>> >>>>>>>>>>>> two questions: >>>>>>>>>>>> - can I upgrade from OM 3.1.x to 3.2.0 or I have to >>>>>>>>>>>> install a new/fresh >>>>>>>>>>>> OM installation? >>>>>>>>>>>> - does the moodle om plugin some improvements? >>>>>>>>>>>> >>>>>>>>>>>> Thanks & Greetings, >>>>>>>>>>>> Michael >>>>>>>>>>>> >>>>>>>>>>>> Am 29.01.2017 um 08:52 schrieb Maxim Solodovnik: >>>>>>>>>>>> > I'm going to start 3.2.0 release :)) >>>>>>>>>>>> > >>>>>>>>>>>> > On Sat, Jan 28, 2017 at 11:44 AM, Maxim Solodovnik >>>>>>>>>>>> <[email protected] <mailto:[email protected]>> wrote: >>>>>>>>>>>> >> Hello All, >>>>>>>>>>>> >> >>>>>>>>>>>> >> I'm almost ready to start 3.2.0 release process, Any "last >>>>>>>>>>>> minute" issues? >>>>>>>>>>>> >> :))) >>>>>>>>>>>> >> >>>>>>>>>>>> >> Another question: Is it OK to drop 3.1.x support? i.e. >>>>>>>>>>>> 3.1.5 will >>>>>>>>>>>> be the >>>>>>>>>>>> >> last 3.1.x release >>>>>>>>>>>> >> >>>>>>>>>>>> >> On Tue, Jan 24, 2017 at 1:08 PM, Maxim Solodovnik >>>>>>>>>>>> <[email protected] <mailto:[email protected]>> >>>>>>>>>>>> >> wrote: >>>>>>>>>>>> >>> >>>>>>>>>>>> >>> Thanks for the report Sebastian! >>>>>>>>>>>> >>> I was able to reproduce and fix this issue >>>>>>>>>>>> >>> demo is updated >>>>>>>>>>>> >>> >>>>>>>>>>>> >>> please let me know if anything else is broken ... >>>>>>>>>>>> >>> >>>>>>>>>>>> >>> On Tue, Jan 24, 2017 at 7:56 AM, Maxim Solodovnik >>>>>>>>>>>> <[email protected] <mailto:[email protected]>> >>>>>>>>>>>> >>> wrote: >>>>>>>>>>>> >>>> Thanks Sebastian, >>>>>>>>>>>> >>>> I'll double-check >>>>>>>>>>>> >>>> It was ok during my test, maybe will ask for the steps >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> WBR, Maxim >>>>>>>>>>>> >>>> (from mobile, sorry for the typos) >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> On Jan 24, 2017 04:02, "[email protected] >>>>>>>>>>>> <mailto:[email protected]>" <[email protected] >>>>>>>>>>>> <mailto:[email protected]>> >>>>>>>>>>>> >>>> wrote: >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> Hi Maxim, >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> good work! I have seen some >>>>>>>>>>>> improvements/simplifications on the >>>>>>>>>>>> >>>> User-list. >>>>>>>>>>>> >>>> Less buttons. I think that is the right approach. >>>>>>>>>>>> Simpler user >>>>>>>>>>>> interface >>>>>>>>>>>> >>>> is >>>>>>>>>>>> >>>> better. >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> But I noticed that a bit of work is required in the >>>>>>>>>>>> Audio/Video >>>>>>>>>>>> >>>> settings. It >>>>>>>>>>>> >>>> works initially, but if you try to refresh (via the >>>>>>>>>>>> small icon >>>>>>>>>>>> in the >>>>>>>>>>>> >>>> video >>>>>>>>>>>> >>>> pod) or via triggering the modal/dialogue to choose >>>>>>>>>>>> different >>>>>>>>>>>> device >>>>>>>>>>>> >>>> settings via the user-list the video just becomes >>>>>>>>>>>> black and nothing >>>>>>>>>>>> >>>> happens >>>>>>>>>>>> >>>> anymore. Not possible to recover unless complete >>>>>>>>>>>> refresh of the >>>>>>>>>>>> browser. >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> I think that flow requires some attention. >>>>>>>>>>>> Audio/Video settings is >>>>>>>>>>>> >>>> pretty >>>>>>>>>>>> >>>> much our core functionality. >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> Cheers, >>>>>>>>>>>> >>>> Seb >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> 2017-01-24 0:53 GMT+13:00 Peter Dähn <[email protected] >>>>>>>>>>>> <mailto:[email protected]>>: >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> Hi Dimitriy, >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> node.js for server-side js is a huge package that >>>>>>>>>>>> need to handled >>>>>>>>>>>> >>>>> somehow... I also don't know if this would be the >>>>>>>>>>>> best solution... >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> webRTC browser2browser will not scale for private >>>>>>>>>>>> user and their >>>>>>>>>>>> >>>>> dsl-connection. So webRTC or SIP/RTMP to a >>>>>>>>>>>> mediaserver that then >>>>>>>>>>>> >>>>> multicasts >>>>>>>>>>>> >>>>> to all peers sounds like a way to move away from >>>>>>>>>>>> flash... I >>>>>>>>>>>> think this >>>>>>>>>>>> >>>>> is >>>>>>>>>>>> >>>>> already discussed. >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> Anyway I have no experience in this area and I was >>>>>>>>>>>> wondering >>>>>>>>>>>> that this >>>>>>>>>>>> >>>>> guy >>>>>>>>>>>> >>>>> mentions a "simple solution". >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> Greetings Peter >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> Am 23.01.2017 um 11:58 schrieb Dmitriy -: >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> Hello Peter, >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> I'm working on webRTC native client that can accept >>>>>>>>>>>> peer >>>>>>>>>>>> connection >>>>>>>>>>>> >>>>> from >>>>>>>>>>>> >>>>> browser. >>>>>>>>>>>> >>>>> We already have "serverlessmedia" solution "browser >>>>>>>>>>>> - to - >>>>>>>>>>>> browser" >>>>>>>>>>>> >>>>> with >>>>>>>>>>>> >>>>> our signal server in Java. >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> We're moving to "peer-to-media server-to-all other >>>>>>>>>>>> peers" >>>>>>>>>>>> solution. >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>>>> Do you know this guy? >>>>>>>>>>>> >>>>>>> https://github.com/muaz-khan >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> Yeah, I know him, and even have tried to use his >>>>>>>>>>>> library >>>>>>>>>>>> recordRTC. >>>>>>>>>>>> >>>>> Unfortunately, It allows to capture media stream ("live >>>>>>>>>>>> video") only in >>>>>>>>>>>> >>>>> Chrome. Firefox just produces only one big chunk, >>>>>>>>>>>> IE/Edge doesn't >>>>>>>>>>>> >>>>> support >>>>>>>>>>>> >>>>> video etc. >>>>>>>>>>>> >>>>> I tried many times to use pure JavaScript solution but >>>>>>>>>>>> libraries not >>>>>>>>>>>> >>>>> ready >>>>>>>>>>>> >>>>> for this purposes (MediaRecorder API and >>>>>>>>>>>> MediaSources API) yet >>>>>>>>>>>> and also >>>>>>>>>>>> >>>>> our >>>>>>>>>>>> >>>>> stack of technology doesn't permit to use JavaScript >>>>>>>>>>>> on the server >>>>>>>>>>>> >>>>> side. >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> On Mon, Jan 23, 2017 at 5:41 PM, Peter Dähn >>>>>>>>>>>> <[email protected] >>>>>>>>>>>> <mailto:[email protected]>> wrote: >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> I had a look around... >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> I found this one... >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>>>>>>>> http://stackoverflow.com/questions/20056683/webrtc-multicast-one-to-many >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> <http://stackoverflow.com/questions/20056683/webrtc-multicast-one-to-many> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> and the "simple solution can be peer-to-server model >>>>>>>>>>>> (peer-to-media >>>>>>>>>>>> >>>>>> server-to-all other peers)." >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> Do you know this guy? >>>>>>>>>>>> >>>>>> https://github.com/muaz-khan >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> Greetings Peter >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> Am 23.01.2017 um 10:43 schrieb Peter Dähn: >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> I thought the same about the general roadmap >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> 1st whiteborad (there was something in gsoc, right?) >>>>>>>>>>>> >>>>>> 2nd audio/video (also gsoc but not finally prototyped) >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> Lets have a look, if we could get some input (and >>>>>>>>>>>> feedback!) >>>>>>>>>>>> from such >>>>>>>>>>>> >>>>>> whish-list... >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> Am 23.01.2017 um 10:33 schrieb Maxim Solodovnik: >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> Wish list is good idea :) >>>>>>>>>>>> >>>>>> I guess it can be created from the list of JIRA >>>>>>>>>>>> issues, then >>>>>>>>>>>> discussed >>>>>>>>>>>> >>>>>> :) >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> My plans were to perform next steps to remove Flash >>>>>>>>>>>> :), >>>>>>>>>>>> >>>>>> 1) move WB to HTML5 >>>>>>>>>>>> >>>>>> 2) move Audio/Video ... >>>>>>>>>>>> >>>>>> last one seems to be tricky :( no POC yet :( >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> On Mon, Jan 23, 2017 at 4:28 PM, Peter Dähn >>>>>>>>>>>> <[email protected] >>>>>>>>>>>> <mailto:[email protected]>> wrote: >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> nothing critical, rooms are working so far... >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> We will collect a few things regarding usability >>>>>>>>>>>> and look >>>>>>>>>>>> and feel. >>>>>>>>>>>> >>>>>>> Unfortunatly by now no time is left... I think we >>>>>>>>>>>> will >>>>>>>>>>>> report this >>>>>>>>>>>> >>>>>>> using >>>>>>>>>>>> >>>>>>> Jira... >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> btw.. Is there a kind of wish-list to discuss new >>>>>>>>>>>> features/wishes and >>>>>>>>>>>> >>>>>>> probably get a ranking of things to implement or >>>>>>>>>>>> improve? >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> Greetings Peter >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> Am 23.01.2017 um 05:29 schrieb Maxim Solodovnik: >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> If no critical issues will be reported, I plan to >>>>>>>>>>>> pack RC1 on >>>>>>>>>>>> >>>>>>> Wednesday >>>>>>>>>>>> >>>>>>> Thanks for participating :) >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> On Sat, Jan 21, 2017 at 10:48 AM, Maxim Solodovnik >>>>>>>>>>>> >>>>>>> <[email protected] >>>>>>>>>>>> <mailto:[email protected]>> wrote: >>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>> >>>>>>>> Or maybe even better to correct >>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>> http://openmeetings.apache.org/themes-and-branding.html >>>>>>>>>>>> <http://openmeetings.apache.org/themes-and-branding.html> >>>>>>>>>>>> >>>>>>>> (Configuration -> >>>>>>>>>>>> >>>>>>>> User Interface -> Themes) >>>>>>>>>>>> >>>>>>>> And add section .... >>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>> >>>>>>>> On Fri, Jan 20, 2017 at 11:56 PM, Maxim Solodovnik >>>>>>>>>>>> >>>>>>>> <[email protected] >>>>>>>>>>>> <mailto:[email protected]>> wrote: >>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>> >>>>>>>>> I can add the page to >>>>>>>>>>>> >>>>>>>>> http://openmeetings.apache.org/ >>>>>>>>>>>> <http://openmeetings.apache.org/> >>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>> >>>>>>>>> Configuration -> Customization -> Styling >>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>> >>>>>>>>> What do you think would it be OK? >>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>> >>>>>>>>> On Fri, Jan 20, 2017 at 9:22 PM, Peter Dähn >>>>>>>>>>>> <[email protected] >>>>>>>>>>>> <mailto:[email protected]>> wrote: >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> ok... is this Info somewhere? Maybe it is >>>>>>>>>>>> enough to write >>>>>>>>>>>> it down >>>>>>>>>>>> >>>>>>>>>> in >>>>>>>>>>>> >>>>>>>>>> the documentation... >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> Am 20.01.2017 um 13:27 schrieb Maxim Solodovnik: >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> To provide custom styling/layout you can modify >>>>>>>>>>>> existing >>>>>>>>>>>> css files >>>>>>>>>>>> >>>>>>>>>> .... >>>>>>>>>>>> >>>>>>>>>> I can create empty "custom.css" and will add it >>>>>>>>>>>> to be >>>>>>>>>>>> included >>>>>>>>>>>> >>>>>>>>>> last, >>>>>>>>>>>> >>>>>>>>>> but I see not much sense in it .... >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> and you can do it as follows: >>>>>>>>>>>> >>>>>>>>>> 1) create webapps/openmeetings/css/custom.css file >>>>>>>>>>>> >>>>>>>>>> 2) open >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> webapps/openmeetings/WEB-INF/classes/org/apache/openmeetings/web/pages/BasePage.html >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> add link to your new CSS file >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> something like this :) >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> On Fri, Jan 20, 2017 at 6:15 PM, Peter Dähn >>>>>>>>>>>> <[email protected] <mailto:[email protected]>> wrote: >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> one more thing: is it possible to provide a >>>>>>>>>>>> custom.css >>>>>>>>>>>> file to >>>>>>>>>>>> >>>>>>>>>>> provide custom layout somehow? >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> Am 19.01.2017 um 06:42 schrieb Maxim Solodovnik: >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> Hello All, >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> I believe 3.2.0 should be released, I'm going >>>>>>>>>>>> to implement >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> https://issues.apache.org/jira/browse/OPENMEETINGS-1527 >>>>>>>>>>>> <https://issues.apache.org/jira/browse/OPENMEETINGS-1527> >>>>>>>>>>>> and would >>>>>>>>>>>> >>>>>>>>>>> like to >>>>>>>>>>>> >>>>>>>>>>> pack RC1 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> Please let me know if there are any critical >>>>>>>>>>>> issues. >>>>>>>>>>>> >>>>>>>>>>> (you can use our demo for tests: >>>>>>>>>>>> >>>>>>>>>>> https://om.alteametasoft.com:8443/next >>>>>>>>>>>> <https://om.alteametasoft.com:8443/next>) >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> And IMHO we need to switch main stable >>>>>>>>>>>> development branch to >>>>>>>>>>>> >>>>>>>>>>> 3.2.x >>>>>>>>>>>> >>>>>>>>>>> 3.1.5 can be released in a week or so with >>>>>>>>>>>> some critical >>>>>>>>>>>> >>>>>>>>>>> REST/SOAP >>>>>>>>>>>> >>>>>>>>>>> fixes >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> WDYT? >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>> WBR >>>>>>>>>>>> >>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>> WBR >>>>>>>>>>>> >>>>>>>>>> Maxim aka solomax >>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>> >>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>> WBR >>>>>>>>>>>> >>>>>>>>> Maxim aka solomax >>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>> >>>>>>>> -- >>>>>>>>>>>> >>>>>>>> WBR >>>>>>>>>>>> >>>>>>>> Maxim aka solomax >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>>>>>>>> >>>>>>> -- >>>>>>>>>>>> >>>>>>> WBR >>>>>>>>>>>> >>>>>>> Maxim aka solomax >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> >>>>>>>>>>>> >>>>>> -- >>>>>>>>>>>> >>>>>> WBR >>>>>>>>>>>> >>>>>> Maxim aka solomax >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> -- >>>>>>>>>>>> >>>>> Regards, >>>>>>>>>>>> >>>>> Dmitry Bezheckov. >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> -- >>>>>>>>>>>> >>>> Sebastian Wagner >>>>>>>>>>>> >>>> https://twitter.com/#!/dead_lock >>>>>>>>>>>> <https://twitter.com/#!/dead_lock> >>>>>>>>>>>> >>>> [email protected] <mailto:[email protected]> >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>>> >>>>>>>>>>>> >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> >>> -- >>>>>>>>>>>> >>> WBR >>>>>>>>>>>> >>> Maxim aka solomax >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> -- >>>>>>>>>>>> >> WBR >>>>>>>>>>>> >> Maxim aka solomax >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> WBR >>>>>>>>>> Maxim aka solomax >>> >> >> >> >> -- >> WBR >> Maxim aka solomax > > > > -- > WBR > Maxim aka solomax -- WBR Maxim aka solomax
