On Mon, Jan 05, 2015 at 01:13:28PM -0800, Kent James wrote: > On 1/4/2015 3:43 PM, Mike Hommey wrote: > >I don't think anyone in their right mind > >would have installed 2012 after we dropped support for 2010, because the > >current version was 2013 at the time, and what's the point to upgrade if > >it's not for the current version? > > I am not objecting to dropping support for VS2012, but just to repeat what I > previously said, this person "in his right mind" installed VS2012 recently > to have a single version of a build environment that works from esr24 - > trunk. That is a big advantage, but the prevailing opinion is that it is not > enough of an advantage to maintain support. > > If I had my choice, VS2012 support would be logically dropped when gecko 31 > support was dropped. But that would actually not solve my issues, since I > will be compiling with gecko 31 long after official support is dropped, and > it is clear that VS2012 will be gone long before then. > > So that is my opinion, but that is not the prevailing view, and I can accept > that.
We dropped support for 2010 during this cycle. Esr24 was not supported anymore already, why do you need to build it? Does esr31 actually fail to build with 2013? Mike _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
