+1

Am 11.12.19 um 15:31 schrieb Daniel Ascher:
> +1
>
> On Wed, Dec 11, 2019 at 9:30 AM Alvaro <[email protected]> wrote:
>
>> +1
>>
>> -------------
>>
>> El mié, 11-12-2019 a las 20:02 +0700, Maxim Solodovnik escribió:
>>> Dear OpenMeetings Community,
>>>
>>> I would like to start a vote about releasing Apache OpenMeetings
>>> 5.0.0-M3 RC1
>>>
>>> Main changes are:
>>>
>>> Release 5.0.0-M3, provides following improvements:
>>>
>>> his release provides WebRTC audio/video/screen-sharing in the Room
>>> IMPORTANT: Java 11 is required
>>> Flash plugin is no more required in the browser
>>>
>>> Backup/Restore:
>>> * Multiple issues with restore were fixed
>>> * Confirmation of backup import was added
>>> * File/recording hashes are preserved when possible
>>>
>>> White board:
>>> * Document upload/conversion is improved
>>> * Whiteboards are not auto-created on room enter
>>> * Keyboard shortcut for quick poll is added
>>>
>>> Room:
>>> * User list is now sorted
>>>
>>> Audio/Video:
>>> * Multiple issues with audio/video/screen sharing are fixed
>>>
>>> Please NOTE: this version might be not production ready
>>>
>>> Some other fixes and improvements, 36 issues were addressed
>>>
>>> Readme: https://github.com/apache/openmeetings/blob/5.0.0-M3-RC1/READ
>>> ME.md
>>>
>>> Changelog: https://github.com/apache/openmeetings/blob/5.0.0-M3-RC1/C
>>> HANGELOG.md
>>>
>>> List of fixed issues:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231
>>> 2720&version=12345741
>>>
>>> Release artifacts:
>>> https://dist.apache.org/repos/dist/dev/openmeetings/5.0.0-M3/rc1/
>>>
>>> Maven Staged repo:
>>> https://repository.apache.org/service/local/repositories/orgapacheope
>>> nmeetings-1045/content/
>>>
>>> Tag: https://github.com/apache/openmeetings/tree/5.0.0-M3-RC1
>>>
>>> PGP release keys (signed using 8456901E):
>>> https://www.apache.org/dist/openmeetings/KEYS
>>>
>>> Vote will be open for 72 hours.
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> My vote is +1.
>

Reply via email to