You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Maxim Solodovnik <so...@gmail.com> on 2020/07/21 02:56:56 UTC

Time to release :)

Hello All,

I had plans to fix OPENMEETINGS-2402 before release but it seems to take
too much time already
I would like to release, then do some fixes, improvements
Please let me know if you see any show-stoppers

Thanks!

-- 
Best regards,
Maxim

Re: Time to release :)

Posted by Alvaro <zu...@gmail.com>.
Thank you!



..............


El mar, 21-07-2020 a las 16:06 +0700, Maxim Solodovnik escribió:
> yes :)
> On Tue, 21 Jul 2020 at 16:06, Alvaro <zu...@gmail.com> wrote:
> > ...then Maxim, snapshot OM 5.0.0 - 3252 it is the lastbefore
> > release?
> > 
> > 
> > ................
> > El mar, 21-07-2020 a las 09:56 +0700, Maxim Solodovnik escribió:
> > > Hello All,
> > > I had plans to fix OPENMEETINGS-2402 before release but it seems
> > > to take too much time already
> > > I would like to release, then do some fixes, improvements
> > > Please let me know if you see any show-stoppers
> > > 
> > > Thanks!
> > > 
> > > -- 
> > > Best regards,
> > > Maxim
> 
> -- 
> Best regards,
> Maxim
> 

Re: Time to release :)

Posted by Maxim Solodovnik <so...@gmail.com>.
yes :)

On Tue, 21 Jul 2020 at 16:06, Alvaro <zu...@gmail.com> wrote:

> ...then Maxim, snapshot OM 5.0.0 - 3252 it is the last
> before release?
>
>
>
> ................
>
> El mar, 21-07-2020 a las 09:56 +0700, Maxim Solodovnik escribió:
>
> Hello All,
>
> I had plans to fix OPENMEETINGS-2402 before release but it seems to take
> too much time already
> I would like to release, then do some fixes, improvements
> Please let me know if you see any show-stoppers
>
> Thanks!
>
> --
> Best regards,
> Maxim
>
>

-- 
Best regards,
Maxim

Re: Time to release :)

Posted by Alvaro <zu...@gmail.com>.
...then Maxim, snapshot OM 5.0.0 - 3252 it is the last
before release?



................

El mar, 21-07-2020 a las 09:56 +0700, Maxim Solodovnik escribió:
> Hello All,
> I had plans to fix OPENMEETINGS-2402 before release but it seems to
> take too much time already
> I would like to release, then do some fixes, improvements
> Please let me know if you see any show-stoppers
> 
> Thanks!
> 
> -- 
> Best regards,
> Maxim
> 

Re: Time to release :)

Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks :)

(from mobile, sorry for typos)

On Wed, Jul 29, 2020, 22:08 Alvaro <zu...@gmail.com> wrote:

