8.1.0 Tracking Issue

[jasnell]

@nodejs/ctc @nodejs/release ... Just an FYI... later on today I will be opening a proposal for a Node.js 8.1.0 release that I'm scheduling for Wednesday. The release will include semver-patch and semver-minor's that have landed since 8.x including a number of 8.x bug fixes. I will have the proposal PR opened by end of the day today.

[bricss]

What about #13306 ❓

[mgol]

V8 5.9 is stable now if that matters for this release.

[jasnell]

neither V8 5.9 or libuv 1.12.0 will go in to this release.

[zimbabao]

npm-5.0.3 will be bundled with it?.

[gibfahn]

npm-5.0.3 will be bundled with it?.

If it can land by Wednesday morning (see #13487 (comment))

[jasnell]

@nodejs/release ... just an fyi for all releasers: none of the V8 updates that may land in master around 5.9 can be pulled into 8.x at all because the 5.9 stuff does not have the ABI compatibility stuff for 6.0. If you look, the NODE_MODULE_VERSION in 8.x is 57, while on master it is still at 55. Any V8 backport will need to be looked at carefully before it can be pulled over. We will not be able to update V8 in 8.x until either (a) 5.9 lands in master with the ABI stability fixes or (b) 6.0 lands in master.

[Fishrock123]

@jasnell Those commits then must be labeled as dont-land- or release tooling will be a mess?

[silverwind]

It's released, closing.