Create weekly-update.2015-04-17.md

[Gioyik]

CC #55

[c0b41]

@Gioyik When will the merge?

[Gioyik]

@ayhankuru Let's wait for more people review it, then someone with the rights will merge it. :)

[rosskukulinski]

Overall looks good -- thanks for pulling this together @Gioyik. I'm wondering how we should reference the pending 1.8 release (ongoing here including draft release notes). We are including the 1.8 perf improvements, but if its not out yet, then I think we should bundle that comment with the actual 1.8 release notes.

I'm thinking that we shouldn't wait for 1.8 to land for us to release this weekly update. In that case, lets hold onto the 1.8 crypto performance comment until next week.

Thoughts?

[Gioyik]

I think is OK in the way we present it. It's on Comunity Updates section and not presented as something released. But we can keep it for a week update when we mention 1.8 features. I don't have problem with it.

[diagramatics]

I wonder, should we use H3 for Notable Changes and Known Issues or H4? I found the rendered Markdown, when pasted to Medium automatically formats it right like the rest of the published articles with H4.

And speaking of Known Issues, none for this week?

[Gioyik]

And speaking of Known Issues, none for this week?

Not this time: https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#2015-04-14-version-171-rvagg

[diagramatics]

Hm, weird. 1.8.0 has the same issues as 1.6.4. Is it intentional?

[Gioyik]

@diagramatics not sure about it, but seems something to be discussed for next weekly update due this week is about 1.7.x

[yosuke-furukawa]

I guess Known Issues is just forgotten ...
We have to include the Known issues in this article. I will fix the change log and throw a pull request to io.js.

If we remove them, everyone misleads the known issues are resolved.

[Gioyik]

@yosuke-furukawa which know issues we should add? Same as in previous weekly update?

[yosuke-furukawa]

@Gioyik
Here. nodejs/node#1473
The known issues are seems to be good. But does not merge yet.
io.js core collaborators is discussing on how to handle the Known issues.

@Gioyik go ahead to write down the Known issues and publish the medium ??? this is Wednesday!!!

[Gioyik]

@yosuke-furukawa know issues are added. Let me know if there's something to add.

[yosuke-furukawa]

LGTM.

[Gioyik]

I have not permissions to merge PR (I am not added to org) and publish on Medium. So from now it's a task of someone else :)

[yosuke-furukawa]

I don't have a permission to publish on Medium neither. @julianduque @mikeal please publish our weekly updates on medium :)

[Gioyik]

Show us your super powers \o/

[julianduque]

Published: https://medium.com/node-js-javascript/io-js-week-of-april-17th-e4c6f2db7659

Sorry for the late publication

[diagramatics]

@julianduque No subtitles for this week on Medium?

(I feel bad for nitpicking all over the place)

[julianduque]

@diagramatics you are the official nit picker ;) and done, added subtitles

[diagramatics]

Great, thanks! :)