Re: [DISCUSSION] release current 5.1.0 as 5.0.2

; > about this . > > > > > > > > > > > > > > > > > > > > > > > > Right now, the dragable button to resize the screen-sharing > > > > > > display is > > > > > > > > >

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

t size? > > (preserving aspect ratio? > > > > On Fri, 20 Nov 2020 at 20:53, kaffeesurrogat > <mailto:kaffeesurro...@posteo.de>> wrote: > > > > sorry maxim, send this message directly to you not to the list. > > need to > >

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

out of the monitor screen. You can hit minimize, then use the > > > > dragable > > > > > > > > resize button and then unminize. > > > > > > > > But that's something I need to explain to people on the > > > > receiving side

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

t; (preserving aspect ratio? > > > > On Fri, 20 Nov 2020 at 20:53, kaffeesurrogat > <mailto:kaffeesurro...@posteo.de>> wrote: > > > > sorry maxim, send this message directly to you not to the list. > > need to > > learn how to use thunderbird > > &

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

very often they don't get it > > > > > > > > > > > > > > > > many thanks Maxim, > > > > > > > > kaffeesurrogat > > > > > > > > > better solution would be to address OPENMEETING

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

be to address OPENMEETINGS-2000 but i'm not sure how >> > would it be OK if all video pods will be displayed of constant size? >> > (preserving aspect ratio? >> > >> > On Fri, 20 Nov 2020 at 20:53, kaffeesurrogat > > <mailto:kaffeesurro...@posteo.de>> wrote: >> > &

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

ll video pods will be displayed of constant size? > > (preserving aspect ratio? > > > > On Fri, 20 Nov 2020 at 20:53, kaffeesurrogat > <mailto:kaffeesurro...@posteo.de>> wrote: > > > > sorry maxim, send this message directly to you not to the list. > &

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

size? > (preserving aspect ratio? > > On Fri, 20 Nov 2020 at 20:53, kaffeesurrogat <mailto:kaffeesurro...@posteo.de>> wrote: > > sorry maxim, send this message directly to you not to the list. > need to > learn how to use thunderbird > > >

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

l video pods will be displayed of constant size? (preserving aspect ratio? On Fri, 20 Nov 2020 at 20:53, kaffeesurrogat wrote: > sorry maxim, send this message directly to you not to the list. need to > learn how to use thunderbird > > > Forwarded Message ---- > Subject:

Fwd: [DISCUSSION] release current 5.1.0 as 5.0.2

sorry maxim, send this message directly to you not to the list. need to learn how to use thunderbird Forwarded Message Subject:Re: [DISCUSSION] release current 5.1.0 as 5.0.2 Date: Fri, 20 Nov 2020 14:48:39 +0100 From: kaffeesurrogat Reply-To: kaffeesurro

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On Fri, 20 Nov 2020 at 20:28, kaffeesurrogat wrote: > Dear Maxim, > > > On 20/11/2020 13:09, Maxim Solodovnik wrote: > > > > > > On Fri, 20 Nov 2020 at 18:53, kaffeesurrogat > > wrote: > > > > Hi Everybody, > > > > is it a bug or a feature ? > > > > I

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

:-) On 11/20/20 4:05 PM, Maxim Solodovnik wrote: I guess we will made everybody's life easier if we move to the simpler versioning So let it be - 5.1.0 - 6.0.0 Are there any objections? (minors will be for the "super fast" security fixed, like it was with 5.0.1 :))) On Fri, 20 Nov 2020 at 1

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

I guess we will made everybody's life easier if we move to the simpler versioning So let it be - 5.1.0 - 6.0.0 Are there any objections? (minors will be for the "super fast" security fixed, like it was with 5.0.1 :))) On Fri, 20 Nov 2020 at 19:29, Ali Alhaidary wrote: > True, but that is becaus

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

True, but that is because they have merged x and y together for long period of time, but internally you might find a.b.c.x.y.z ... On 11/20/20 3:12 PM, Maxim Solodovnik wrote: On Fri, 20 Nov 2020 at 18:53, Ali Alhaidary mailto:ali.alhaid...@the5stars.org>> wrote: I assume that x.y.z is

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On Fri, 20 Nov 2020 at 18:53, Ali Alhaidary wrote: > I assume that x.y.z is: > It depends :)) modern software has higher majors than old days :))) you can check for example browser versions :)) > x: major technology change: as 4 to 5 moving from flash to WebRTC, so 5 > stays. > y: introducing

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On Fri, 20 Nov 2020 at 18:53, kaffeesurrogat wrote: > Hi Everybody, > > is it a bug or a feature ? > > I'm running: > > > Name > OpenMeetings > Version > 5.1.0-SNAPSHOT > Revision > b9b202a > Build date > 2020-11-18T09:35:56Z > > Previous versions offered to set the screen size before starting sc

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

I assume that x.y.z is: x: major technology change: as 4 to 5 moving from flash to WebRTC, so 5 stays. y: introducing new functionality or big code change, since SIP is not implemented yet, 0 stays, unless considering tables DB change that is not compatible with 0, so it should be 1. z: enhanc

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

Hi Everybody, is it a bug or a feature ? I'm running: Name OpenMeetings Version 5.1.0-SNAPSHOT Revision b9b202a Build date 2020-11-18T09:35:56Z Previous versions offered to set the screen size before starting screen shares. This option is gone. I would love have it back ... ;-) Screen share fr

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

El vie, 20-11-2020 a las 09:51 +0100, Alvaro escribió: > BTW we can update the versioningrelease 5.1.0 "as is"and if/when SIP > will be ready release 6.0.0 : ...this is. .

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

...This is a good idea . El vie, 20-11-2020 a las 14:45 +0700, Maxim Solodovnik escribió: > BTW we can update the versioningrelease 5.1.0 "as is" > and if/when SIP will be ready release 6.0.0 : > > WDYT? > > On Fri, 20 Nov 2020 at 14:44, Maxim Solodovnik > wrote:

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

BTW we can update the versioning release 5.1.0 "as is" and if/when SIP will be ready release 6.0.0 : WDYT? On Fri, 20 Nov 2020 at 14:44, Maxim Solodovnik wrote: > > > On Fri, 20 Nov 2020 at 00:10, Ali Alhaidary > wrote: > >> So 5.0.2 will be based on the latest build of 5.1.0, and you will

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On Fri, 20 Nov 2020 at 00:10, Ali Alhaidary wrote: > So 5.0.2 will be based on the latest build of 5.1.0, and you will keep > working on 5.1.0 snapshots ? > 5.0.2 will be based on _some_ build 5.1.0 is delayed due to SIP integration is not ready :( > On 11/19/20 7:21 PM, Maxim Solodovnik wrote

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

..Ok, Thank you! .. El jue, 19-11-2020 a las 23:21 +0700, Maxim Solodovnik escribió: > yesI would like to release 5.0.2 in a week or so > It will be based on current master > > there should be lot's of time to do some more testing > and maybe fix some bugs :))) > > > > On Thu, 19

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

So 5.0.2 will be based on the latest build of 5.1.0, and you will keep working on 5.1.0 snapshots ? On 11/19/20 7:21 PM, Maxim Solodovnik wrote: yes I would like to release 5.0.2 in a week or so It will be based on current master there should be lot's of time to do some more testing and maybe

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

yes I would like to release 5.0.2 in a week or so It will be based on current master there should be lot's of time to do some more testing and maybe fix some bugs :))) On Thu, 19 Nov 2020 at 23:09, Alvaro wrote: > ...sorry you know how is my english. Then, that is a yes or a not? > > .

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

...sorry you know how is my english. Then, that is a yes or a not? ... El jue, 19-11-2020 a las 23:03 +0700, Maxim Solodovnik escribió: > I saw no votes against itso let it be 5.0.2 - another bug fix release > for 5.0.0 :))) > > On Thu, 19 Nov 2020 at 22:39, Alvaro wrote: > > ...

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

I saw no votes against it so let it be 5.0.2 - another bug fix release for 5.0.0 :))) On Thu, 19 Nov 2020 at 22:39, Alvaro wrote: > > ...Maxim, then the next release will be called 5.0.2? > > Thanks > > . > > El jue, 19-11-2020 a las 08:17 +0100, kaffeesurrogat escribió: > > Hi M

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

...Maxim, then the next release will be called 5.0.2? Thanks . El jue, 19-11-2020 a las 08:17 +0100, kaffeesurrogat escribió: > Hi Maxim, > > > On 19/11/2020 02:53, Maxim Solodovnik wrote: > > https://issues.apache.org/jira/browse/OPENMEETINGS-2514 > >

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

Hi Maxim, On 19/11/2020 02:53, Maxim Solodovnik wrote: > https://issues.apache.org/jira/browse/OPENMEETINGS-2514 > > > On Thu, 19 Nov 2020 at 08:27, Maxim Solodovnik > wrote: > > > > On Thu, 19 Nov 2020

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

For us, 3-5 rooms a time, 5-7 users per room Audio only, screen sharing and recording Server is in Germany and users are around the globe OM is stable/usable So, why not ;-) On 11/18/20 7:47 PM, Maxim Solodovnik wrote: Hello All, ATM we have 39 JIRA issues addressed I would like to releas

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

https://issues.apache.org/jira/browse/OPENMEETINGS-2514 On Thu, 19 Nov 2020 at 08:27, Maxim Solodovnik wrote: > > > On Thu, 19 Nov 2020 at 00:08, kaffeesurrogat > wrote: > >> Hi Maxim, >> >> just installed your latest build. Some things I like to address . >> >> >> 1) The frontelements for

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On Thu, 19 Nov 2020 at 00:08, kaffeesurrogat wrote: > Hi Maxim, > > just installed your latest build. Some things I like to address . > > > 1) The frontelements for invited users in a password protected room are > back > > Many thanks ... ;-) > > 2) The camera/audio connections starts as soon

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

...then Maxim, the next release will be 5.0.2...no 5.1.0. Is it right? El mié, 18-11-2020 a las 23:47 +0700, Maxim Solodovnik escribió: > Hello All, > ATM we have 39 JIRA issues addressed > I would like to release 5.0.2 based on current 5.1.0-SNAPSHOT in a > week or so >

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On 18/11/2020 18:07, kaffeesurrogat wrote: > Hi Maxim, > > just installed your latest build. Some things I like to address . > > > 1) The frontelements for invited users in a password protected room are back > > Many thanks ... ;-) > > 2) The camera/audio connections starts as soon as i'm en

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

Hi Maxim, just installed your latest build. Some things I like to address . 1) The frontelements for invited users in a password protected room are back Many thanks ... ;-) 2) The camera/audio connections starts as soon as i'm entering a personal room. Didn't test with other rooms. It's th

[DISCUSSION] release current 5.1.0 as 5.0.2

Hello All, ATM we have 39 JIRA issues addressed I would like to release 5.0.2 based on current 5.1.0-SNAPSHOT in a week or so implementation of SIP is moving slow, so one-two intermediate releases might be good idea What do you think? -- Best regards, Maxim