| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Responsible parties as far as I can tell are:
Folks, please push on getting your PRs merged if you can so we can get this out. |
Sorry, something went wrong.
Ok, landed that.
I would like to see the CI results after that lands. |
Sorry, something went wrong.
|
Thanks for opening this, @rvagg. I'd like to also propose #1513 as part of this release, since I think folks will open up the repl and type class XYZ {} immediately upon installing :) Otherwise, #1506 is waiting on a LGTM from @bnoordhuis or @indutny. I'm working on documenting the V8 upgrade process in a separate branch. |
Sorry, something went wrong.
|
also on the list is an item from @evanlucas who needs to fix the build for us now that it's failing on most test machines due to an ipv6 problem as per #1527 |
Sorry, something went wrong.
|
I think it's time to set a deadline on this. We are several weeks behind V8 and a new Chrome/V8 will be coming relatively soon. We should just merge the V8 upgrade and anything else that is ready and do a release, say, tomorrow. Anything that missed the train can hop on the next one in a few weeks. No need to hold things up waiting for all our ducks to line up. |
Sorry, something went wrong.
|
Also if someone broke the build we should immediately revert that patch instead of waiting for a fix. |
Sorry, something went wrong.
|
@domenic myself, @jbergstroem and @evanlucas are working on the broken build side, it's a bit more complicated than just a single thing but rest assured that if it comes to just reverting then that'll be done, we must get off red builds. |
Sorry, something went wrong.
|
master should be back to green now (literally green thanks to a Jenkins plugin): https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/631/ Note that we've also got Fedora 21, Debian 8 and Ubuntu 15.04 in the CI set now. |
Sorry, something went wrong.
|
A failure I haven't seen before, on one of the Windows slaves: not ok 637 - test-timers-first-fire.js
#
#assert.js:88
# throw new assert.AssertionError({
# ^
#AssertionError: Timer fired early
# at null._onTimeout (c:\workspace\iojs+any-pr+multi\nodes\win2008r2\test\parallel\test-timers-first-fire.js:11:10)
# at Timer.listOnTimeout (timers.js:89:15)
#timer fired in -0.6199840000000023
@piscisaureus, @trevnorris, @bnoordhuis or other, do you have any idea if this is relevant? setTimeout() set for 50, fires 0.6 ms early but the assertion is looking for it to be 0.6 ms early or smaller, possibly positive; i.e. delta > 0.5. To be honest I don't really understand the point of this test even with the comments in the original commit, 93b0624. |
Sorry, something went wrong.
|
I suspect that's a bug in the Windows implementation of uv_hrtime(); it uses floating point math that may be lossy. I believe there is a libuv issue about it but I can't find it.
delta > -0.5 :-) Which is a somewhat dubious change that (IIRC) Trevor made; it used to check that delta > 0. |
Sorry, something went wrong.
|
OK, now we're getting somewhere, we have the V8 upgrade in, at 4.2.77.18 and our first 2.0.0 release candidate is at: https://iojs.org/download/nightly/v2.0.0-nightly20150428509b59ea7c/ I'll start writing up some notable changes in here. @petkaantonov is still working on the url changes in #933 and has hit some snags, hopefully that'll be sorted within a couple of days. @bnoordhuis has the process.send() changes to land in #774 but given the state of the tests on Windows for that change and how busy Ben is we may be punting on that change to 3.0.0. |
Sorry, something went wrong.
|
I think we should set a deadline so as to avoid the failure mode of "X is almost ready, just give it a few more days." |
Sorry, something went wrong.
|
If someone wants to adopt #774, s/he has my blessing. |
Sorry, something went wrong.
For me a deadline 2 days from now is fine. |
Sorry, something went wrong.
|
Converted this to a pull request so I can submit my CHANGELOG changes for review. @domenic can you have a look at the V8 4.2 notable items I've listed please? |
Sorry, something went wrong.
|
https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/634/ CI looking pretty good |
Sorry, something went wrong.
There was a problem hiding this comment.
s/,/;
Also want to mention object literal extensions (concise methods and property shorthands).
Maybe mention that like let and const, class is only usable in strict mode.
Sorry, something went wrong.
There was a problem hiding this comment.
Did we get those free when they enabled classes such that we can use them in POJSO's too? { foo() { return 'bar' } }? Would you mind having a quick go at some words for this for me?
Sorry, something went wrong.
There was a problem hiding this comment.
OK, did some experimenting and answered my own question console.log({woo(){return "woot!"}}.woo()), nice. I'd still appreciate some words from you on this @domenic if you don't mind.
Sorry, something went wrong.
There was a problem hiding this comment.
Let's try
Sorry, something went wrong.
There was a problem hiding this comment.
classes only in strict mode
Sorry, something went wrong.
Sorry, something went wrong.
V8 4.2 introduces some minor C++ API changes that make it necessary for many native add-ons to recompile in order to be usable in v2.0.0+ PR-URL: nodejs#1532
|
I think the CI is ok. |
Sorry, something went wrong.
|
yeah, just going through the motions now, which is mostly about sorting out the changelog docs and testing the build process |
Sorry, something went wrong.
There was a problem hiding this comment.
maybe link to #1451?
Sorry, something went wrong.
There was a problem hiding this comment.
done, ptal
Sorry, something went wrong.
V8 4.2 introduces some minor C++ API changes that make it necessary for many native add-ons to recompile in order to be usable in v2.0.0+ PR-URL: nodejs#1532
There was a problem hiding this comment.
Classes are still strict-mode only.
Object literals appear to be in regular mode? Still testing..
Sorry, something went wrong.
There was a problem hiding this comment.
Reason we might want to mention this is so we don't get questions why it doesn't work yet.
Sorry, something went wrong.
There was a problem hiding this comment.
Object literals work in sloppy, except for computed props, which do not appear to exist in any non-flagged mode yet.
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
PR-URL: #1532 Notable Changes: * crypto: significantly reduced memory usage for TLS (Fedor Indutny & Сковорода Никита Андреевич) #1529 * net: socket.connect() now accepts a 'lookup' option for a custom DNS resolution mechanism, defaults to dns.lookup() (Evan Lucas) #1505 * npm: Upgrade npm to 2.9.0. See the v2.8.4 and v2.9.0 release notes for details. Notable items: - Add support for default author field to make npm init -y work without user-input (@othiym23) npm/npm/d8eee6cf9d - Include local modules in npm outdated and npm update (@ArnaudRinquin) npm/npm#7426 - The prefix used before the version number on npm version is now configurable via tag-version-prefix (@kkragenbrink) npm/npm#8014 * os: os.tmpdir() is now cross-platform consistent and will no longer returns a path with a trailling slash on any platform (Christian Tellnes) #747 * process: - process.nextTick() performance has been improved by between 2-42% across the benchmark suite, notable because this is heavily used across core (Brian White) #1548 - New process.geteuid(), process.seteuid(id), process.getegid() and process.setegid(id) methods allow you to get and set effective UID and GID of the process (Evan Lucas) #1536 * repl: - REPL history can be persisted across sessions if the NODE_REPL_HISTORY_FILE environment variable is set to a user accessible file, NODE_REPL_HISTORY_SIZE can set the maximum history size and defaults to 1000 (Chris Dickinson) #1513 - The REPL can be placed in to one of three modes using the NODE_REPL_MODE environment variable: sloppy, strict or magic (default); the new magic mode will automatically run "strict mode only" statements in strict mode (Chris Dickinson) #1513 * smalloc: the 'smalloc' module has been deprecated due to changes coming in V8 4.4 that will render it unusable * util: add Promise, Map and Set inspection support (Christopher Monsanto) #1471 * V8: upgrade to 4.2.77.18, see the ChangeLog for full details. Notable items: - Classes have moved out of staging; the class keyword is now usable in strict mode without flags - Object literal enhancements have moved out of staging; shorthand method and property syntax is now usable ({ method() { }, property }) - Rest parameters (function(...args) {}) are implemented in staging behind the --harmony-rest-parameters flag - Computed property names ({['foo'+'bar']:'bam'}) are implemented in staging behind the --harmony-computed-property-names flag - Unicode escapes ('\u{xxxx}') are implemented in staging behind the --harmony_unicode flag and the --harmony_unicode_regexps flag for use in regular expressions * Windows: - Random process termination on Windows fixed (Fedor Indutny) #1512 / #1563 - The delay-load hook introduced to fix issues with process naming (iojs.exe / node.exe) has been made opt-out for native add-ons. Native add-ons should include 'win_delay_load_hook': 'false' in their binding.gyp to disable this feature if they experience problems . (Bert Belder) #1433 * Governance: - Rod Vagg (@rvagg) was added to the Technical Committee (TC) - Jeremiah Senkpiel (@Fishrock123) was added to the Technical Committee (TC)
|
tagged @ 7c89c4c building @ https://jenkins-iojs.nodesource.com/job/iojs+release/62/ |
Sorry, something went wrong.
|
All looks fine, armv6 is there too. thanks @rvagg |
Sorry, something went wrong.
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) nodejs#1779. * 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.
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#1699 nodejs#1768 nodejs#1779. * 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.
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#1699 nodejs#1768 nodejs#1779. * 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.
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#1699 nodejs#1768 nodejs#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.
| Back | FazBrowse Home | New Git URL |
This is very early but we're risking a long period of time with no release and a build-up of changes so we need to push to get this out.
Main issues for this release are in the 2.0.0 milestone. Note that the V8 upgrade still isn't in master, see #1506 for that.