node: rename from io.js to node

This commit replaces instances of io.js with Node.js, based on the
recent convergence. There are some remaining instances of io.js,
related to build and the installer.

Fixes: https://github.com/nodejs/node/issues/2361
PR-URL: https://github.com/nodejs/node/pull/2367
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: João Reis <reis@janeasystems.com>

1 files changed, 15 insertions, 15 deletions

diff --git a/ROADMAP.md b/ROADMAP.md
index 04254859d9..51b87ae624 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -1,4 +1,4 @@
-# io.js Roadmap
+# Node.js Roadmap
 
 ***This is a living document, it describes the policy and priorities as they exist today but can evolve over time.***
 
@@ -6,15 +6,15 @@
 
 The most important consideration in every code change is the impact it will have, positive or negative, on the ecosystem (modules and applications).
 
-io.js does not remove stdlib JS API.
+Node.js does not remove stdlib JS API.
 
-Shipping with current and well supported dependencies is the best way to ensure long term stability of the platform. When those dependencies are no longer maintained io.js will take on their continued maintenance as part of our [Long Term Support policy](#long-term-support).
+Shipping with current and well supported dependencies is the best way to ensure long term stability of the platform. When those dependencies are no longer maintained Node.js will take on their continued maintenance as part of our [Long Term Support policy](#long-term-support).
 
-io.js will continue to adopt new V8 releases.
+Node.js will continue to adopt new V8 releases.
 * When V8 ships a breaking change to their C++ API that can be handled by [`nan`](https://github.com/rvagg/nan)
-the *minor* version of io.js will be increased.
+the *minor* version of Node.js will be increased.
 * When V8 ships a breaking change to their C++ API that can NOT be handled by [`nan`](https://github.com/rvagg/nan)
-the *major* version of io.js will be increased.
+the *major* version of Node.js will be increased.
 * When new features in the JavaScript language are introduced by V8 the
 *minor* version number will be increased. TC39 has stated clearly that no
 backwards incompatible changes will be made to the language so it is
@@ -26,23 +26,23 @@ Any API addition will cause an increase in the *minor* version.
 
 ### Long Term Support
 
-io.js supports old versions for as long as community members are fixing bugs in them.
+Node.js supports old versions for as long as community members are fixing bugs in them.
 
-As long as there is a community back porting bug fixes we will push patch releases for those versions of io.js.
+As long as there is a community back porting bug fixes we will push patch releases for those versions of Node.js.
 
-When old versions of dependencies like V8 are no longer supported by their project io.js will take on the responsibility of maintenance to ensure continued long term support in io.js patch releases.
+When old versions of dependencies like V8 are no longer supported by their project Node.js will take on the responsibility of maintenance to ensure continued long term support in Node.js patch releases.
 
 ## Channels
 
 Channels are points of collaboration with the broader community and are not strictly scoped to a repository or branch.
 
 * Release - Stable production ready builds. Unique version numbers following semver.
-* Canary - Nightly builds w/ V8 version in Chrome Canary + changes landing to io.js. No version designation.
+* Canary - Nightly builds w/ V8 version in Chrome Canary + changes landing to Node.js. No version designation.
 * NG - "Next Generation." No version designation.
 
 ## NG (Next Generation)
 
-In order for io.js to stay competitive we need to work on the next generation of the platform which will more accurately integrate and reflect the advancements in the language and the ecosystem.
+In order for Node.js to stay competitive we need to work on the next generation of the platform which will more accurately integrate and reflect the advancements in the language and the ecosystem.
 
 While this constitutes a great leap forward for the platform we will be making this leap without breaking backwards compatibility with the existing ecosystem of modules.
 
@@ -50,9 +50,9 @@ While this constitutes a great leap forward for the platform we will be making t
 
 ## Debugging and Tracing
 
-Debugging is one of the first things from everyone's mouth, both developer and enterprise, when describing trouble they've had with node.js/io.js.
+Debugging is one of the first things from everyone's mouth, both developer and enterprise, when describing trouble they've had with Node.js.
 
-The goal of io.js' effort is to build a healthy debugging and tracing ecosystem and not to try and build any "silver bullet" features for core (like the domains debacle).
+The goal of Node.js' effort is to build a healthy debugging and tracing ecosystem and not to try and build any "silver bullet" features for core (like the domains debacle).
 
 The [Tracing WG](https://github.com/nodejs/tracing-wg) is driving this effort:
 
@@ -60,8 +60,8 @@ The [Tracing WG](https://github.com/nodejs/tracing-wg) is driving this effort:
 * async-listener - userland module that will dogfood AsyncWrap as well as provide many often requested debugging features.
 * Tracing
   * Add tracing support for more platforms (LTTng, etc).
-  * [Unify the Tracing endpoint](https://github.com/nodejs/io.js/issues/729).
-  * New Chrome Debugger - Google is working on a version of Chrome's debugger that is without Chrome and can be used with io.js.
+  * [Unify the Tracing endpoint](https://github.com/nodejs/node/issues/729).
+  * New Chrome Debugger - Google is working on a version of Chrome's debugger that is without Chrome and can be used with Node.js.
 
 ## Ecosystem Automation