Hi, There is no objection. We drop support for Visual Studio 2017.
Thanks, -- kou In <20220817.170509.1487454221214035438....@clear-code.com> "[C++] Can we drop support for Visual Studio 2017?" on Wed, 17 Aug 2022 17:05:09 +0900 (JST), Sutou Kouhei <k...@clear-code.com> wrote: > Hi, > > Can we drop support for Visual Studio 2017? > > Visual Studio 2017 reached EOL at 2022-04-12: > https://docs.microsoft.com/en-us/lifecycle/products/visual-studio-2017 > > Listing | Start Date | Mainstream End Date | Extended End Date > Visual Studio 2017 | Mar 7, 2017 | Apr 12, 2022 | Apr 13, 2027 > > Note that users can mix binaries built with Visual Studio > 2015 or later because Visual Studio 2015 or later keep > binary compatibility. > > See also: > https://docs.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017 > > If we drop support for Visual Studio 2017, we can remove CI > jobs that run on AppVeyor. Because GitHub Actions provides > Visual Studio 2019 or later. We're using AppVeyor only for > Visual Studio 2017. > > > Thanks, > -- > kou
