Re: Dropping support for VS2013

2016-08-16 Thread 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

Re: Dropping support for VS2013

2016-07-06 Thread Gregory Szorc
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+.

Re: Dropping support for VS2013

2016-06-30 Thread Gregory Szorc
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 >

Re: Dropping support for VS2013

2016-06-08 Thread Gijs Kruitbosch
Who is responsible for updating our build documentation about this? It seems the docs still don't believe we can even build for sure on VS2015 (though it's been the recommended compiler for a while now), and list a number of SDKs that I'm not convinced you'd actually need to manually install

Re: Dropping support for VS2013

2016-06-01 Thread Liz Henry (:lizzard)
Hi Greg and others, I was just about to raise the issue of performance regression from this change. If we are aiming this at the 49 release, I would like for us to improve the situation described in bug 1259923, a 15% performance regression across all Talos tests covering Windows platforms, which

Dropping support for VS2013

2016-05-31 Thread Gregory Szorc
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