> Enjoy your trip...
>
>
> ..............
>
>
> El mié, 29-07-2020 a las 21:56 +0700, Maxim Solodovnik escribió:
>
> It's Wed already,
> I will be absent since Sat night, so, I can start the release process only
> when I get back from my trip
> Or someone else can be release manager :)
>
> p.s. will patch and prepare release of 4.0.x on return
> p.p.s please expect loooong delay in my answers :)))
>
> On Mon, 27 Jul 2020 at 04:19, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
> Lets open a new thread, I think there is some value in having a separated
> Safari/iOS chat.
>
> Thanks,
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Sat, 25 Jul 2020 at 19:14, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
> But yeah something is truly odd with Safari.
>
> The same samples from the webRTC samples section:
> https://webrtc.github.io/samples/src/content/getusermedia/audio/
> => Works in Chrome/iOS
> => Fails in Safari/iOS
>
> It's pretty much the same symptoms as described here:
> https://discussions.apple.com/thread/8510720
>
> Cheers
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Sat, 25 Jul 2020 at 12:01, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
> The audio/video testing tool actually also doesn't work for Safari.
> So maybe fixing up that may help before finding out why the overall
> conference room doesn't work.
>
> I've created https://issues.apache.org/jira/browse/OPENMEETINGS-2412
>
> Thanks,
> Seb
>
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Sat, 25 Jul 2020 at 11:08, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
> I was hoping updating kurento-utils would help. Unfortunate it doesn't
> seem so.
>
> There is a page from kurento project around Safari in particular:
> https://doc-kurento.readthedocs.io/en/6.14.0/knowledge/safari.html
>
> Our particular issue is that you can't publish audio using Safari/iOS.
> Which is a bit different from the above errors.
>
> On the other hand there are examples of working code, including Safari, on
> https://webrtc.github.io/samples/
> For example a simple:
>
>    - Choose camera, microphone and speaker
>    <https://webrtc.github.io/samples/src/content/devices/input-output/>
>
>
> => That example seems to works fine on Safari/iOS for publishing audio
>
> Thanks
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Wed, 22 Jul 2020 at 02:11, Jason <ja...@romos.net> wrote:
>
> So far the main things I have seen is safari users and  iPad users can’t
> use audio.  iPad no browsers work to get around the audio issue.  It seems
> they changed how to select audio devices.
>
> J
>
>
>
> On Monday, Jul 20, 2020 at 9:58 PM, Maxim Solodovnik <so...@gmail.com>
> wrote:
> Hello All,
>
> I had plans to fix OPENMEETINGS-2402 before release but it seems to take
> too much time already
> I would like to release, then do some fixes, improvements
> Please let me know if you see any show-stoppers
>
> Thanks!
>
> --
> Best regards,
> Maxim
>
>
>
>
>
>
>
>
> --
> Best regards,
> Maxim
>
>

Re: Time to release :)

Posted by Alvaro <zu...@gmail.com>.
Enjoy your trip...

..............

