build: increase macOS minimum supported version

[targos]

Starting with V8 6.8, it will not be possible to build with macOS 10.10 and
below. Those versions are already EoL.

Refs: nodejs/build#1358

Checklist

• documentation is changed or added
• commit message follows commit guidelines

[nodejs-github-bot]

@targos build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/314/pipeline

[targos]

/cc @nodejs/tsc @nodejs/build

Does this have to be semver-major? If the answer is yes, we won't be able to update V8 to 6.8 in Node 10.

[gibfahn]

Does this have to be semver-major? If the answer is yes, we won't be able to update V8 to 6.8 in Node 10.

Seems like a question that we are coming to consensus on in nodejs/build#1358.

[jasnell]

I don't believe this needs to be semver-major if the older mac os versions are already EoL

[mmarchini]

LGTM and IMO we should update the minimum version of our compilers more frequently, otherwise we'll keep having problems when upgrading our dependencies.

[Trott]

[Trott]

For a separate PR, perhaps, but we may want to add a fourth support level that is the opposite of Experimental in that it's something that is heading towards EOL. Right now, we use Experimental for both things that are heading towards EOL and things that we're working on getting more fully supported. The text explaining Experimental implies that it's the latter. A separate label for the former might be useful.

[maclover7]

Writing this down as a reminder for myself/other Build WG members (or anyone else who would like to contribute), that we'll have to update our build exclusion matrix whenever this lands

[ChALkeR]

@Trott I don't think 10.10 was Experimental. Only >= 10.8 < 10.10 was experimental afaik, and this removes both >= 10.8 < 10.10 and 10.10.

I'm +1 to removing it though.

[ChALkeR]

Note that relative 10.10 + 10.9 market share of OS X looks to be high (above 10% of all macs).

But, given that OS X 10.10 reached EoL, and that v8 6.8 is failing to build on it, I don't think that those users have a significant intersection with users that would need to build latest Node.js 10.x on their machines. We have 8.x LTS that should still work there.

Newer v8 for everyone is more important.

Also, this already falls under "The community does not build or test against end-of-life distributions (EoL)", so dropping support for that should not be a semver-major.

[ChALkeR]

@targos@ofrobots One question, though: Chrome 68 and 69 claim to have support for OS X 10.10.
Is that correct, and, if yes, does that mean that we can avoid dropping the support for 10.10?

Ref: https://www.google.com/chrome/canary/?platform=mac

[mcollina]

LGTM

[ofrobots]

ping @hashseed regarding #21883 (comment).

[mmarchini]

Chrome 68 and 69 claim to have support for OS X 10.10.
Is that correct, and, if yes, does that mean that we can avoid dropping the support for 10.10?

I think this is possible because Chrome and V8 are built using clang from depot_tools and not from Xcode.

[hashseed]

Yeah I honestly don't know. V8 did not change anything in particular. We simply pull the clang that Chrome bundles from gclient. If that happens to support OSX 10.10, then I guess we do.

[targos]

@ChALkeR see nodejs/build#1358 (comment). It won't be possible to build Node from OSX 10.10 but that doesn't mean the binary won't be compatible.

[targos]

The problem is not with OSX, it's with Xcode. The version of Xcode that is in 10.10 has a bug that makes compilation fail. This bug is fixed in the more recent Xcode that is in 10.11.

[mmarchini]

I think updating the OS X/Xcode version we use on our infrastructure won't make the builds incompatible with previous OS X versions, but I'm not 100% sure.

[targos]

Landed in 9453240