2014.12.22, Version 0.10.35 (Stable)
tls: re-add 1024-bit SSL certs removed by f9456a2 (Chris Dickinson)
timers: don't close interval timers when unrefd (Julien Gilli)
timers: don't mutate unref list while iterating it (Julien Gilli)
Source Code: http://nodejs.org/dist/v0.10.35/node-v0.10.35.tar.gz
Macintosh Installer (Universal): http://nodejs.org/dist/v0.10.35/node-v0.10.35.pkg
Windows Installer: http://nodejs.org/dist/v0.10.35/node-v0.10.35-x86.msi
Windows x64 Installer: http://nodejs.org/dist/v0.10.35/x64/node-v0.10.35-x64.msi
Windows x64 Files: http://nodejs.org/dist/v0.10.35/x64/
Linux 32-bit Binary: http://nodejs.org/dist/v0.10.35/node-v0.10.35-linux-x86.tar.gz
Linux 64-bit Binary: http://nodejs.org/dist/v0.10.35/node-v0.10.35-linux-x64.tar.gz
Solaris 32-bit Binary: http://nodejs.org/dist/v0.10.35/node-v0.10.35-sunos-x86.tar.gz
Solaris 64-bit Binary: http://nodejs.org/dist/v0.10.35/node-v0.10.35-sunos-x64.tar.gz
Other release files: http://nodejs.org/dist/v0.10.35/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 98f61cb09685ed45f2db6e0fc5ccbdd273204091 node-v0.10.35-darwin-x64.tar.gz 8616029e0bb79dea1a974f97e42399fe24d3f4d7 node-v0.10.35-darwin-x86.tar.gz 3a202a749492e48542d2c28220e43ef6dae084bc node-v0.10.35-linux-x64.tar.gz c71823a584aa4cc778d73ff4ea89ed2b6f0ac250 node-v0.10.35-linux-x86.tar.gz 56f2837da0cf1a302e7b3e6da770fba875a13a62 node-v0.10.35-sunos-x64.tar.gz d5713e3933a4ddfd9573a5326a2a5043fb50184f node-v0.10.35-sunos-x86.tar.gz fca0fcf21a0dcd4ae02b319804a99e3cfeb83ee3 node-v0.10.35-x86.msi 3781eae7bcbf55d87b528b3a0b3c9524f94e66a4 node-v0.10.35.pkg bcad4ebf56516676f93b28377f03d3b3ea52795c node-v0.10.35.tar.gz 16a363d39f08fa5119f3ca82dcd08a6d67110bcb node.exe 43197d7d92e9a6eead6060288173941041dac9a4 node.exp c0cc751dcc915234b15cfc210cdd459b78148435 node.lib 9ff7f9e7959c196a97cc53400d86602da7f5a74d node.pdb bfc708da1114ac539cd43738145d8cc1f5e39f6f openssl-cli.exe f54d55939d9493f934dc36baa169429df8fb47f4 openssl-cli.pdb c95e8041b5b16488eb2522fa072061690f6ef0cb x64/node-v0.10.35-x64.msi 7f31dd9c636e658f7386e8f8b2ef3be885158c55 x64/node.exe 6df8b6b95024e5f0bd7f39cd5a83341ae227e8aa x64/node.exp 82fa5ea193f4aac3267b58c8c5f581952ae46fea x64/node.lib e6e4df82798d36343f0f0e872a36d15172e86f70 x64/node.pdb ae6917172865a8fa3ddfdf3bc93a863043742fa9 x64/openssl-cli.exe b9bb9409cbf63c20b2c2e7db9f5f323cfd400771 x64/openssl-cli.pdb -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlSYki4ACgkQfTP/nQJGQG0BYQCeNpRS2Bj8IJPfRomoaXMJgr+f p/IAoOukOg36PqphzVe2C2kEUcIxb2H1 =fA07 -----END PGP SIGNATURE-----
2014.12.17, Version 0.10.34 (Stable)
uv: update to v0.10.30
zlib: upgrade to v1.2.8
child_process: check execFile args is an array (Sam Roberts)
child_process: check fork args is an array (Sam Roberts)
crypto: update root certificates (Ben Noordhuis)
domains: fix issues with abort on uncaught (Julien Gilli)
timers: Avoid linear scan in _unrefActive. (Julien Gilli)
timers: fix unref() memory leak (Trevor Norris)
v8: add api for aborting on uncaught exception (Julien Gilli)
debugger: fix when using "use strict" (Julien Gilli)
Source Code: http://nodejs.org/dist/v0.10.34/node-v0.10.34.tar.gz
Macintosh Installer (Universal): http://nodejs.org/dist/v0.10.34/node-v0.10.34.pkg
Windows Installer: http://nodejs.org/dist/v0.10.34/node-v0.10.34-x86.msi
Windows x64 Installer: http://nodejs.org/dist/v0.10.34/x64/node-v0.10.34-x64.msi
Windows x64 Files: http://nodejs.org/dist/v0.10.34/x64/
Linux 32-bit Binary: http://nodejs.org/dist/v0.10.34/node-v0.10.34-linux-x86.tar.gz
Linux 64-bit Binary: http://nodejs.org/dist/v0.10.34/node-v0.10.34-linux-x64.tar.gz
Solaris 32-bit Binary: http://nodejs.org/dist/v0.10.34/node-v0.10.34-sunos-x86.tar.gz
Solaris 64-bit Binary: http://nodejs.org/dist/v0.10.34/node-v0.10.34-sunos-x64.tar.gz
Other release files: http://nodejs.org/dist/v0.10.34/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 8df2fdb333dd8edee59ceaf72738e3773c7863e6 node-v0.10.34-darwin-x64.tar.gz 03168c2157baff928a397b85d8a7e6731b270f9a node-v0.10.34-darwin-x86.tar.gz f064a252827c8129126f0e8ab3c8bf46f92506ec node-v0.10.34-linux-x64.tar.gz fe0343f97c35aeb2c72bfd997dafde947ff44c23 node-v0.10.34-linux-x86.tar.gz 4b3ccf37886f8056800ed174688c8782f9857d52 node-v0.10.34-sunos-x64.tar.gz ea891434436ed91d806201eb329d3c98f7e3c6b6 node-v0.10.34-sunos-x86.tar.gz 7609d6dda6071e499a54656bbf85f16ed097c106 node-v0.10.34-x86.msi 56e2aec59ac526d3daf607c7f50c2faf3e857cff node-v0.10.34.pkg a342eb4d653ab48ba016c0c0c259565c822881cc node-v0.10.34.tar.gz c71dce9dd3f3fbff34506a4edc3e37c59e31d7bd node.exe ffc836802c3b2e25b38f4f73c0f044fef345e152 node.exp 3e24f9c69826f320d303795c3564994e4311879f node.lib 8ccb4fdaaaec797e0762cea38112af5456fe3f7e node.pdb fa0d0c098f475d6e1d6ad74c301a2361a9ac9888 openssl-cli.exe 72772212ff62ecbf76ca468f402184e3f364de51 openssl-cli.pdb c54153231d0003792c4431cea38b9cb733a142b5 x64/node-v0.10.34-x64.msi b84684c92ed41a883452eb65a3010223378eb1ca x64/node.exe c95e2dd11dc216c4b2d5a76852d2a0e7a8b247bc x64/node.exp 41db33520c33c576e4591771c371ae5f2644cadf x64/node.lib d2ebec3f34e1a7e7969bfbe3330140f253b3cf9c x64/node.pdb b678c997ad7747c4c35dc8c8362730fca5bad97c x64/openssl-cli.exe f38f6eaae3aa2b11f3835b67f2dce04f4fc0fab8 x64/openssl-cli.pdb -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlSR/MIACgkQfTP/nQJGQG3ViACcC47u19WHh+vC4rfwJOoaRBFq 4fUAnAm48HaJGYQ3sUlJlEq68LCwJfgL =yduE -----END PGP SIGNATURE-----
We assembled the Node.js Advisory Board (AB) to listen to the community and make the necessary changes to have a unified direction for Node.js, a passionate group of developers, a vibrant ecosystem of product and service providers, and a satisfied user base. Over the last month we have made great progress on an open governance model, API standards, IP management, and transparency to ensure the project is community-driven. These efforts explicitly target helping resolve conflicts and with the goal of moving the community forward together. It is important that we understand voices of dissent and frustration and work together to build the greater ecosystem. We are committed to this goal.
Node.js remains the trusted platform that users rely on for creative projects and to drive business goals. The v0.12 release will ship shortly and the project team is already engaged in discussions about the next release.
A lot has been happening in Node.js, so I wanted bring everyone up to date on where we are with regards to the advisory board, its working groups, and the release of v0.12.
The interim advisory board has met three times since its creation. You can find the minutes from the advisory board meetings here: http://nodejs.org/advisory-board. As we have more meetings and minutes, we will announce the dates and times for those meeting and their minutes here on the blog. The next meeting is this Thursday December 4th, at 1:30PM PST. We're looking to collect as much feedback and input from as many representatives of the community as we can, so it's important that we keep everyone up to date as much as possible.
The interim advisory board has been working through a series of topics (in general meetings as well as working groups) to further hone the scope of the board, as well as define the structure that the advisory board will use to conduct its meetings. Everyone on the board wants to make sure we're being as transparent as possible, so let me describe how things operate so far. The board is using a traditional two conference call structure, a public portion that is recorded and open for anyone to join, and a private portion that is only for board members.
The public portion is meant to provide an update of what happened in the previous meeting, as well as the status of action items from the previous meeting. At the end of each public session is a open comment section, where listeners are able to ask questions and the advisory board can respond.
Following the public portion the board dials into the private conference, further discussion happens during this time around specific agenda items, working groups providing updates, and facilitating conversations about those topics. These conversations are open and frank, and their content is recorded in the minutes. Those minutes are then published a few days after the meeting in the GitHub repository https://github.com/joyent/nodejs-advisory-board, as well as on the website https://nodejs.org/advisory-board.
There are a few working groups so far, for instance one is focused on making sure the membership of the board is representative of the community Node.js serves. While the board was initially bootstrapped with its existing membership, we want to quickly move to a model that fully represents our community. We want the board to represent the broadest spectrum of our community, that also enables the board to move swiftly and make progress.
Another working group is having a conversation about governance. This includes topics like what is the team that makes decisions for Node.js, how do you become a member of that team, how does that team set the roadmap for the project, and how does that team makes decisions.
One thing that we all agree on, is that we're not going to be using the Benevolent Dictator model. In fact, recently the project hasn't been operating that way. We can be more clear about that in our documentation. We all agree we want a healthy and vibrant team, a team focused on making progress for Node.js, not for progress's sake, but for the betterment of the software project and the community we serve. We also agree that this means that there should be consensus among the team. The conversation has been fruitful, and is on going, we're continuing to work through the finer points of how much consensus we need.
I want to take a moment to describe what consensus means in this context. The consensus model is about accountability. Accountability for the changes being integrated into the project, accountability for documentation, and accountability for releases. While members of the team are responsible for subsystems or features of Node.js, everyone reviews each others changes. They make sure to understand the impact on their relevant responsibilities.
The goal of the team, especially that of the project lead, is to drive consensus and ensure accountability. This means asking critical questions and being able to answer them specifically and succinctly, for example:
- What are we trying to solve with this change?
- Does this change effectively solve for this problem?
- Does this API have a consumer?
- Does this API reach the broadest amount of use cases?
- Is this API supportable?
- Does this change have adverse effects on other subsystems or use cases (and is that acceptable)?
- Does this change have tests that verify its operation, now and in the future?
- Does this change pass our style guidelines?
- Does this change pass our integration tests for the matrix of our supported configurations?
- For instance: ia32 and x64 for Windows, Linux, OSX, SmartOS
These are just some of the questions, and while the questions are not unusual or unique to Node.js, they are still important.
Finally, we are very close to releasing v0.12, there's only one major patch we're waiting to land. Once that's done we'll be releasing v0.11.15 as a release candidate. Assuming no severe issues are filed against v0.11.15 we will be going live with v0.12 about two weeks after the v0.11.15 release.
If you have questions for the advisory board you can email email@example.com or file an issue on its repository https://github.com/joyent/nodejs-advisory-board. Thanks for all of your continued contributions to Node.js, in the form of filing issues, submitting pull requests, and publishing your modules. Node.js is lucky to have such an enthusiastic and engaged community, and we're excited to be working with you on the future of Node.js.