-
Notifications
You must be signed in to change notification settings - Fork 166
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
MacOS 10.14 deprecation plan #3087
Comments
Our minimum deployment target is set to 10.15 already but thats only for v18 and above so 10.14 is still supported by LTS lines still in support. I know we have a caveat that we can drop EOL systems at will but it might be worth waiting for a bit before dropping that. firstly we need some more machines of later versions, we dont have any 12 or 13 machines to my knowledge nor do we have the capacity on the arm64 side for them. Intel should be fine due to the amount of space we have in orka. |
It is worth discussing bumping the minimum deployment target for Node.js 20 (bearing in mind whatever we set will be it until the April 2026 End-of-Life date). If we bump to, e.g. macOS 11 we'd need to move where we build the x64 releases onto a macOS 11 machine (and probably would need to set up a x64 macOS 11 release machine unless we'd be comfortable compiling under Rosetta 2 on the arm64 machines (which we do anyway for the pkg builds)). |
Good! Let's discuss about it in the next meeting and build a plan 👍 |
Moving to 11 as the minimum makes sense to me. |
As agreed in #3299 we will remove the MacOS 10.14 machines from the build pipelines. This open the opportunity to use the HW for other MacOS Versions. The deprecation will take place once Nodejs 14 reach the End-of-life at 2023-04-30. Affected machines
Next steps (After 2023-04-30) As only Orka VMs are affected we can do a backup and delete them easily:
I will need some help to remove the machines from Jenkins as I don't have the admin access to Jenkins. Should I ask for the access? The empty slots that this machines will generate in Orka cluster will be managed in a separate discussion (#3240) |
@UlisesGascon I'm happy to remove the machines from Jenkins. Are there other cases where you need jenkins access? If so then getting you access instead might make sense. |
@nodejs/build I'm thinking giving @UlisesGascon Jenkins access makes sense. What do you think? |
+1 from me |
Also +1 from me. |
Current Status
Before After Next stepsThis issue will be closed when: |
@UlisesGascon Did we verify if building on the later release with the minimum deployment target option of 10.14/10.15 still allows it to run ok on those versions? |
Checking the support for MacOs versions, seems like 10.x versions are deprecated. Should be plan the upgrade of the test machines using 10.x?
The text was updated successfully, but these errors were encountered: