updates for v4.0 and minor tweaks #110

rvagg · 2015-09-08T12:06:02Z

Put a versions.json in here for v4 and couldn't help but fix up a bunch of things:

put the name in the downloads list, Node.js or io.js
put a correct download URL
change a whole lot of "node.js" to "Node.js", sorry, I've got a beef with this one, does anyone object? @mikeal, @fhemberger?
change NPM to npm in the header of the downloads table

fhemberger · 2015-09-08T13:06:00Z

LGTM 👍

rvagg · 2015-09-08T13:12:10Z

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.

jasnell · 2015-09-08T13:18:40Z

Will review shortly. 10-15 minutes or so
On Sep 8, 2015 2:12 PM, "Rod Vagg" [email protected] wrote:

Added some text to a release post, please review @mikeal
https://github.com/mikeal and others, @nodejs/tsc
https://github.com/orgs/nodejs/teams/tsc perhaps? See the big
locale/en/blog/release/v4.0.0.md file in this PR.

—
Reply to this email directly or view it on GitHub
#110 (comment)
.

evanlucas · 2015-09-08T13:21:53Z

layouts/download-releases.hbs

                                <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>


Does it matter that the data-label is still NPM instead of npm?

seems to work, I just didn't dare touch it because I don't know what it's doing

You can change that as well, it's just the label for the mobile table version.

rvagg · 2015-09-08T13:27:27Z

you have time, I'm rerunning tests and making builds and whatnot since the late addition of the handle zapping change

rvagg · 2015-09-08T13:39:01Z

Added a new section on build/platforms/arm:

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.

fhemberger · 2015-09-08T13:53:30Z

Text looks good as well.

jasnell · 2015-09-08T14:13:49Z

Looks good on initial read through. Nothing major sticks out.

cjihrig · 2015-09-08T14:31:46Z

+1 to what @jasnell said.

mikeal · 2015-09-08T14:45:39Z

locale/en/blog/release/v4.0.0.md

+
+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.


Don't forget Cloudflare.

whoops, and Joyent, added

mikeal · 2015-09-08T14:47:32Z

locale/en/blog/release/v4.0.0.md

+
+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.


npm ecosystem is ready

"npm ecosystem is ready today."

mikeal · 2015-09-08T14:49:18Z

Comments inline. Other than that, +1

Fishrock123 · 2015-09-08T14:57:53Z

source/versions.json

+  },
+  {
+    "version": "v0.10.20",
+    "date": 


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.

We need all release for the release history page: https://nodejs.org/en/download/releases/

phillipj · 2015-09-08T18:44:51Z

locale/en/blog/release/v4.0.0.md

+
+Shasums:
+```
+{{shasums}}


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?

evanlucas reviewed Sep 8, 2015
View reviewed changes

rvagg added 4 commits September 8, 2015 23:44

updates for v4.0 and minor tweaks

4b25e48

v4.0.0 release post basic

3e72c0f

v4.0.0 release post prose

0907013

added section on build/platforms/arm

a3437c2

rvagg force-pushed the 4.0-updates-rvagg branch from c36c1c4 to a3437c2 Compare September 8, 2015 13:44

mikeal reviewed Sep 8, 2015
View reviewed changes

added cloudflare and joyent

0b192e6

mikeal reviewed Sep 8, 2015
View reviewed changes

minor copy edit

a5414ae

Fishrock123 reviewed Sep 8, 2015
View reviewed changes

4.0.0 release post: addressed @Fishrock123's edit suggestions

8bbb0c2

rvagg mentioned this pull request Sep 8, 2015

Node.js v4 Release Timeline nodejs/node#2522

Closed

10 tasks

phillipj reviewed Sep 8, 2015
View reviewed changes

added shasums for 4.0.0

e2ca337

rvagg merged commit e2ca337 into node-4.0-release Sep 8, 2015

rvagg deleted the 4.0-updates-rvagg branch September 8, 2015 19:11

bnb mentioned this pull request Nov 12, 2015

Call for Speakers nodejs/evangelism#87

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

updates for v4.0 and minor tweaks #110

updates for v4.0 and minor tweaks #110

rvagg commented Sep 8, 2015

fhemberger commented Sep 8, 2015

rvagg commented Sep 8, 2015

jasnell commented Sep 8, 2015

evanlucas Sep 8, 2015

rvagg Sep 8, 2015

fhemberger Sep 8, 2015

rvagg commented Sep 8, 2015

rvagg commented Sep 8, 2015

fhemberger commented Sep 8, 2015

jasnell commented Sep 8, 2015

cjihrig commented Sep 8, 2015

mikeal Sep 8, 2015

rvagg Sep 8, 2015

mikeal Sep 8, 2015

mikeal commented Sep 8, 2015

Fishrock123 Sep 8, 2015

fhemberger Sep 8, 2015

phillipj Sep 8, 2015


		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.


		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.

updates for v4.0 and minor tweaks #110

updates for v4.0 and minor tweaks #110

Conversation

rvagg commented Sep 8, 2015

fhemberger commented Sep 8, 2015

rvagg commented Sep 8, 2015

jasnell commented Sep 8, 2015

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rvagg commented Sep 8, 2015

rvagg commented Sep 8, 2015

fhemberger commented Sep 8, 2015

jasnell commented Sep 8, 2015

cjihrig commented Sep 8, 2015

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mikeal commented Sep 8, 2015

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment