-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2016-04-26, Version 6.0.0 (Current) Release #6383
Conversation
Also, #3743 just landed |
minor nit:
makes it sound like it was using libuv before, but less efficiently. How about:
? |
#6352 just landed. |
the greatest news in this morning! |
* Windows | ||
* Windows XP and Vista are no longer supported | ||
[#5167](https://github.com/nodejs/node/pull/5167), | ||
[#5167](https://github.com/nodejs/node/pull/5167). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think this was pointed out before in the RCs, but this link is duplicated
This comment was marked as abuse.
This comment was marked as abuse.
Re the workaround, please note https://twitter.com/ljharb/status/724815514338512897 |
Still not comfortable with the |
@ljharb ... regarding nvm... it's being proposed in this release to change from using the label |
f5f573f
to
c53d296
Compare
Rebased and updated. Will Rebase and update again shortly. |
Looks like the foundation is already doing messaging in favor of this: nodejs/nodejs.org#672 (comment) Rest in peace, |
c53d296
to
81ddc5c
Compare
@jasnell no, "stable" is a synonym for "node", and i won't be adding "current" - "node" is what people should be using for "latest". "stable" is a pre-semver concept anyways, as version numbers don't convey stability in semver, so I'm glad it's being removed. "stable" will remain for awhile as a legacy default alias, just like "unstable" does (pointing to 0.11). |
Ok, calling time on things getting into v6 now. I've got a few more cleanups to do, then will start the smoke testing and build process. Thanks all! |
81ddc5c
to
4972db3
Compare
Initial CI run : https://ci.nodejs.org/job/node-test-pull-request/2402/ (does not include #6402) |
Initial citgm run: https://ci.nodejs.org/view/Node.js-citgm/job/thealphanerd-smoker/216/ edit: it is worth mentioning that we should expect failures in both The |
New run to hopefully get a good centos build: https://ci-release.nodejs.org/job/iojs+release/555/ |
OSX is done. There is some unexpected stuff going on in request that I am digging into... it looks like it might be related to some changes affecting fsevents. I'll update this comment with the investigation. |
da92e3a
to
548e5ba
Compare
The following significant (semver-major) changes have been made since the previous Node v5.0.0 release. * Buffer * New Buffer constructors have been added [#4682](#4682) * Previously deprecated Buffer APIs are removed [#5048](#5048), [#4594](#4594) * Improved error handling [#4514](#4514) * Cluster * Worker emitted as first argument in 'message' event [#5361](#5361). * Crypto * Improved error handling [#3100](#3100), [#5611](#5611) * Simplified Certificate class bindings [#5382](#5382) * Improved control over FIPS mode [#5181](#5181) * pbkdf2 digest overloading is deprecated [#4047](#4047) * Dependencies * Reintroduce shared c-ares build support [#5775](#5775). * V8 updated to 5.0.71.31 [#6111](#6111). * DNS * Add resolvePtr API to query plain DNS PTR records [#4921](#4921). * Domains * Clear stack when no error handler [#4659](#4659). * File System * The `fs.realpath()` and `fs.realpathSync()` methods have been updated to use a more efficient libuv implementation. This change includes the removal of the `cache` argument and the method can throw new errors [#3594](#3594) * FS apis can now accept and return paths as Buffers [#5616](#5616). * Error handling and type checking improvements [#5616](#5616), [#5590](#5590), [#4518](#4518), [#3917](#3917). * fs.read's string interface is deprecated [#4525](#4525) * HTTP * 'clientError' can now be used to return custom errors from an HTTP server [#4557](#4557). * Modules * Current directory is now prioritized for local lookups [#5689](#5689) * Symbolic links are preserved when requiring modules [#5950](#5950) * Net * DNS hints no longer implicitly set [#6021](#6021). * Improved error handling and type checking [#5981](#5981), [#5733](#5733), [#2904](#2904) * OS X * MACOSX_DEPLOYMENT_TARGET has been bumped up to 10.7 [#6402](#6402). * Path * Improved type checking [#5348](#5348). * Process * Introduce process warnings API [#4782](#4782). * Throw exception when non-function passed to nextTick [#3860](#3860). * Readline * Emit key info unconditionally [#6024](#6024) * REPL * Assignment to `_` will emit a warning. [#5535](#5535) * Timers * Fail early when callback is not a function [#4362](#4362) * TLS * Rename 'clientError' to 'tlsClientError' [#4557](#4557) * SHA1 used for sessionIdContext [#3866](#3866) * TTY * Previously deprecated setRawMode wrapper is removed [#2528](#2528). * Util * Changes to Error object formatting [#4582](#4582). * Windows * Windows XP and Vista are no longer supported [#5167](#5167), [#5167](#5167).
548e5ba
to
37f2f03
Compare
New Release Build Run: https://ci-release.nodejs.org/job/iojs+release/557/ |
(fingers crossed Jenkins behaves) |
GitHub needs fingers crossed reaction? Lol. |
It definitely needs "Hold your Breath" and "Rage Quit" reactions for sure |
Can I ask anyone who is waiting for this build to complete to do some extra testing of |
@jasnell are you building of "v6.0.0-proposal"? The test case for tick processor is failing again on OSX El Capitan 10.11.5 - and so is "master". |
@dnalborczyk, no, building off v6.x |
Done! Released! |
That face when the changelog file too big for GitHub to display now. |
Reference: nodejs/node#6383
@jamen that just got fixed! |
You sure about that? Link from the website actually still displays as too big for me. Though the one in the repo seems to work. Linking to different branch? |
@jamen: yeah, it was fixed in master, need to backport that change into v6 now tho ;-) It might be the first backport into v6 |
@jasnell @Fishrock123 Hi, Debian and Ubuntu based Linux distributions package-manager not found setup_6.x =) |
@jasnell Can this branch be deleted now? |
more general question: can we delete all the |
Yep! I was planning to do some housekeeping today and clean those up, but
|
Noticed that the 6.0.0 change log was missing an entry for this fix: #4222 Node ignoring redirections when redirected to a tty It was part of the libuv 1.9.0 merge. |
Yeah it seems the change log is missing quite a few commits, just not quite
|
@nodejs/ctc @nodejs/collaborators ... Please take a good look at the notable changes. There are some updates that need to be made and likely stuff that I missed. I will be cutting the v6 release tomorrow morning.
The following significant (semver-major) changes have been made since the
previous Node v5.0.0 release.
#4682
#5048,
#4594
#5361.
#5611
#5382
#5181
#4047
#5775.
#4921.
#4659.
fs.realpath()
andfs.realpathSync()
methods have been updatedto use a more efficient libuv implementation. This change includes the
removal of the
cache
argument and the method can throw new errors#3594
#5616.
#5616,
#5590,
#4518,
#3917.
#4525
HTTP server #4557.
#5689
#5950
#6021.
#5981,
#5733,
#2904
#4782.
#3860.
#6024
_
will emit a warning.#5535
#4362
#4557
#3866
#2528.
#4582.
#5167,
#5167.