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: enhancements and bug fixing. which is a lot and has been going for
months and hundreds of hours of work and testing were put, so 2 is not
good enough, may be 4 or 5 (1 for each 25 build, after DB changes)
So, it is either 5.1.0 (no technology change, but DB tables changed,
using the latest build)
or, 5.0.5 (no technology change, no technology implemented within, so
many enhancements and bug fixing)
I prefer 5.1.0 as we do consider DB table change a major core
modification, and when SIP is implemented, 5.2.0 can be announced,
during this period you can announce 5.1.1... on regular bases depending
on build numbers.
And very important issue here is that data should be separated from code
and should be stated clearly in the installation manual.
On 11/20/20 10:45 AM, Maxim Solodovnik wrote:
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 <[email protected]
<mailto:[email protected]>> wrote:
On Fri, 20 Nov 2020 at 00:10, Ali Alhaidary
<[email protected] <mailto:[email protected]>>
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:
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 <[email protected]
<mailto:[email protected]>> wrote:
...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 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 <[email protected]
<mailto:[email protected]>> 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 Maxim,
>
>
> On 19/11/2020 02:53, Maxim Solodovnik wrote:
> > https://issues.apache.org/jira/browse/OPENMEETINGS-2514
> >
<https://issues.apache.org/jira/browse/OPENMEETINGS-2514>
> >
> > On Thu, 19 Nov 2020 at 08:27, Maxim Solodovnik <
> > [email protected] <mailto:[email protected]>
> > <mailto:[email protected]
<mailto:[email protected]>>> wrote:
> >
> >
> >
> > On Thu, 19 Nov 2020 at 00:08, kaffeesurrogat
> > <[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>
> > 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
> > entering a
> > personal room. Didn't test with other
rooms. It's the same
> > with the
> > guest invited. No need to give any
permissions. It just
> > happens ...
> >
> >
> > this is expected in room of type "conference"
> >
>
> stupid me, that was the difference between my
previous setup and my
> new
> setup .... sorry for that ....
>
> >
> >
> > 3) If i hit the unenrool user button in the
front end, the
> > connection
> > doesn't dissapear all the way. The video
and audio stream
> > of the
> > unenrolled user stops but the unenrolled
user stays in the
> > room and
> > still can use the pointer (google maps like
symbol) tool.
> > The Host sees the pointer blinking even
so the user
> > vanished from the
> > user list. The guest which was unenrolled
still has a full
> > list of users
> > cause he stays in the room.
> >
> >
> > this seems to be broken
> > please file JIRA
> >
>
> i will install the new build soon ....
>
>
> >
> >
> > 4) In the configuration menue the key
> > personal.rooms.enabled
> > vanished
> > after i set it to false. It did not showing
up again ;-(
> >
> >
> > this one I was unable to reproduce
> >
>
> personal.rooms.enabled is still gone .... will check
if i can
> reproduce
> this after reinstall ...
>
>
> Have fun,
>
> kaffeesurrogat
>
> >
> >
> >
> >
> > By the way,
> >
> > openmeetings is the best product ever ....
it is based on a
> > great
> > concept and helps a lot to do some online
teaching ....
> >
> >
> > Thanks :)
> >
> >
> >
> > Have fun,
> >
> > kaffeesurrogat
> >
> >
> >
> > ##################### installed version
> > ##############################
> >
> > Name
> > OpenMeetings
> > Version
> > 5.1.0-SNAPSHOT
> > Revision
> > b9b202a
> > Build date
> > 2020-11-18T09:35:56Z
> >
> > ##################### installed version
> > ##############################
> >
> >
> >
> > On 18/11/2020 17:47, Maxim Solodovnik wrote:
> > > 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
> >
> >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
> >
> >
> > --
> > Best regards,
> > Maxim
--
Best regards,
Maxim
--
Best regards,
Maxim
--
Best regards,
Maxim
