Re: Dropping support for VS2013

[waxmiguel]

> On Jul 7, 2016, at 09:55, Gregory Szorc  wrote:
> 
> On Thu, Jun 30, 2016 at 5:55 PM, Gregory Szorc  wrote:
> 
>> On Tue, May 31, 2016 at 4:22 PM, Gregory Szorc  wrote:
>> 
>>> Heads up: we'll soon be dropping support for building mozilla-central
>>> with VS2013. Bug 1186064 tracks and the patch has already received r+.
>>> 
>>> I'm going to wait a few days before landing because this could be
>>> disruptive and I want to at least give a heads up before I create a fire.
>>> Please install VS2015 in the next 48 hours to avoid a surprise the next
>>> time you pull.
>>> 
>> 
>> The patch just landed on the autoland repo (delayed due to London and PTO).
>> 
>> It will require VS2015u2 or newer to build (drops support for building
>> with VS2015u1).
>> 
>> Also, VS2015u3 was released this week. It seems to build in
>> warnings-as-errors mode just fine locally with a vanilla mozconfig. But
>> YMMV. Bug 1283203 getting it more officially supported.
>> 
> 
> After bouncing twice, it finally got merged into central and inbound a few
> minutes ago. Sorry for the delays.
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Rationalising Linux audio backend support

[waxmiguel]

thanks!

On 14/07/2016, Paul Adenot  wrote:
> I just landed some telemetry to measure the usage of all audio backends,
> we'll have data soon.
>
> This was bug 1280630, and the probe is at [0]. This also measures
> failures to open a stream and usage of backends that should not be used
> on certain platform, like winmm on windows vista+.
>
> Also I support this proposal.
>
> Cheers,
> Paul.
>
> [0]:
> http://searchfox.org/mozilla-central/source/toolkit/components/telemetry/Histograms.json#105
>
> On Thu, Jul 14, 2016, at 09:32 AM, Jet Villegas wrote:
>> I generally support reducing the support matrix for Linux PCM audio.
>>
>> A quick search for "ALSA vs. PulseAudio" comes up with mixed reviews for
>> either, which probably explains why we have both. It also seems like we
>> can
>> count on ALSA being available on every distro, but perhaps not
>> PulseAudio.
>> Can we add some telemetry to measure that?
>>
>> Alternatively, you can wire this up so that we only fall back to ALSA
>> (stereo) when we can't get PCM audio to route through Pulse.
>>
>> --Jet
>>
>> On Wed, Jul 13, 2016 at 7:31 PM,  wrote:
>>
>> > Supporting two separate audio backends in Linux is duplicated effort.
>> >
>> > I took over the platform media playback team at Mozilla a little over 3
>> > years ago. At that point we only supported WebM/VP8/Vorbis,
>> > Ogg/Theora/Vorbis and Wave as well as MP3 on Windows and some additional
>> > codecs including MP4/H.264/AAC on a small number of Android phones. At
>> > that
>> > time most media in the browser ran in Flash.
>> >
>> > Since then we’ve added words like MP3, MP4, H.264, VP9, Opus, AAC,
>> > HE-AAC,
>> > MSE and EME to our vocabulary. DASH and HLS are handled by site
>> > Javascript
>> > using MSE. A massive amount of effort has gone into making everything
>> > parallel so we can get as many pixels to the screen as possible. We’re
>> > working on platform specific performance improvements on Windows, Linux
>> > and
>> > Mac. We’re also doing some work to protect ourselves against driver
>> > crashes
>> > on Windows and Android.
>> >
>> > We are seeing an explosion of interest in HTML5 video and the
>> > accompanying
>> > audio is going through libcubeb, our audio backend. We’ve added low
>> > latency
>> > support to libcubeb for WebAudio and full duplex support so we can use
>> > it
>> > directly for microphone input for WebRTC.
>> >
>> > Our official Firefox builds on Linux support both PulseAudio and ALSA.
>> > There are a number of additional contributed backends that can be turned
>> > on
>> > at compile time, although contribution towards long-term maintenance and
>> > matching feature parity with the actively developed backends has been
>> > low.
>> > On Linux, we actively maintain the PulseAudio backend but we also
>> > approach
>> > the PulseAudio developers when we see issues in PulseAudio. The
>> > PulseAudio
>> > developers are generally good to work with.
>> >
>> > The most problematic backend across all platforms is ALSA. It is also
>> > missing full duplex support. We are intending to add multichannel (5.1)
>> > support across all platforms and the ones that don’t make the cut will
>> > be
>> > the ALSA backend and the WinMM backend used on Windows XP.
>> >
>> > Our ALSA backend has fallen behind in features, it is buggy and
>> > difficult
>> > to fix. PulseAudio is contrastingly low maintenance. I propose
>> > discontinuing support for ALSA in our official builds and moving it to
>> > off-by-default in our official builds.
>> >
>> > Leaving all the ALSA code in tree gives people the opportunity to
>> > continue
>> > maintaining the ALSA backend. Re-enabling it would require bringing it
>> > up
>> > to the same standard as other backends, not only in terms of current
>> > state
>> > but also in terms of consistency of contribution.
>> >
>> > As a long time Linux user, I want to get the most value out of our
>> > efforts
>> > on Linux. I can do that by focusing our efforts on the things that will
>> > have the greatest impact. Sometimes that requires taking a step back and
>> > deciding to do one thing well instead of two things poorly.
>> >
>> > Just to be clear, I’m proposing we stop spending time on ALSA so we can
>> > spend that time on adding 5.1 audio support to our PulseAudio backend.
>> > ___
>> > dev-platform mailing list
>> > dev-platform@lists.mozilla.org
>> > https://lists.mozilla.org/listinfo/dev-platform
>> >
>> ___
>> dev-platform mailing list
>> dev-platform@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-platform
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>


-- 
waxmigs2...@gmail.com
waxmig...@mail.ru
waxmig...@bitrix24.com
0xC840F256B0F0FF9069E918d060063057AAaA6b36