v6.0.0 Release Candidate 4

[jasnell]

This is the PR for the release candidate.

PLEASE DO NOT LAND THIS PR

It is here for review and CI purposes only.

/cc @nodejs/ctc

[jasnell]

CI: https://ci.nodejs.org/job/node-test-pull-request/2241/

[cjihrig]

@jasnell the list of semver majors is not comprehensive. Is that intentional? Shouldn't all of them at least be mentioned in the changelog?

[jasnell]

I pulled out some of the "lesser" ones from the notable changes. The
commits are currently only since v5.10.1. I still have to go in and add the
full list of the semver-majors to that list.
On Apr 11, 2016 1:55 PM, "Colin Ihrig" notifications@github.com wrote:

@jasnellhttps://github.com/jasnell the list of semver majors is not
comprehensive. Is that intentional? Shouldn't all of them at least be
mentioned in the changelog?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6155 (comment)

[jasnell]

Release Candidate Build: https://ci-release.nodejs.org/job/iojs+release/503/

[jbergstroem]

(the 32-bit slave's java process crashed)

[mscdex]

It's a conspiracy, Java will stop at nothing to prevent node v6 from being released!

[jasnell]

Well, we at least got a partial rc.1 build: https://nodejs.org/download/rc/v6.0.0-rc.1/

[jasnell]

I'll do a RC.2 on wednesday. Time to start the testing!

[MylesBorins]

@jasnell a quick test shows the the .pkg installer is working as expected. npm install works, and installing a gyp compiled module (heapdump) does as well

This was all manually tested on osx 10.10.5

[fhemberger]

Can we ship localized Windows and OS X installers with 6.0? First one is already on hold since io.js v3 ;)

[vsemozhetbyt]

v8 is still 4.9 in the RC1. Will it be 5.0 in the release or another RC?

[jasnell]

@vsemozhetbyt ... that is the hope. I decided to hold off building RC.1 with v5 until we're a bit closer to v5 going stable. The plan is to try our absolute best to get v5 in.

[vsemozhetbyt]

@jasnell Thank you. It will be greate, with its RegEx Unicode support and performance improvements.

[orangemocha]

Duplicate link

[dnalborczyk]

@jasnell

Chrome 50.0.2661.75 went stable: http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html and so should be V8 5.0.71.32, according to Dominic's gist: https://gist.github.com/domenic/aca7774a5d94156bfcc1 and https://omahaproxy.appspot.com/

Daniel

[jasnell]

Rebased for RC 2. Initial CI: https://ci.nodejs.org/job/node-test-pull-request/2261/

[jasnell]

Note: I HAVE NOT yet updated the change log in this. I will do so before cutting the actual updated release candidate.

[MylesBorins]

CI looks good. The two arm failures are unrelated (flaky)

[jasnell]

Release Candidate 2 Build: https://ci-release.nodejs.org/job/iojs+release/514/
Build failure on Rpi -> https://ci-release.nodejs.org/job/iojs+release/nodes=pi1-raspbian-wheezy/514/

[jasnell]

Release Candidate 2 builds with v8 v5 are ready to go... https://nodejs.org/download/rc/v6.0.0-rc.2/

[vsemozhetbyt]

node-v6.0.0-rc.2-x64.msi creates link to docs as
https://nodejs.org/download/custom/v6.0.0-rc.2/docs/api/ ("404: Page could not be found")
instead of
https://nodejs.org/download/rc/v6.0.0-rc.2/docs/api/ (OK).

[jasnell]

Ok, that's due to me missing a step in the CI job that sets the url base. Will be fixed in RC3 next week.

[Salakar]

@jasnell have there been any regressions to module.js / require?

See: Salakar/mocha@7c07b67

Works fine on v5.10.1

[jasnell]

@vsemozhetbyt ... we have one regression currently being looked at here: #6215 , likely the cause

[jasnell]

That's a question for v8 folks /cc @ofrobots

[dnalborczyk]

@vsemozhetbyt The flag might be just a leftover. A search for the 'harmony_regexp_property' flag in the node/v8-project-code reveals no usage.

It seems it should work without a flag in v8 5.0:
http://v8project.blogspot.com/2016/03/v8-release-50.html

[vsemozhetbyt]

@dnalborczyk The http://v8project.blogspot.com/2016/03/v8-release-50.html supposes this flag:

 --harmony_unicode_regexps (enable "harmony unicode regexps")
type: bool default: true

— i.e. the u regexp flag, the \u{xxxxx} symbols and unicode semantics of quantifiers and . class. It seems to have nothing to do with property classes (\p{} symbols) under the different flag (--harmony_regexp_property).

[dnalborczyk]

My bad. I only glanced over the blog post. Nonetheless, the flag is not being used, there's no condition using it whatsoever (unless my search is broken).

Maybe the flag was forgotten or it wasn't feasible to use it?

[vsemozhetbyt]

@dnalborczyk Then why node --v8-options on the Node v6 RC2 has it in the output? And why the feature that is not a part of any standart or even draft works just like that (while in the last Crome Canary it does not)? This is a great feature and I like it a lot (I've missed it since the Perl RegExp), but it seems a bit strange.

[ofrobots]

@vsemozhetbyt I suspect this is a V8 issue – I can reproduce it with Chrome 50 – I have opened an upstream bug.

[rvagg]

@nodejs/collaborators FYI nightlies are back on, they took a bit of a break after we moved the Jenkins release job to a more secure instance but they should be running again and coming out at https://nodejs.org/download/nightly/

There are currently v5.x (currently 5.10.2-nightly...) and master (currently 6.0.0-nightly...) nightlies. The 5.x ones will only appear if folks are cherry picking from master to v5.x, there have been a couple of us doing this in the past but it's not been very regular. If those who are regularly releasing off v5.x could make a regular habit of cherry picking eligible commits then we will get more regular nightlies. The master nightlies will switch to 7.0.0-nightly... after we make the v6 release and I'll also turn off nightlies for v5.x and turn on v6.x.

The master nightlies should be good for testing v6.0.0 if you're on that effort. node-gyp understands these so in theory the should be drop-in replacements to whatever you're using now.

[jasnell]

Woo! Yeah I got all excited yesterday when I saw a nightly build had been
kicked off. Great to see.
On Apr 16, 2016 3:56 AM, "Rod Vagg" notifications@github.com wrote:

@nodejs/collaborators https://github.com/orgs/nodejs/teams/collaborators
FYI nightlies are back on, they took a bit of a break after we moved the
Jenkins release job to a more secure instance but they should be
running again and coming out at https://nodejs.org/download/nightly/

There are currently v5.x (currently 5.10.2-nightly...) and master
(currently 6.0.0-nightly...) nightlies. The 5.x ones will only appear if
folks are cherry picking from master to v5.x, there have been a couple of
us doing this in the past but it's not been very regular. If those who are
regularly releasing off v5.x could make a regular habit of cherry picking
eligible commits then we will get more regular nightlies. The master
nightlies will switch to 7.0.0-nightly... after we make the v6 release and
I'll also turn off nightlies for v5.x and turn on v6.x.

The master nightlies should be good for testing v6.0.0 if you're on that
effort. node-gyp understands these so in theory the should be drop-in
replacements to whatever you're using now.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6155 (comment)

[dnalborczyk]

@vsemozhetbyt
Then why node --v8-options on the Node v6 RC2 has it in the output?

The parameters are just being passed on from node to the v8 engine. Node itself doesn't provide nor handle them.

And why the feature that is not a part of any standart or even draft works just like that

You might have to ask that question the v8 project. Not sure about any drafts or proposals. The commit message in one of the links you provided says: [regexp] experimental implementation for \p property class.

[dnalborczyk]

@jasnell@rvagg

I asked myself the following already in the past, but always forgot to follow up:

I'm wondering if the RC releases are announced and accessible anywhere, besides buried in github issues and pull requests. I can't find any mention on the node website. How would anyone be able to test the RC, if the majority doesn't even know about its existence?

[jasnell]

They're announced on Twitter, that's about it. We could definitely do more
to get the word out tho. A blog post on the website would likely be a good
start.
On Apr 16, 2016 6:34 AM, "dnalborczyk" notifications@github.com wrote:

@jasnellhttps://github.com/jasnell@rvagghttps://github.com/rvagg

I asked myself the following already in the past, but always forgot to
follow up:

I'm wondering if the RC releases are announced and accessible anywhere,
besides buried in github issues and pull requests. I can't find any mention
on the node website https://nodejs.org. How would anyone be able to
test the RC, if the majority doesn't even know about it's existence?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6155 (comment)

[vsemozhetbyt]

@jasnell Could you give the twitter link please?

[benjamingr]

Sorry if unrelated - and this might be a silly thing to ask - but why should collaborators care about nightlies? Whenever I want to test something I just build the source off the branch and run it (which I need to be able to do as a collaborator anyway).

I think it could be interesting to get people to run v6 before the release and provide useful feedback and bug reports. That might be a @nodejs/evangelism issue though.

[hashseed]

This is simply a bug in V8's 5.0 branch. It's already fixed in 5.1 and 5.2. I'll fix this. Related V8 issue: https://bugs.chromium.org/p/v8/issues/detail?id=4926

[hashseed]

Fixed in V8 version 5.0.71.33.

[jasnell]

Release Candidate 3 build running now: https://ci-release.nodejs.org/job/iojs+release/532/

[mdouglass]

Can't run our projects with rc3 because of mocha being broken by #6215. Will that be being merged before release?

[jasnell]

@mdouglass ... hopefully should land in the next day or two. Definitely in time for the release next week

[jasnell]

Release candidate 4 build: https://ci-release.nodejs.org/job/iojs+release/545/
(this includes #6215 btw)

[mdouglass]

Excellent, I'll give it a try now.

[jasnell]

Give it a few more minutes to finish building :-) ... likely about 10-20 at the max

[jasnell]

Continuing work here: #6383