-
Notifications
You must be signed in to change notification settings - Fork 44
Evangelism: Weekly Update Mar 6th #16
Comments
Walmart are sponsoring a build machine for our CI set, we're just in the process of trying it out how well it's going to work but this could lead to "sunos" binaries from io.js like you can get from nodejs.org. So far we have the following companies contributing hardware (and related means to make this work)
Someone in here should get @geek to update the status of SmartOS before this Weekly Update goes out because it'll have evolved by then. |
proxyquire v1.3.2 published with support for iojs. Announcement here |
We have a jenkins worker running on SmartOS at the moment, but we are running into issues getting v8 to compile: https://code.google.com/p/v8/issues/detail?id=3935 |
The Node Version Delimma - http://hueniverse.com/2015/03/02/the-node-version-dilemma/ |
jsperf.com backend going io.js https://twitter.com/jsperf/status/572716156357873665 |
io.js and latest node.js are NOT affected by the FREAK Attack openSSL vulnerability. https://strongloop.com/strongblog/are-node-and-io-js-affected-by-the-freak-attack-openssl-vulnerability/ |
scrypt do now support io.js, details in barrysteyn/node-scrypt#39 |
Major version bump issue - iojs/io.js - nodejs/node#1061 |
iojs.org adds localization links to footer for access to available localized versions. #31 |
NodeSource io.js linux distributions: https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories |
Tessel2 is io.js compatible. https://twitter.com/rwaldron/status/573525951688085504 https://twitter.com/technicalhumans/status/573503873727356929 |
More on the Tessel 2. It runs io.js on the hardware http://blog.technical.io/post/112787427217/tessel-2-new-hardware-for-the-tessel-ecosystem |
Just wanted to ask if someone could take over writing this tomorrow, as I'm having a pretty painful dental issue, and will be trying to get into the dentist to get it fixed. Would anybody be able to take it over? |
I can step in. I'll ping you in the am for details unless there's a readme Ross On Thursday, March 5, 2015, &! (bitandbang) [email protected]
|
FYI We're up to 20 active languages now published (and linked) on io.js org. |
dangit @mikeal beat me to it XD |
Also, io.js 1.5.0 should be landing today: nodejs/node#1060 |
Additionally, we have a fix for the issue here: nodejs/node#1079 |
@rosskukulinski we can start drafting the language for the weekly update now :) |
@mikeal aye, I'll start writing it up |
Still working, but here's what I've got so far. Comments welcome. io.js 1.5.0 ReleaseThis week version 1.5.0 was released. Notable changesFor reference, the complete change log is here
Community Updates
io.js Support Added
|
I would appreciate it if someone from @iojs/core could help flush out the 1.5.0 release description & notable changes. |
@rosskukulinski I'm in the process of doing the Notable changes right now, watch the 1.5.0 issue for that. Breaking news that will impact this update is that Joyent are stepping up to provide some SmartOS machines but we're still in the early stages of that -- the Walmart SmartOS server will probably not end up being required and we'll switch out to Joyent resources. Obviously this is bigger news than just having new build servers so perhaps the best way to handle this for now is to run with what you have and the next update can provide new information about the situation when we actually have our hands on something. |
:) Awesome, thanks |
ok, updated again. I think it's all flushed out. Anything/everything fair game for comments/suggestions/rewrites. |
|
thanks @julianduque - updated! |
Is it ready? I can throw it up on Medium. |
the npm sub-points have come out cray cray |
too much bracket |
same |
cut the sub points. let's not do subpoints, they don't wokr on medium. |
ok, I'll ditch the npm subpoints, fixing the extra brackets |
fixed the bracketing issue son the medium post |
Trying a little (safe) experiment: https://iojs.org/en/index.html is featuring a link to the weekly update (english homepage.) This might help keep occasional users more in the loop until we expand the site's content offerings more. Thoughts? |
If you read this from the perspective of a new user/visitor there could be confusion about what "update" means, particularly given there is a "v1.5.0" next to it. Sounds like maybe io.js has weekly updates to download. |
better I guess |
-1 on the word "official." Strike it from our vocabulary :) |
@mikeal My bad, I keep forgetting.
That better? |
+1 |
Updated, thanks for the feedback |
Perhaps someone here should start a new issue for this at the begining of each week, or just after the last update goes out, so you can start collecting tidbits from around the interwebs. For the next one, while I have it top of mind, @jbergstroem is likely getting a patch into V8 on behalf of io.js to bring Solaris support back into the latest version. It's nice to highlight these points of collaboration because they go to the value of the ongoing relationship between io.js and V8. |
This was published, thank you all for this great work, this week will be on #41 |
io.js 1.5.0 Release
On Friday, March 6th, @rvagg released io.js v1.5.0. The complete change log can be found on GitHub.
Notable changes
Buffer#indexOf()
method, modelled offArray#indexOf()
. Accepts a String, Buffer or a Number. Strings are interpreted as UTF8. (Trevor Norris) #561options
object properties in'fs'
methods no longer perform ahasOwnProperty()
check, thereby allowing options objects to have prototype properties that apply. (Jonathan Ong) #635145af65
#4887 Replace calls to the
node-gyp
script bundled with npm by passing the--node-gyp=/path/to/node-gyp
option to npm. Swap inpangyp
or a versionof
node-gyp
modified to work better with io.js without having to touchnpm's code! (@ackalker)
2f6a1df
#1999 Only run
stop
andstart
scripts (plus their pre- and post- scripts) when there's no
restart
scriptdefined. This makes it easier to support graceful restarts of services
managed by npm. (@watilde /
@scien)
448efd0
#2853 Add support for
--dev
and--prod
tonpm ls
, so that you can list only the trees of production ordevelopment dependencies, as desired.
(@watilde)
a0a8777
#7463 Split the list printed by
npm run-script
into lifecycle scripts and scripts directly invoked vianpm run-script
. (@watilde)a5edc17
#6749
[email protected]
:Support for passing scopes to
npm init
so packages are initialized as partof that scope / organization / team. (@watilde)
Known issues
process.send()
is not synchronous as the docs suggest, a regression introduced in 1.0.2, see #760 and fix in #774Community Updates
io.js Support Added
The text was updated successfully, but these errors were encountered: