You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
***This is a living document, it describes the policy and priorities as they exist today but can evolve over time.***
4
+
5
+
## Stability Policy
6
+
7
+
The most important consideration in every code change is the impact it will have, positive or negative, on the ecosystem (modules and applications).
8
+
9
+
io.js does not remove stdlib JS API.
10
+
11
+
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).
12
+
13
+
io.js will continue to adopt new V8 releases.
14
+
* When V8 ships a breaking change to their C++ API that can be handled by [`nan`](https://github.com/rvagg/nan)
15
+
the *minor* version of io.js will be increased.
16
+
* When V8 ships a breaking change to their C++ API that can NOT be handled by [`nan`](https://github.com/rvagg/nan)
17
+
the *major* version of io.js will be increased.
18
+
* When new features in the JavaScript language are introduced by V8 the
19
+
*minor* version number will be increased. TC39 has stated clearly that no
20
+
backwards incompatible changes will be made to the language so it is
21
+
appropriate to increase the minor rather than major.
22
+
23
+
No new API will be added in *patch* releases.
24
+
25
+
Any API addition will cause an increase in the *minor* version.
26
+
27
+
### Long Term Support
28
+
29
+
io.js supports old versions for as long as community members are fixing bugs in them.
30
+
31
+
As long as there is a community back porting bug fixes we will push patch releases for those versions of io.js.
32
+
33
+
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.
34
+
35
+
## Channels
36
+
37
+
Channels are points of collaboration with the broader community and are not strictly scoped to a repository or branch.
38
+
39
+
* Release - Stable production ready builds. Unique version numbers following semver.
40
+
* Canary - Nightly builds w/ V8 version in Chrome Canary + changes landing to io.js. No version designation.
41
+
* NG - "Next Generation." No version designation.
42
+
43
+
## NG (Next Generation)
44
+
45
+
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.
46
+
47
+
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.
48
+
49
+
# Immediate Priorities
50
+
51
+
## Debugging and Tracing
52
+
53
+
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.
54
+
55
+
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).
56
+
57
+
The [Tracing WG](https://github.com/iojs/tracing-wg) is driving this effort:
58
+
59
+
* AsyncWrap improvements - basically just iterations based on feedback from people using it.
60
+
* async-listener - userland module that will dogfood AsyncWrap as well as provide many often requested debugging features.
61
+
* Tracing
62
+
* Add tracing support for more platforms (LTTng, etc).
63
+
*[Unify the Tracing endpoint](https://github.com/iojs/io.js/issues/729).
64
+
* New Chrome Debugger - Google is working on a version of Chrome's debugger that is without Chrome and can be used with io.js.
65
+
66
+
## Ecosystem Automation
67
+
68
+
In order to maintain a good release cadence without harming compatibility we must do a better job of understanding exactly what impact a particular change or release will have on the ecosystem. This requires new automation.
69
+
70
+
The initial goals for this automation are relatively simple but will create a baseline toolchain we can continue to improve upon.
71
+
72
+
* Produce a list of modules that no longer build between two release versions.
73
+
* Produce a list of modules that use a particular core API.
74
+
* Produce detailed code coverage data for the tests in core.
75
+
76
+
## Improve Installation and Upgrades
77
+
78
+
* Host and maintain registry endpoints (Homebrew, apt, etc).
79
+
* Document installation and upgrade procedures with an emphasis on using nvm or nave for development and our registry endpoints for traditional package managers and production.
80
+
81
+
## Streams
82
+
83
+
* Fix all existing compatibility issues.
84
+
* Simplify stream creation to avoid user error.
85
+
* Explore and identify compatibility issues with [WHATWG Streams](https://github.com/whatwg/streams).
86
+
* Improve stream performance.
87
+
88
+
## Internationalization / Localization
89
+
90
+
* Build documentation tooling with localization support built in.
0 commit comments