-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
updates for v4.0 and minor tweaks #110
Conversation
LGTM 👍 |
Added some text to a release post, please review @mikeal and others, @nodejs/tsc perhaps? See the big locale/en/blog/release/v4.0.0.md file in this PR. |
Will review shortly. 10-15 minutes or so
|
<td></td> | ||
</tr> | ||
</thead> | ||
<tbody> | ||
{{#project.versions}} | ||
<tr> | ||
<td data-label="Version">{{version}}</td> | ||
<td data-label="Version">{{name}} {{version}}</td> | ||
<td data-label="Date"><time>{{date}}</time></td> | ||
<td data-label="V8">{{v8}}</td> | ||
<td data-label="NPM">{{npm}}</td> |
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.
Does it matter that the data-label
is still NPM
instead of npm
?
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.
seems to work, I just didn't dare touch it because I don't know what it's doing
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.
You can change that as well, it's just the label for the mobile table version.
you have time, I'm rerunning tests and making builds and whatnot since the late addition of the handle zapping change |
Added a new section on build/platforms/arm:
|
c36c1c4
to
a3437c2
Compare
Text looks good as well. |
Looks good on initial read through. Nothing major sticks out. |
+1 to what @jasnell said. |
|
||
Node.js v4.0.0 contains V8 v4.5, the same version of V8 shipping with the Chrome web browser today. This brings with it many bonuses for Node.js users, most notably a raft of new [ES6](https://nodejs.org/en/docs/es6/) features that are enabled by default including block scoping, classes, typed arrays, generators, Promises, Symbols, template strings, collections (Map, Set, etc.) and, new to V8 v4.5, arrow functions. | ||
|
||
Over the past year thanks to donations from companies such as Rackspace, DigitalOcean, Scaleway, miniNodes, Voxer, ARM Holdings, and individuals from the community, we've built an amazing test cluster that includes an impressive line-up of Linux variants, OS X, Windows, FreeBSD and SmartOS. New to Node.js, we also have first-class support for ARM processors. Our test suite must be continually passing on ARMv6, ARMv7 and the new 64-bit ARMv8 processors. So Node.js is officially ready for use by hobbyists and ARM server users alike. |
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.
Don't forget Cloudflare.
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.
whoops, and Joyent, added
|
||
In parallel, we will be releasing a new Stable line of releases every 6 months, one in October and one in April each year. Every second one of these, the April release, will continue life in LTS form by the time October comes around. This means that there will be overlapping LTS branches being maintained throughout the year, each receiving attention for a total of 30 months (LTS plus Maintenance). We believe that the Stable and LTS cycles provide the room for the project to continue its **innovation** and stay with the cutting-edge of JavaScript while also serving the need for **predictable long-term stability and security** demanded by the growing line-up of enterprise users proudly adopting Node.js as a key technology; some of who already count themselves as [members of the Node.js Foundation](https://nodejs.org/en/foundation/members/). | ||
|
||
As always with a major release, we don't expect the adoption of Node.js v4 to be painless. It will take time to adapt, particularly as compiled add-ons catch up with the new version of V8 (hint: see [NAN](https://github.com/nodejs/nan) for our official solution to the compatibility problem). Thankfully, the io.js v3.x series of releases have given many add-on authors a chance to prepare their code for Node.js v4, so much of the npm ecosystem is ready. |
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.
npm ecosystem is ready
"npm ecosystem is ready today."
Comments inline. Other than that, +1 |
}, | ||
{ | ||
"version": "v0.10.20", | ||
"date": |
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.
Can we just keep like a max of 3 releases in here? This file doesn't need to have them all when checked in to git.
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.
We need all release for the release history page: https://nodejs.org/en/download/releases/
|
||
Shasums: | ||
``` | ||
{{shasums}} |
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.
The list of release files and their corresponding shasums are missing, e.g. for v3.3.0: https://iojs.org/dist/v3.3.0/SHASUMS256.txt.asc
For all I know you havent done the final build yet?
Put a versions.json in here for v4 and couldn't help but fix up a bunch of things: