| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
RC.0 Build Underway: https://ci-release.nodejs.org/job/iojs+release/2125/ |
Sorry, something went wrong.
| <a href="doc/changelogs/CHANGELOG_V8.md#8.0.0">8.0.0</a><br/> | ||
| </td> | ||
| <td valign="top"> | ||
| <b><a href="doc/changelogs/CHANGELOG_V7.md#7.10.1">7.10.1</a></b><br/> |
There was a problem hiding this comment.
Why are we removing 7?
Sorry, something went wrong.
There was a problem hiding this comment.
For the same reason 5 is not listed. The changelogs are still there and accessible
Sorry, something went wrong.
|
@jasnell can you include the list of commits here as it currently stands. |
Sorry, something went wrong.
|
Yes. Will be updating this later on today with a plan towards having a new RC. It'll likely be later this afternoon as I'm waiting on the security release to be finished before I start on it. |
Sorry, something went wrong.
|
All @nodejs/collaborators @nodejs/TSC ... I will be updating from master one final time tomorrow before working on generating and testing the release binaries. The release will happen on Tuesday. @nodejs/build ... Heads up :) |
Sorry, something went wrong.
|
#16589 should get in before release to ease compatibility with future readable-stream releases. |
Sorry, something went wrong.
|
I would like to get a bunch of the http2 fixes in if possible, since they're pretty major. #16575, #16525 and #16580 That said, it's not a must :) so depends on timing |
Sorry, something went wrong.
|
@nodejs/collaborators @nodejs/tsc ... definitely last call. I will be doing one final rebase from master this afternoon after noon pacific time (just over one hour from now). Unless it is an absolutely critical bug fix, if it doesn't land by noon, it won't make it in to 9.0.0 |
Sorry, something went wrong.
|
@nodejs/collaborators @nodejs/tsc ... I've completed what should be the final update. I will build a final RC in the morning, do some testing, then will build the release binaries by end of day, with intent of promoting those first thing tuesday morning. Please take one final look. |
Sorry, something went wrong.
|
Oh, sorry. I completely forgot to land #16318 As discussed in #15454 (comment) and in the TSC meeting this should be part of the v9.0 release. edit: landed in 23a3911 |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/11094/ |
Sorry, something went wrong.
| * [[`2249234fee`](https://github.com/nodejs/node/commit/2249234fee)] - **(SEMVER-MAJOR)** **fs**: invoke callbacks with undefined context (Rich Trott) [#14645](https://github.com/nodejs/node/pull/14645) | ||
| * [[`f2f391e575`](https://github.com/nodejs/node/commit/f2f391e575)] - **(SEMVER-MAJOR)** **http**: send 400 bad request on parse error (mog422) [#15324](https://github.com/nodejs/node/pull/15324) | ||
| * [[`10be20a0e8`](https://github.com/nodejs/node/commit/10be20a0e8)] - **(SEMVER-MAJOR)** **http**: set socket timeout when socket connects (Luigi Pinca) [#8895](https://github.com/nodejs/node/pull/8895) | ||
| * [[`620ba41694`](https://github.com/nodejs/node/commit/620ba41694)] - **(SEMVER-MAJOR)** **http**: don't double-fire the req error event (fengmk2) [#14659](https://github.com/nodejs/node/pull/14659) |
There was a problem hiding this comment.
PR-URL should be #14333
Sorry, something went wrong.
|
@jasnell you wanted confirmation that #16130 didn't have anything that would prevent it from landing as semver-minor after 9.0.0 goes out (i.e. so there's no rush to bundle it here). This is that confirmation, and if I'm wrong, then we'll force it to be semver-minor! |
Sorry, something went wrong.
|
A handful of concerning fails on CITGM Most alarming is a module resolution failure in david on all platforms Other less worrying problems include: 1 failing
1) socket.monitor should read multiple events on monitor interval:
Uncaught AssertionError: expected 7 to be within 0..5
at Assertion.fail (node_modules\should\cjs\should.js:265:17)
at Assertion.value [as within] (node_modules\should\cjs\should.js:340:19)
at exports.Socket.<anonymous> (test\socket.monitor.js:103:22)
at Object.self._zmq.onMonitorEvent (lib\index.js:543:12)
undefinedadded 190 packages in 23.23s > shot@4.0.3 test /Users/iojs/build/workspace/citgm-smoker/nodes/osx1010/citgm_tmp/2d905b84-8e9e-4015-ba29-ec9013f618ba/shot > lab -a code -t 100 -L ............................................ 44 tests complete Test duration: 431 ms Assertions count: 0 (verbosity: 0.00) The following leaks were detected:SharedArrayBuffer, Atomics Coverage: 100.00% Linting results: No issues npm ERR! Test failed. See above for more details. |
Sorry, something went wrong.
|
Should tools/remark-cli be added to LICENSE (i.e. as we do for tools/eslint)? |
Sorry, something went wrong.
|
The shot failures aren't real. SharedArrayBuffer and Atomics are globals that just haven't been whitelisted by lab yet (hapijs/lab#748). |
Sorry, something went wrong.
|
Build is failing on Windows. Tracking it down now. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Yep. Awesome, hadn't seen that pr yet. I may just drop the errant commit
then
…On Oct 31, 2017 07:41, "Anna Henningsen" ***@***.***> wrote:
@jasnell <https://github.com/jasnell> I’d *assume* that’s #16639
<#16639>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15135 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAa2ec3uzo0BewqV7LQR-OM7qPHd5T2Vks5sxzGBgaJpZM4PKZRg>
.
|
Sorry, something went wrong.
|
This is currently waiting on #16634 and the 8.9.0 release. 8.9.0 needs to go out first so that I can update the changelog since there is some overlap in the commits. |
Sorry, something went wrong.
|
New CI: https://ci.nodejs.org/job/node-test-pull-request/11120/ |
Sorry, something went wrong.
|
Once 8.9.0 is released, I will update the changelog in this then proceed with the release. |
Sorry, something went wrong.
|
@gibfahn ... please ping me here once 8.9.0 is out :-) |
Sorry, something went wrong.
* Older experimental APIs have been removed.
[[`d731369b1d`](d731369b1d)]
[#14414](#14414)
* **Errors**
* Improvements have been made to `buffer` module error messages.
* The assignment of static error codes to Node.js error continues:
* `buffer`
* `child_process`
* `console`
* `crypto`
* `dns`
* `events`
* `fs`
* `http`
* `inspector`
* `net`
* `path`
* `process`
* `querystring`
* `readline`
* `repl`
* `streams`
* `string_decoder`
* `timers`
* `tls`
* `url`
* `util`
* `v8`
* `zlib`
* **Child Processes**
* Errors are emitted on process nextTick.
* **Domains**
* The long-deprecated `.dispose()` method has been removed.
* **fs**
* The `fs.ReadStream` and `fs.WriteStream` classes now use `destroy()`.
* `fs` module callbacks are now invoked with an undefined context.
* **HTTP/1**
* A 400 Bad Request response will now be sent when parsing fails.
* Socket timeout will be set when the socket connects.
* A bug causing the request `'error'` event to fire twice was fixed.
* HTTP clients may now use generic `Duplex` streams in addition to `net.Socket`.
* **Intl**
* The deprecated `Intl.v8BreakIterator` has been removed.
* **Modules**
* The `require.resolve()` method now supports using custom lookup paths.
* **OS**
* The `os.EOL` property is now read-only.
* **Timers**
* `setTimeout()` will emit a warning if the timeout is larger that the maximum
32-bit unsigned integer.
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #15135
|
@jasnell armv6l binaries are in staging, can you promote please? |
Sorry, something went wrong.
* Older experimental APIs have been removed.
[[`d731369b1d`](d731369b1d)]
[#14414](#14414)
* **Errors**
* Improvements have been made to `buffer` module error messages.
* The assignment of static error codes to Node.js error continues:
* `buffer`
* `child_process`
* `console`
* `crypto`
* `dns`
* `events`
* `fs`
* `http`
* `inspector`
* `net`
* `path`
* `process`
* `querystring`
* `readline`
* `repl`
* `streams`
* `string_decoder`
* `timers`
* `tls`
* `url`
* `util`
* `v8`
* `zlib`
* **Child Processes**
* Errors are emitted on process nextTick.
* **Domains**
* The long-deprecated `.dispose()` method has been removed.
* **fs**
* The `fs.ReadStream` and `fs.WriteStream` classes now use `destroy()`.
* `fs` module callbacks are now invoked with an undefined context.
* **HTTP/1**
* A 400 Bad Request response will now be sent when parsing fails.
* Socket timeout will be set when the socket connects.
* A bug causing the request `'error'` event to fire twice was fixed.
* HTTP clients may now use generic `Duplex` streams in addition to `net.Socket`.
* **Intl**
* The deprecated `Intl.v8BreakIterator` has been removed.
* **Modules**
* The `require.resolve()` method now supports using custom lookup paths.
* **OS**
* The `os.EOL` property is now read-only.
* **Timers**
* `setTimeout()` will emit a warning if the timeout is larger that the maximum
32-bit unsigned integer.
| Back | FazBrowse Home | New Git URL |
Commits
DetailsSemver-Major
Semver-minor
Semver-patch