El mié, 29-07-2020 a las 21:56 +0700, Maxim Solodovnik escribió:
> It's Wed already,I will be absent since Sat night, so, I can start
> the release process only when I get back from my trip
> Or someone else can be release manager :)
> 
> p.s. will patch and prepare release of 4.0.x on return
> p.p.s please expect loooong delay in my answers :)))
> On Mon, 27 Jul 2020 at 04:19, seba.wagner@gmail.com <seba.wagner@gmai
> l.com> wrote:
> > Lets open a new thread, I think there is some value in having a
> > separated Safari/iOS chat.
> > Thanks,
> > Seb
> > 
> > Sebastian Wagner
> > Director Arrakeen Solutions
> > http://arrakeen-solutions.co.nz/
> > 
> > 
> > 
> > 
> > On Sat, 25 Jul 2020 at 19:14, seba.wagner@gmail.com <seba.wagner@gm
> > ail.com> wrote:
> > > But yeah something is truly odd with Safari.
> > > The same samples from the webRTC samples section: https://webrtc.
> > > github.io/samples/src/content/getusermedia/audio/
> > > => Works in Chrome/iOS
> > > => Fails in Safari/iOS
> > > 
> > > It's pretty much the same symptoms as described here: 
> > > https://discussions.apple.com/thread/8510720
> > > 
> > > Cheers
> > > Seb
> > > 
> > > Sebastian Wagner
> > > Director Arrakeen Solutions
> > > http://arrakeen-solutions.co.nz/
> > > 
> > > 
> > > 
> > > 
> > > On Sat, 25 Jul 2020 at 12:01, seba.wagner@gmail.com <seba.wagner@
> > > gmail.com> wrote:
> > > > The audio/video testing tool actually also doesn't work for
> > > > Safari.So maybe fixing up that may help before finding out why
> > > > the overall conference room doesn't work.
> > > > 
> > > > I've created https://issues.apache.org/jira/browse/OPENMEETINGS
> > > > -2412
> > > > 
> > > > Thanks,
> > > > Seb
> > > > 
> > > > 
> > > > Sebastian Wagner
> > > > Director Arrakeen Solutions
> > > > http://arrakeen-solutions.co.nz/
> > > > 
> > > > 
> > > > 
> > > > 
> > > > On Sat, 25 Jul 2020 at 11:08, seba.wagner@gmail.com <seba.wagne
> > > > r@gmail.com> wrote:
> > > > > I was hoping updating kurento-utils would help. Unfortunate
> > > > > it doesn't seem so.
> > > > > 
> > > > > There is a page from kurento project around Safari in
> > > > > particular:
> > > > > https://doc-kurento.readthedocs.io/en/6.14.0/knowledge/safari
> > > > > .html
> > > > > 
> > > > > Our particular issue is that you can't publish audio using
> > > > > Safari/iOS. Which is a bit different from the above errors.
> > > > > 
> > > > > On the other hand there are examples of working code,
> > > > > including Safari, on https://webrtc.github.io/samples/
> > > > > For example a simple: 
> > > > > Choose camera, microphone and speaker
> > > > > => That example seems to works fine on Safari/iOS for
> > > > > publishing audio 
> > > > > 
> > > > > Thanks
> > > > > Seb
> > > > > 
> > > > > Sebastian Wagner
> > > > > Director Arrakeen Solutions
> > > > > http://arrakeen-solutions.co.nz/
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > On Wed, 22 Jul 2020 at 02:11, Jason <ja...@romos.net> wrote:
> > > > > >       So far the main things I have seen is safari users
> > > > > > and  iPad users can’t use audio.  iPad no browsers work to
> > > > > > get around the audio issue.  It seems they changed how to
> > > > > > select audio devices.
> > > > > > J 
> > > > > >     
> > > > > >  
> > > > > >        On Monday, Jul 20, 2020 at 9:58 PM, Maxim Solodovnik
> > > > > > <so...@gmail.com> wrote:
> > > > > >  Hello All,
> > > > > > I had plans to fix OPENMEETINGS-2402 before release but it
> > > > > > seems to take too much time already
> > > > > > I would like to release, then do some fixes, improvements
> > > > > > Please let me know if you see any show-stoppers
> > > > > > 
> > > > > > Thanks!
> > > > > > 
> > > > > > -- 
> > > > > > Best regards,
> > > > > > Maxim    
> 
> -- 
> Best regards,
> Maxim

Re: Time to release :)

Posted by Maxim Solodovnik <so...@gmail.com>.
It's Wed already,
I will be absent since Sat night, so, I can start the release process only
when I get back from my trip
Or someone else can be release manager :)

p.s. will patch and prepare release of 4.0.x on return
p.p.s please expect loooong delay in my answers :)))

On Mon, 27 Jul 2020 at 04:19, seba.wagner@gmail.com <se...@gmail.com>
wrote:

> Lets open a new thread, I think there is some value in having a separated
> Safari/iOS chat.
>
> Thanks,
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Sat, 25 Jul 2020 at 19:14, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
>> But yeah something is truly odd with Safari.
>>
>> The same samples from the webRTC samples section:
>> https://webrtc.github.io/samples/src/content/getusermedia/audio/
>> => Works in Chrome/iOS
>> => Fails in Safari/iOS
>>
>> It's pretty much the same symptoms as described here:
>> https://discussions.apple.com/thread/8510720
>>
>> Cheers
>> Seb
>>
>> Sebastian Wagner
>> Director Arrakeen Solutions
>> http://arrakeen-solutions.co.nz/
>>
>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>>
>>
>> On Sat, 25 Jul 2020 at 12:01, seba.wagner@gmail.com <
>> seba.wagner@gmail.com> wrote:
>>
>>> The audio/video testing tool actually also doesn't work for Safari.
>>> So maybe fixing up that may help before finding out why the overall
>>> conference room doesn't work.
>>>
>>> I've created https://issues.apache.org/jira/browse/OPENMEETINGS-2412
>>>
>>> Thanks,
>>> Seb
>>>
>>>
>>> Sebastian Wagner
>>> Director Arrakeen Solutions
>>> http://arrakeen-solutions.co.nz/
>>>
>>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
>>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>>>
>>>
>>> On Sat, 25 Jul 2020 at 11:08, seba.wagner@gmail.com <
>>> seba.wagner@gmail.com> wrote:
>>>
>>>> I was hoping updating kurento-utils would help. Unfortunate it doesn't
>>>> seem so.
>>>>
>>>> There is a page from kurento project around Safari in particular:
>>>> https://doc-kurento.readthedocs.io/en/6.14.0/knowledge/safari.html
>>>>
>>>> Our particular issue is that you can't publish audio using Safari/iOS.
>>>> Which is a bit different from the above errors.
>>>>
>>>> On the other hand there are examples of working code, including Safari,
>>>> on https://webrtc.github.io/samples/
>>>> For example a simple:
>>>>
>>>>    - Choose camera, microphone and speaker
>>>>    <https://webrtc.github.io/samples/src/content/devices/input-output/>
>>>>
>>>>
>>>> => That example seems to works fine on Safari/iOS for publishing audio
>>>>
>>>> Thanks
>>>> Seb
>>>>
>>>> Sebastian Wagner
>>>> Director Arrakeen Solutions
>>>> http://arrakeen-solutions.co.nz/
>>>>
>>>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
>>>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>>>>
>>>>
>>>> On Wed, 22 Jul 2020 at 02:11, Jason <ja...@romos.net> wrote:
>>>>
>>>>> So far the main things I have seen is safari users and  iPad users
>>>>> can’t use audio.  iPad no browsers work to get around the audio issue.  It
>>>>> seems they changed how to select audio devices.
>>>>>
>>>>> J
>>>>>
>>>>>
>>>>>
>>>>> On Monday, Jul 20, 2020 at 9:58 PM, Maxim Solodovnik <
>>>>> solomax666@gmail.com> wrote:
>>>>> Hello All,
>>>>>
>>>>> I had plans to fix OPENMEETINGS-2402 before release but it seems to
>>>>> take too much time already
>>>>> I would like to release, then do some fixes, improvements
>>>>> Please let me know if you see any show-stoppers
>>>>>
>>>>> Thanks!
>>>>>
>>>>> --
>>>>> Best regards,
>>>>> Maxim
>>>>>
>>>>>

-- 
Best regards,
Maxim

Re: Time to release :)

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Lets open a new thread, I think there is some value in having a separated
Safari/iOS chat.

Thanks,
Seb

Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>


On Sat, 25 Jul 2020 at 19:14, seba.wagner@gmail.com <se...@gmail.com>
wrote:

> But yeah something is truly odd with Safari.
>
> The same samples from the webRTC samples section:
> https://webrtc.github.io/samples/src/content/getusermedia/audio/
> => Works in Chrome/iOS
> => Fails in Safari/iOS
>
> It's pretty much the same symptoms as described here:
> https://discussions.apple.com/thread/8510720
>
> Cheers
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Sat, 25 Jul 2020 at 12:01, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
>> The audio/video testing tool actually also doesn't work for Safari.
>> So maybe fixing up that may help before finding out why the overall
>> conference room doesn't work.
>>
>> I've created https://issues.apache.org/jira/browse/OPENMEETINGS-2412
>>
>> Thanks,
>> Seb
>>
>>
>> Sebastian Wagner
>> Director Arrakeen Solutions
>> http://arrakeen-solutions.co.nz/
>>
>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>>
>>
>> On Sat, 25 Jul 2020 at 11:08, seba.wagner@gmail.com <
>> seba.wagner@gmail.com> wrote:
>>
>>> I was hoping updating kurento-utils would help. Unfortunate it doesn't
>>> seem so.
>>>
>>> There is a page from kurento project around Safari in particular:
>>> https://doc-kurento.readthedocs.io/en/6.14.0/knowledge/safari.html
>>>
>>> Our particular issue is that you can't publish audio using Safari/iOS.
>>> Which is a bit different from the above errors.
>>>
>>> On the other hand there are examples of working code, including Safari,
>>> on https://webrtc.github.io/samples/
>>> For example a simple:
>>>
>>>    - Choose camera, microphone and speaker
>>>    <https://webrtc.github.io/samples/src/content/devices/input-output/>
>>>
>>>
>>> => That example seems to works fine on Safari/iOS for publishing audio
>>>
>>> Thanks
>>> Seb
>>>
>>> Sebastian Wagner
>>> Director Arrakeen Solutions
>>> http://arrakeen-solutions.co.nz/
>>>
>>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
>>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>>>
>>>
>>> On Wed, 22 Jul 2020 at 02:11, Jason <ja...@romos.net> wrote:
>>>
>>>> So far the main things I have seen is safari users and  iPad users
>>>> can’t use audio.  iPad no browsers work to get around the audio issue.  It
>>>> seems they changed how to select audio devices.
>>>>
>>>> J
>>>>
>>>>
>>>>
>>>> On Monday, Jul 20, 2020 at 9:58 PM, Maxim Solodovnik <
>>>> solomax666@gmail.com> wrote:
>>>> Hello All,
>>>>
>>>> I had plans to fix OPENMEETINGS-2402 before release but it seems to
>>>> take too much time already
>>>> I would like to release, then do some fixes, improvements
>>>> Please let me know if you see any show-stoppers
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> Best regards,
>>>> Maxim
>>>>
>>>>

Re: Time to release :)

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
But yeah something is truly odd with Safari.

The same samples from the webRTC samples section:
https://webrtc.github.io/samples/src/content/getusermedia/audio/
=> Works in Chrome/iOS
=> Fails in Safari/iOS

It's pretty much the same symptoms as described here:
https://discussions.apple.com/thread/8510720

Cheers
Seb

Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>


On Sat, 25 Jul 2020 at 12:01, seba.wagner@gmail.com <se...@gmail.com>
wrote:

> The audio/video testing tool actually also doesn't work for Safari.
> So maybe fixing up that may help before finding out why the overall
> conference room doesn't work.
>
> I've created https://issues.apache.org/jira/browse/OPENMEETINGS-2412
>
> Thanks,
> Seb
>
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Sat, 25 Jul 2020 at 11:08, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
>> I was hoping updating kurento-utils would help. Unfortunate it doesn't
>> seem so.
>>
>> There is a page from kurento project around Safari in particular:
>> https://doc-kurento.readthedocs.io/en/6.14.0/knowledge/safari.html
>>
>> Our particular issue is that you can't publish audio using Safari/iOS.
>> Which is a bit different from the above errors.
>>
>> On the other hand there are examples of working code, including Safari,
>> on https://webrtc.github.io/samples/
>> For example a simple:
>>
>>    - Choose camera, microphone and speaker
>>    <https://webrtc.github.io/samples/src/content/devices/input-output/>
>>
>>
>> => That example seems to works fine on Safari/iOS for publishing audio
>>
>> Thanks
>> Seb
>>
>> Sebastian Wagner
>> Director Arrakeen Solutions
>> http://arrakeen-solutions.co.nz/
>>
>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>>
>>
>> On Wed, 22 Jul 2020 at 02:11, Jason <ja...@romos.net> wrote:
>>
>>> So far the main things I have seen is safari users and  iPad users can’t
>>> use audio.  iPad no browsers work to get around the audio issue.  It seems
>>> they changed how to select audio devices.
>>>
>>> J
>>>
>>>
>>>
>>> On Monday, Jul 20, 2020 at 9:58 PM, Maxim Solodovnik <
>>> solomax666@gmail.com> wrote:
>>> Hello All,
>>>
>>> I had plans to fix OPENMEETINGS-2402 before release but it seems to take
>>> too much time already
>>> I would like to release, then do some fixes, improvements
>>> Please let me know if you see any show-stoppers
>>>
>>> Thanks!
>>>
>>> --
>>> Best regards,
>>> Maxim
>>>
>>>

