We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to https://learn.microsoft.com/en-us/visualstudio/productinfo/vs-servicing#older-versions-of-visual-studio, Microsoft will fully drop support for Visual Studio 2015 in 9 months (October 2025).
Should LightGBM drop support for it after the v4.6.0 release (#6796)?
LightGBM uses Appveyor to test the oldest supported Visual Studio. So this change would mean updating this:
LightGBM/.appveyor.yml
Line 3 in 3aac25a
To Visual Studio 2017 (ref: https://www.appveyor.com/docs/build-environment/#build-worker-images
The text was updated successfully, but these errors were encountered:
I don't mind.
Sorry, something went wrong.
No branches or pull requests
Description
According to https://learn.microsoft.com/en-us/visualstudio/productinfo/vs-servicing#older-versions-of-visual-studio, Microsoft will fully drop support for Visual Studio 2015 in 9 months (October 2025).
Should LightGBM drop support for it after the v4.6.0 release (#6796)?
Benefits of this work
Approach
LightGBM uses Appveyor to test the oldest supported Visual Studio. So this change would mean updating this:
LightGBM/.appveyor.yml
Line 3 in 3aac25a
To Visual Studio 2017 (ref: https://www.appveyor.com/docs/build-environment/#build-worker-images
The text was updated successfully, but these errors were encountered: