Skip to content

Release proposal v2.1.0 - #1777

Closed
rvagg wants to merge 1 commit into
nodejs:masterfrom
rvagg:v2.1.0-release
Closed

Release proposal v2.1.0#1777
rvagg wants to merge 1 commit into
nodejs:masterfrom
rvagg:v2.1.0-release

Conversation

@rvagg

Copy link
Copy Markdown
Member

It's been more than a week, how could we be so slack?!

Only thing forcing semver-minor here is the --trace-sync-io flag. I have a vague memory of a discussion resulting in an decision that CLI changes shouldn't impact semver (I don't actually agree with this fwiw), however I see that --require still got in with semver-minor so it looks like we're saying that CLI changes do impact semver.

I see no reason to delay this, I'm proposing that we push ahead with this within ~24h unless something major comes up.

Windows timeouts still happening but apart from that we're looking solid: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/700/ (I'm going to have yet another go at understanding the Windows Jenkins problems, they are becoming a big problem for defining stability)

@mscdexmscdex added the meta Issues and PRs related to the general management of the project. label May 23, 2015
@Fishrock123

Copy link
Copy Markdown
Contributor

👍 There's still problems with v8 so no 3.0 for now.

@rvagg

Copy link
Copy Markdown
MemberAuthor

Switched to running all of the windows build machines to manually from cmd since it's the running-as-a-service that's causing these failures. @wolfeidau is suggesting that it's likely a security-policy thing that's preventing some action from occurring and maybe the timeout is because there's a dialog box or a UAC-ish thing (although it's 2008 as well so probably not UAC exactly).

Got this failure on run 701 on SmartOS, been seeing this occasionally on those machines: test-net-server-max-connections.js https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/701/nodes=smartos14-64, who do we have for SmartOS? @jbergstroem, @geek, @misterdjules? Anyone care to have a look and consider why this might be a recurring problem?

New run that should have Windows greens, if not all-green: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/702/

@rvagg

Copy link
Copy Markdown
MemberAuthor

just remembered we have a @nodejs/platform-solaris; @misterdjules can we add you to that team as well?

@silverwind

Copy link
Copy Markdown
Contributor

I added semver-minor tags to #1699 and #1768 because it is an API change that's not going to break something. #1768 will land momentarily, and there'll be one more PR for the remaining methods, I'd like to get in. I'll get to it now.

@silverwind

Copy link
Copy Markdown
Contributor

Opened #1779 as the last in the series of return this things. Would like to get this in before release.

@misterdjules

Copy link
Copy Markdown

@rvagg I don't have the time right now to look at https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/701/nodes=smartos14-64 because I'm supposed to be on vacation and I still have a lot to do with node v0.12.x before I can actually get off my computer :) But definitely, please cc me on Solaris/SmartOS issues, hopefully I'll be in a better position to help next time.

I would also like to be part of the @nodejs/platform-solaris team, thanks for bringing that up!

@jbergstroem

Copy link
Copy Markdown
Member

@misterdjules I'm onto it! Just need to setup a new vm locally (and downloading with imgadm is currently painfully slow).

@misterdjules

Copy link
Copy Markdown

@jbergstroem Thank you 👍

@jbergstroem

Copy link
Copy Markdown
Member

I unfortunately can't reliably reproduce it outside of Jenkins; just tried running it 100 times without a fail on our 32-bit builder (as well as a local one). I'll bring this up on our next build meeting.

@jbergstroem

Copy link
Copy Markdown
Member

@rvagg: win32 + running as a service is pretty much what I was playing around with when tinkering around a few weeks ago – but we ended up with the same errors after a week passed. There's definitely something there though. Last time I stopped the windows service and ran it through nssm on command line. I think it adds it to windows services as well, but it at least worked for a while.

@silverwind

Copy link
Copy Markdown
Contributor

All return this PRs done. Suggesting this for the changelog:

  • To allow for chaining of methods, setTimeout, setKeepAlive, setNoDelay, ref, unref used in net, dgram, http, https and tls now return the current instance instead of undefined.

@rvagg

Copy link
Copy Markdown
MemberAuthor

this issue has been converted to a PR, see diff for the changelog entry for this release

https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/705/

moving on to release within an hour or two, consider this a warning if you have any pending concerns

Comment threadCHANGELOG.md Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change was split up in three PRs by Evan and me: #1699#1768#1779

@silverwind

Copy link
Copy Markdown
Contributor

Changelog LGTM besides those two points.

@Fishrock123

Copy link
Copy Markdown
Contributor

@rvagg Do I have time to land npm@2.10.1 before we push this out? #1763

(Just need to add to the squashed commit's changelog, but will wait on the go ahead from you.)

@rvagg
rvaggforce-pushed the v2.1.0-release branch 2 times, most recently from 7c92f3a to c71bad6CompareMay 23, 2015 23:38
@rvagg

Copy link
Copy Markdown
MemberAuthor

thanks for picking those up @silverwind, fixed now.

@Fishrock123 I'll wait for the npm merge, no rush, it'd be good to get it in

@Fishrock123

Copy link
Copy Markdown
Contributor

npm landed. 👍

PR-URL: nodejs#1532
Notable Changes:
* crypto: Diffie-Hellman key exchange (DHE) parameters ('dhparams') must now be
1024 bits or longer or an error will be thrown. A warning will also be printed
to the console if you supply less than 2048 bits. See https://weakdh.org/ for
further context on this security concern. (Shigeki Ohtsu) nodejs#1739.
* node: A new --trace-sync-io command line flag will print a warning and a stack
trace whenever a synchronous API is used. This can be used to track down
synchronous calls that may be slowing down an application.
(Trevor Norris) nodejs#1707.
* node: To allow for chaining of methods, the setTimeout(), setKeepAlive(),
setNoDelay(), ref() and unref() methods used in 'net', 'dgram', 'http',
'https' and 'tls' now return the current instance instead of undefined
(Roman Reiss & Evan Lucas) nodejs#1699nodejs#1768nodejs#1779.
* npm: Upgraded to v2.10.1, release notes can be found in
https://github.com/npm/npm/releases/tag/v2.10.1 and
https://github.com/npm/npm/releases/tag/v2.10.0.
* util: A significant speed-up (in the order of 35%) for the common-case of a
single string argument to util.format(), used by console.log()
(Сковорода Никита Андреевич) nodejs#1749.
@rvagg

Copy link
Copy Markdown
MemberAuthor

https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/706/

Running another test run, there was an odd failure on PI1 which I suspect is just a time-related issue but I just want to be sure, plus the npm update was merged.

Will push for a release after this.

@rvagg

Copy link
Copy Markdown
MemberAuthor

Windows 2008 failure - the particular machine rebooted with Windows Updates and went back in to Jenkins-as-a-service mode so the timeout failures are back! I've put it back in to cmd.exe mode.

test-cluster-disconnect.js failed on ARMv7, I'm going to call this an anomaly but it probably needs investigation.

Going ahead with release

rvagg added a commit that referenced this pull request May 24, 2015
PR-URL: #1777
Notable Changes:
* crypto: Diffie-Hellman key exchange (DHE) parameters ('dhparams') must now be
1024 bits or longer or an error will be thrown. A warning will also be printed
to the console if you supply less than 2048 bits. See https://weakdh.org/ for
further context on this security concern. (Shigeki Ohtsu) #1739.
* node: A new --trace-sync-io command line flag will print a warning and a stack
trace whenever a synchronous API is used. This can be used to track down
synchronous calls that may be slowing down an application.
(Trevor Norris) #1707.
* node: To allow for chaining of methods, the setTimeout(), setKeepAlive(),
setNoDelay(), ref() and unref() methods used in 'net', 'dgram', 'http',
'https' and 'tls' now return the current instance instead of undefined
(Roman Reiss & Evan Lucas) #1699#1768#1779.
* npm: Upgraded to v2.10.1, release notes can be found in
https://github.com/npm/npm/releases/tag/v2.10.1 and
https://github.com/npm/npm/releases/tag/v2.10.0.
* util: A significant speed-up (in the order of 35%) for the common-case of a
single string argument to util.format(), used by console.log()
(Сковорода Никита Андреевич) #1749.
@rvagg

Copy link
Copy Markdown
MemberAuthor

andrewdeandrade pushed a commit to andrewdeandrade/node that referenced this pull request Jun 3, 2015
PR-URL: nodejs/node#1777
Notable Changes:
* crypto: Diffie-Hellman key exchange (DHE) parameters ('dhparams') must now be
1024 bits or longer or an error will be thrown. A warning will also be printed
to the console if you supply less than 2048 bits. See https://weakdh.org/ for
further context on this security concern. (Shigeki Ohtsu) #1739.
* node: A new --trace-sync-io command line flag will print a warning and a stack
trace whenever a synchronous API is used. This can be used to track down
synchronous calls that may be slowing down an application.
(Trevor Norris) #1707.
* node: To allow for chaining of methods, the setTimeout(), setKeepAlive(),
setNoDelay(), ref() and unref() methods used in 'net', 'dgram', 'http',
'https' and 'tls' now return the current instance instead of undefined
(Roman Reiss & Evan Lucas) #1699 #1768 #1779.
* npm: Upgraded to v2.10.1, release notes can be found in
https://github.com/npm/npm/releases/tag/v2.10.1 and
https://github.com/npm/npm/releases/tag/v2.10.0.
* util: A significant speed-up (in the order of 35%) for the common-case of a
single string argument to util.format(), used by console.log()
(Сковорода Никита Андреевич) #1749.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

metaIssues and PRs related to the general management of the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@rvagg@Fishrock123@silverwind@misterdjules@jbergstroem@mscdex