Re: Time to release :)

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
The audio/video testing tool actually also doesn't work for Safari.
So maybe fixing up that may help before finding out why the overall
conference room doesn't work.

I've created https://issues.apache.org/jira/browse/OPENMEETINGS-2412

Thanks,
Seb


Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>


On Sat, 25 Jul 2020 at 11:08, seba.wagner@gmail.com <se...@gmail.com>
wrote:

> I was hoping updating kurento-utils would help. Unfortunate it doesn't
> seem so.
>
> There is a page from kurento project around Safari in particular:
> https://doc-kurento.readthedocs.io/en/6.14.0/knowledge/safari.html
>
> Our particular issue is that you can't publish audio using Safari/iOS.
> Which is a bit different from the above errors.
>
> On the other hand there are examples of working code, including Safari, on
> https://webrtc.github.io/samples/
> For example a simple:
>
>    - Choose camera, microphone and speaker
>    <https://webrtc.github.io/samples/src/content/devices/input-output/>
>
>
> => That example seems to works fine on Safari/iOS for publishing audio
>
> Thanks
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Wed, 22 Jul 2020 at 02:11, Jason <ja...@romos.net> wrote:
>
>> So far the main things I have seen is safari users and  iPad users can’t
>> use audio.  iPad no browsers work to get around the audio issue.  It seems
>> they changed how to select audio devices.
>>
>> J
>>
>>
>>
>> On Monday, Jul 20, 2020 at 9:58 PM, Maxim Solodovnik <
>> solomax666@gmail.com> wrote:
>> Hello All,
>>
>> I had plans to fix OPENMEETINGS-2402 before release but it seems to take
>> too much time already
>> I would like to release, then do some fixes, improvements
>> Please let me know if you see any show-stoppers
>>
>> Thanks!
>>
>> --
>> Best regards,
>> Maxim
>>
>>

Re: Time to release :)

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I was hoping updating kurento-utils would help. Unfortunate it doesn't seem
so.

There is a page from kurento project around Safari in particular:
https://doc-kurento.readthedocs.io/en/6.14.0/knowledge/safari.html

Our particular issue is that you can't publish audio using Safari/iOS.
Which is a bit different from the above errors.

On the other hand there are examples of working code, including Safari, on
https://webrtc.github.io/samples/
For example a simple:

   - Choose camera, microphone and speaker
   <https://webrtc.github.io/samples/src/content/devices/input-output/>


=> That example seems to works fine on Safari/iOS for publishing audio

Thanks
Seb

Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>


On Wed, 22 Jul 2020 at 02:11, Jason <ja...@romos.net> wrote:

> So far the main things I have seen is safari users and  iPad users can’t
> use audio.  iPad no browsers work to get around the audio issue.  It seems
> they changed how to select audio devices.
>
> J
>
>
>
> On Monday, Jul 20, 2020 at 9:58 PM, Maxim Solodovnik <so...@gmail.com>
> wrote:
> Hello All,
>
> I had plans to fix OPENMEETINGS-2402 before release but it seems to take
> too much time already
> I would like to release, then do some fixes, improvements
> Please let me know if you see any show-stoppers
>
> Thanks!
>
> --
> Best regards,
> Maxim
>
>

Re: Time to release :)

Posted by Jason <ja...@romos.net>.
So far the main things I have seen is safari users and iPad users can’t use audio. iPad no browsers work to get around the audio issue. It seems they changed how to select audio devices.

J

> On Monday, Jul 20, 2020 at 9:58 PM, Maxim Solodovnik <solomax666@gmail.com (mailto:solomax666@gmail.com)> wrote:
> Hello All,
>
> I had plans to fix OPENMEETINGS-2402 before release but it seems to take too much time already
> I would like to release, then do some fixes, improvements
> Please let me know if you see any show-stoppers
>
> Thanks!
>
> --
> Best regards,
> Maxim

Re: Time to release :)

Posted by Stefan Kühl <st...@quatrekuehl.eu>.
Hey @all, 

no show-stoppers from my point of view. 

Greetz, 

Stefan

Am 21.07.2020 05:18, schrieb Maxim Solodovnik:

> On Tue, 21 Jul 2020 at 10:06, seba.wagner@gmail.com <se...@gmail.com> wrote: 
> 
>> Up to you. I'm happy to push tickets to a later version. 
>> 
>> I'm more concerned about production readiness. Stability, performance and security.
> 
> Security is one of the reasons: many dependencies were released with security fixes 
> 
>> Something hard to test and do unit tests on. But important to go to recommend it for production. 
>> 
>> Do we have any metrics, any reports on long term running the server at scale ? 
>> 
>> I don't see much right now, so I tend to think we may have done as much as we can given the circumstances.
> 
> According to user reports there are  
> - Problems with Safari (was unable to get to real Mac yet) 
> - Occasional problems with connectivity (I guess we need to get working example of bullet-proof "one port" configuration) 
> 
> Thanks, 
> Seb
> 
> Sebastian Wagner 
> Director Arrakeen Solutions 
> http://arrakeen-solutions.co.nz/ 
> [1] [2] 
> 
> On Tue, 21 Jul 2020 at 14:58, Maxim Solodovnik <so...@gmail.com> wrote: 
> Hello All, 
> 
> I had plans to fix OPENMEETINGS-2402 before release but it seems to take too much time already 
> I would like to release, then do some fixes, improvements 
> Please let me know if you see any show-stoppers 
> 
> Thanks!
> -- 
> 
> Best regards,
> Maxim

  -- 

Best regards,
Maxim 

Links:
------
[1]
https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url
[2]
https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url

Re: Time to release :)

Posted by Maxim Solodovnik <so...@gmail.com>.
On Tue, 21 Jul 2020 at 10:06, seba.wagner@gmail.com <se...@gmail.com>
wrote:

> Up to you. I'm happy to push tickets to a later version.
>
> I'm more concerned about production readiness. Stability, performance and
> security.
>

Security is one of the reasons: many dependencies were released with
security fixes


>
> Something hard to test and do unit tests on. But important to go to
> recommend it for production.
>
> Do we have any metrics, any reports on long term running the server at
> scale ?
>
> I don't see much right now, so I tend to think we may have done as much as
> we can given the circumstances.
>

According to user reports there are
- Problems with Safari (was unable to get to real Mac yet)
- Occasional problems with connectivity (I guess we need to get working
example of bullet-proof "one port" configuration)


>
> Thanks,
> Seb
>
>
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Tue, 21 Jul 2020 at 14:58, Maxim Solodovnik <so...@gmail.com>
> wrote:
>
>> Hello All,
>>
>> I had plans to fix OPENMEETINGS-2402 before release but it seems to take
>> too much time already
>> I would like to release, then do some fixes, improvements
>> Please let me know if you see any show-stoppers
>>
>> Thanks!
>>
>> --
>> Best regards,
>> Maxim
>>
>

-- 
Best regards,
Maxim

Re: Time to release :)

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Up to you. I'm happy to push tickets to a later version.

I'm more concerned about production readiness. Stability, performance and
security.

Something hard to test and do unit tests on. But important to go to
recommend it for production.

Do we have any metrics, any reports on long term running the server at
scale ?

I don't see much right now, so I tend to think we may have done as much as
we can given the circumstances.

Thanks,
Seb



Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>


On Tue, 21 Jul 2020 at 14:58, Maxim Solodovnik <so...@gmail.com> wrote:

> Hello All,
>
> I had plans to fix OPENMEETINGS-2402 before release but it seems to take
> too much time already
> I would like to release, then do some fixes, improvements
> Please let me know if you see any show-stoppers
>
> Thanks!
>
> --
> Best regards,
> Maxim
>