GeezerVison

CI: https://ci.nodejs.org/job/node-test-commit/4780/

CITGM: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/372/ (I think I have it right..)

I spotted a problem on Windows. A PR will land shortly so I'll update this.

Updated to fix the Windows build issue. Jenkins seems to be away for the weekend, I'll try to run a CI later.

New CI: https://ci.nodejs.org/job/node-test-commit/4811/

CI is green except some RPi binary tests where Jenkins failed to mkdir for some reason.

CITGM: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/374/ (hopefully I started this one right)

Fixes #4351 per #4351 (comment)

Can this land before Node 7?

I don't know, when does Node 7 land?

https://github.com/nodejs/node/milestone/15 seems to indicate a code freeze on September 30? Maybe @rvagg or @jasnell can give more details?

Adding to the 7.0.0 milestone so we don't forget about it.

The v7.x branch has already been cut. Anything that is semver-patch or semver-minor will be pulled over. Anything semver-major will require CTC review and approval to land in v7.x at this point. The first beta build will be going out today.

v7.0.0 is targeted for mid to late October depending largely on when V8 5.4 goes stable, so there's still a short amount of time (but not a lot)

@jasnell Ack. At the moment we are waiting on a patch to finalize z/OS support, other than that the release is ready.

Updated the PR with latest v1.x. Can someone help kick off a CITGM? Thanks!

CITGM: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/394/

Thanks Evan!

I can confirm that this fixes #6763.

@saghul anything in here that needs to land in v7 specifically, or is this good for many minor / patch version?

Note, the release hasn't actually happened yet. It is still waiting on libuv/libuv#1037.

@saghul ... ping... what's the status on this? Should this still be on the v7 milestone? Note that we're a week out from the actual 7.0.0 release.

If the libuv upgrade doesn't make into 7.0.0, when would the next window for that be?

that depends on how significant the update will be. If it can be landed as a semver-minor, then it can land any time within v7.x after v7.0.0 is released. If it must be landed as a semver-major, it won't go into a release until next April

I should be a semver minor, v1x maintains backwards compatibility.

The status is we are waiting for some final issues to be ironed out in the
z/OS PR so it can land. I may try to push for a release before the end of
the week because then I'll go missing for a bit. Colin will take this over
most likely in that case.

On Oct 17, 2016 20:07, "James M Snell" [email protected] wrote:

that depends on how significant the update will be. If it can be landed as
a semver-minor, then it can land any time within v7.x after v7.0.0 is
released. If it must be landed as a semver-major, it won't go into a
release until next April

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#8280 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AATYGOHZE_PXqHQejwRp4ciQ-BgTC0oNks5q07l0gaJpZM4Jt7P0
.

Ok, then I'm going to take this off the v7 milestone critical path. If it lands, great, if not, then it can go into a 7.x minor.

I'll be sending a replacement PR for this soon.