-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
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
jenkins: remove v16 from VersionSelectorScript #3489
Conversation
It's written down that we keep stuff around for 6 months after a release line goes End-of-Life before removing. Lines 294 to 296 in 2e7c763
FWIW I can only remember one time when we decided to do an additional release after End-of-Life, which IIRC was within the month after the End-of-Life. |
I would be good to keep this around a bit longer if possible. I don't think it hurts anything, right? |
That's why I made this a draft. I'll come back to it in 6 months. |
3055d5c
to
e0edf5d
Compare
Ready for a new review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Removing VS2015 and VS2017 from compilation jobs is highly optional.
EDIT: I was thinking about maybe removing the vs2015 and vs2017 compilation configurations completely, but that is not very urgent. I may open a follow-up PR for that at some point.
No description provided.