tag | b16b5817d24cb9ddd4817a20648f93a090f574dd | |
---|---|---|
tagger | Rod Vagg <rod@vagg.org> | Wed Feb 11 02:49:41 2015 |
object | 69b5922b310452ae13a6f799f6fbc1c9c643754b |
2015-02-10 io.js v1.2.0 Release
commit | 69b5922b310452ae13a6f799f6fbc1c9c643754b | [log] [tgz] |
---|---|---|
author | Rod Vagg <rod@vagg.org> | Wed Feb 11 01:41:07 2015 |
committer | Rod Vagg <rod@vagg.org> | Wed Feb 11 02:48:17 2015 |
tree | f79d7d3f0c35cea5cd0baa8f60435cab4bba9d3e | |
parent | 7e2235aebb067b84974e001f9fa4d83f45b7c9dd [diff] |
2015-02-10 io.js v1.2.0 Release Notable changes: * stream: - Simpler stream construction, see https://github.com/iojs/readable-stream/issues/102 for details. This extends the streams base objects to make their constructors accept default implementation methods, reducing the boilerplate required to implement custom streams. An updated version of readable-stream will eventually be released to match this change in core. (@sonewman) * dns: - `lookup()` now supports an `'all'` boolean option, default to `false` but when turned on will cause the method to return an array of *all* resolved names for an address, see, https://github.com/iojs/io.js/pull/744 (@silverwind) * assert: - Remove `prototype` property comparison in `deepEqual()`, considered a bugfix, see https://github.com/iojs/io.js/pull/636 (@vkurchatkin) - Introduce a `deepStrictEqual()` method to mirror `deepEqual()` but performs strict equality checks on primitives, see https://github.com/iojs/io.js/pull/639 (@vkurchatkin) * **tracing**: - Add LTTng (Linux Trace Toolkit Next Generation) when compiled with the `--with-lttng` option. Trace points match those available for DTrace and ETW. https://github.com/iojs/io.js/pull/702 (@thekemkid) * npm upgrade to 2.5.1 * **libuv** upgrade to 1.4.0 * Add new collaborators: - Aleksey Smolenchuk (@lxe) - Shigeki Ohtsu (@shigeki)
![Gitter](https://badges.gitter.im/Join Chat.svg)
This repository began as a GitHub fork of joyent/node.
io.js contributions, releases, and contributorship are under an open governance model. We intend to land, with increasing regularity, releases which are compatible with the npm ecosystem that has been built to date for Node.js.
The official name is io.js, which should never be capitalized, especially not at the start of a sentence, unless it is being displayed in a location that is customarily all-caps (such as the title of man pages).
Binaries, installers and source tarballs are available at https://iojs.org.
Releases are available at https://iojs.org/dist/, listed under their version string. The https://iojs.org/dist/latest/ symlink will point to the latest release directory.
Nightly builds are available at https://iojs.org/download/nightly/, listed under their version string which includes their date (in UTC time) and the commit SHA at the HEAD of the release.
API documentation is available in each release and nightly directory under docs. http://iojs.org/api/ points to the the latest version.
Release and nightly download directories all contain a SHASUM256.txt file that lists the SHA checksums for each file available for download. To check that a downloaded file matches the checksum, run it through sha256sum
with a command such as:
$ grep iojs-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
(Where “iojs-vx.y.z.tar.gz” is the name of the file you have downloaded)
Additionally, releases (not nightlies) have GPG signed copies of SHASUM256.txt files available as SHASUM256.txt.asc. You can use gpg
to verify that the file has not been tampered with.
To verify a SHASUM256.txt.asc, you will first need to import all of the GPG keys of individuals authorized to create releases. They are listed at the bottom of this README. Use a command such as this to import the keys:
$ gpg --keyserver pool.sks-keyservers.net \ --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
(Include each of the key fingerprints at the end of this command.)
You can then use gpg --verify SHASUMS256.txt.asc
to verify that the file has been signed by an authorized member of the io.js team.
Once verified, use the SHASUMS256.txt.asc file to get the checksum for the binary verification command above.
Prerequisites:
gcc
and g++
4.8 or newer, orclang
and clang++
3.3 or newer$ ./configure $ make $ [sudo] make install
If your Python binary is in a non-standard location or has a non-standard name, run the following instead:
$ export PYTHON=/path/to/python $ $PYTHON ./configure $ make $ [sudo] make install
To run the tests:
$ make test
To build the documentation:
$ make doc
To read the documentation:
$ man doc/iojs.1
Prerequisites:
PATH
.> vcbuild nosign
To run the tests:
> vcbuild test
Intl
(ECMA-402) support:Intl support is not enabled by default.
This option will build with “small” (English only) support, but the full Intl
(ECMA-402) APIs. With --download=all
it will download the ICU library as needed.
Unix / Macintosh:
$ ./configure --with-intl=small-icu --download=all
Windows:
> vcbuild small-icu download-all
The small-icu
mode builds with English-only data. You can add full data at runtime.
Note: more docs are on the joyent/node wiki.
With the --download=all
, this may download ICU if you don't have an ICU in deps/icu
.
Unix / Macintosh:
$ ./configure --with-intl=full-icu --download=all
Windows:
> vcbuild full-icu download-all
:-(
The Intl
object will not be available. This is the default at present, so this option is not normally needed.
Unix / Macintosh:
$ ./configure --with-intl=none
Windows:
> vcbuild intl-none
$ pkg-config --modversion icu-i18n && ./configure --with-intl=system-icu
You can find other ICU releases at the ICU homepage. Download the file named something like icu4c-**##.#**-src.tgz
(or .zip
).
Unix / Macintosh
# from an already-unpacked ICU: $ ./configure --with-intl=[small-icu,full-icu] --with-icu-source=/path/to/icu # from a local ICU tarball $ ./configure --with-intl=[small-icu,full-icu] --with-icu-source=/path/to/icu.tgz # from a tarball URL $ ./configure --with-intl=full-icu --with-icu-source=http://url/to/icu.tgz
Windows
First unpack latest ICU to deps/icu
icu4c-##.#-src.tgz (or .zip
) as deps/icu
(You'll have: deps/icu/source/...
)
> vcbuild full-icu
The io.js project team comprises a group of core collaborators and a sub-group that forms the Technical Committee (TC) which governs the project. For more information about the governance of the io.js project, see GOVERNANCE.md.
Collaborators follow the COLLABORATOR_GUIDE.md in maintaining the io.js project.