Evangelism: Weekly Update March 13th

[julianduque]

io.js 1.5.1 Release

On Monday, March 9th, @rvagg released io.js v1.5.1. The complete change log can be found on GitHub.

Notable changes

• tls: The reported TLS memory leak has been resolved via various commits in this release. Current testing indicated that there may still be some leak problems. Track complete progress at #1075.
• http: Fixed an error reported at joyent/node#9348 and npm/npm#7349. Pending data was not being fully read upon an 'error' event leading to an assertion failure on socket.destroy(). (Fedor Indutny) #1103

Known issues

• Possible remaining TLS-related memory leak(s), details at #1075.
• Windows still reports some minor test failures and we are continuing to address all of these as a priority. See #1005.
• Surrogate pair in REPL can freeze terminal #690
• Not possible to build io.js as a static library #686
• process.send() is not synchronous as the docs suggest, a regression introduced in 1.0.2, see #760 and fix in #774
• Calling dns.setServers() while a DNS query is in progress can cause the process to crash on a failed assertion #894

Community Updates

• Tony Pujals gave the io.js roadmap presentation to BayNode. The video was posted to vimeo on March 9. Slides are available for anyone to give at their local meetup.
• Johan Bergström is working on getting a patch into V8 on behalf of io.js to bring Solaris support back into the latest version
• NodeUp Episode 84 it's io.js update Inside io.js podcast season 1 #1 with Mikeal Rogers, Trevor Norris and Bradley Meck
• Mikeal Rogers was interviewed for Descriptive podcast on an episoded called We've Never Had This Many Active Contributors to Core Before
• Mark Wolfe gave a talk about io.js at @melbjs meetup, slides are published here
• dockeri.co now runs on io.js, you can see the announcement here
• Node.js Advisory Board are talking about the io.js/Node.js reconcilitation proposal, you can check the meeting minutes here

Upcoming Events

• NodeConf tickets are on sale, June 8th and 9th at Oakland, CA and NodeConf Adventure for June 11th - 14th at Walker Creek Ranch, CA
• CascadiaJS tickets are on sale, July 8th - 10th at Washington State
• NodeConf EU tickets are on sale, September 6th - 9th at Waterford, Ireland

[julianduque]

@jbergstroem is likely getting a patch into V8 on behalf of io.js to bring Solaris support back into the latest version

[subfuzion]

1.5.1 release 2015-03-9

[subfuzion]

(DRAFT)

io.js 1.5.1 Release

On Monday, March 9th, @rvagg released io.js v1.5.0. The complete change log can be found on GitHub.

Notable changes

• tls: The reported TLS memory leak has been at least partially resolved via various commits in this release. Current testing indicated that there may still be some leak problems. Track complete progress at #1075.
• http: Fixed an error reported at joyent/node#9348 and npm/npm#7349. Pending data was not being fully read upon an 'error' event leading to an assertion failure on socket.destroy(). (Fedor Indutny) #1103

Known issues

• Possible remaining TLS-related memory leak(s), details at #1075.
• Windows still reports some minor test failures and we are continuing to address all of these as a priority. See #1005.
• Surrogate pair in REPL can freeze terminal #690
• Not possible to build io.js as a static library #686
• process.send() is not synchronous as the docs suggest, a regression introduced in 1.0.2, see #760 and fix in #774
• Calling dns.setServers() while a DNS query is in progress can cause the process to crash on a failed assertion #894

Community Updates

• Tony Pujals gave Mikeal's io.js presentation to BayNode. The video was posted to vimeo on March 9.

[rvagg]

FYI, after releasing, updates in nodejs/node#1075 indicate that the leak may actually be fixed, keep an eye on that issue but you may be able to announce that it's fixed even though the release notes hedge the language around it.

[yosuke-furukawa]

NodeUp#84 talks about io.js Update by @mikeal, @bradleymeck and @trevnorris! https://twitter.com/NodeUp/status/573256463440855040

[mikeal]

I got interviewed for this podcast http://descriptive.audio/episodes/12

[mikeal]

I think we should start to list upcoming destination conferences that have tickets on sale. Both NodeConf and NodeConf.eu have tickets on sale right now :)

[rosskukulinski]

It think also CascadiaJS?

[rosskukulinski]

@yosuke-furukawa we listed that nodesource blog last week.

[julianduque]

@mikeal also JSConf Uruguay and EmpireJS on April

[yosuke-furukawa]

@rosskukulinski ooops. thanks. i removed my comment.

[julianduque]

weekly update draft is on the first comment based on @tonypujals one, please review and comment :)

[yosuke-furukawa]

node advisory board members are talking about io.js and node.js reconciliation. https://github.com/joyent/nodejs-advisory-board/blob/master/meetings/2015-03-09/minutes.md#nodejsiojs-reconciliation-bb

[mikeal]

"http://dockeri.co now uses @official_iojs! Many wows! Much excite!"

https://twitter.com/wjblankenship/status/575867637680369665

[mikeal]

"Posted the slides for my @official_iojs talk last night at @melbjs https://speakerdeck.com/wolfeidau/iojs-bringing-es6-to-the-node"

https://twitter.com/wolfeidau/status/575785856545378304

[julianduque]

I've sent the PR - please review/publish #44 :)

[subfuzion]

Add to community updates (including @mikeal 's suggestions:

• io.js TC Meeting 2015-03-11 is available here
• NodeConf and NodeConf EU tickets are on sale now

[Fishrock123]

Looks like it's up at https://medium.com/@iojs/io-js-week-of-march-13th-e3024cc66802

But some of the headers seem at the wrong levels?

[alexpods]

io.js TC Meeting 2015-03-11 is available here

Meeting was skipped nodejs/node#1124 . Why it's published?

[julianduque]

@alexpods you are right, updating article

[subfuzion]

Adding the bullet was my fault; sorry about that @julianduque

[julianduque]

@tonypujals @alexpods fixed :)

[alexpods]

@julianduque 👍

[jbergstroem]

The v8 patch referenced in "community updates" landed upstream and we merged yesterday. We now have two buildbots provided by Joyent running tests. The next step is fixing the failing tests (a handful)!

[julianduque]

@jbergstroem thats good news, will add it to the next weekly update