Skip to content
This repository has been archived by the owner on May 18, 2021. It is now read-only.

Commit

Permalink
Merge pull request #52 from Ferrari/february-27th
Browse files Browse the repository at this point in the history 
翻譯 week-of-february-27th
  • Loading branch information
@appleboy
appleboy committed Mar 1, 2015
2 parents 89252df + 65041ac commit ac07c11
Showing 1 changed file with 22 additions and 21 deletions.
43 changes: 22 additions & 21 deletions source/_drafts/io-js-week-of-february-27th.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,9 @@ categories: iojs 週報
---

_Note: version **1.4.0** was tagged and built but not released. A libuv bug was discovered in the process so the release was aborted. We have jumped to 1.4.1 to avoid confusion._
_注意：版本 **1.4.0** 已經編譯完成並標籤但是尚未釋出。在過程中一個 libuv 的臭蟲被發現所以這次的釋出將被棄置，我們將會升版號到 1.4.1 以避免造成混淆。_

## Notable changes
## 主要更動

* **process** / **promises**: An`'unhandledRejection'` event is now emitted on `process` whenever a `Promise` is rejected and no error handler is attached to the `Promise` within a turn of the event loop. A `'rejectionHandled'` event is now emitted whenever a `Promise` was rejected and an error handler was attached to it later than after an event loop turn. [#758](https://github.com/iojs/io.js/pull/758) (Petka Antonov)
* **streams**: you can now use regular streams as an underlying socket for `tls.connect()` [#926](https://github.com/iojs/io.js/pull/926) (Fedor Indutny)
Expand All @@ -17,7 +18,7 @@ _Note: version **1.4.0** was tagged and built but not released. A libuv bug was
* [#7171](https://github.com/npm/npm/issues/7171) Warn that `engineStrict` in `package.json` will be going away in the next major version of npm (coming soon!)
* **libuv**: Upgrade to 1.4.2. See [libuv ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog) for details of fixes.

# ARM offers support for io.js on ARMv8
# ARM 提供 io.js 在 ARMv8 上的支援

ARM contacted Rod Vagg, lead of the io.js Build Working Group, to offer their support to the io.js project. ARM and their hardware partners are on track to make ARMv8 a viable server platform and the nimble nature of server-side JavaScript make it a perfect fit to run on the new ARM.

Expand All @@ -27,22 +28,22 @@ From the beginning of the io.js project, Rod has championed the role of ARM for

The build team is in the process of being given access to the Linaro ARMv8 Server Cluster for integration with the io.js CI platform, which should eventually lead to regular ARMv8 binary releases.

# Community Updates

* [**Reconciliation Proposal**](https://github.com/iojs/io.js/issues/978): The io.js project is preparing a plan for reconciliation that can be brought to The Node.js Foundation. Input from the community is very important at this early stage so please leave a comment.
* **New internal C++ Streams API**: A [fresh C++ Streams API](https://github.com/iojs/io.js/commit/b9686233fc0be679d7ba1262b611711629ee334e) landed in io.js this week, allowing you to wrap a TLS stream into another TLS stream.
* **io.js Roadmap**: [The Roadmap](https://github.com/iojs/io.js/blob/v1.x/ROADMAP.md) is the plan for the future of io.js. It presents the plans for the stability policy, and lists what the immediate priorities for io.js as a whole are.
* **Roadmap Slides Finished and Ready for Translation**: The set of introductory slides for the Roadmap of io.js [have been finished, and are ready for translation](https://github.com/iojs/roadmap/issues/18). Do you think you could present them to a group near you? Comment and we'll work with you to prepare you to present!
* **Microsoft io.js How-To for Azure Websites**: Microsoft [published a how-to](http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/) tutorial for their Azure platform that describes how to use io.js with Azure Websites.
* **Floobits moves to io.js**: The code pairing software Floobits [converted their platform to io.js](https://news.floobits.com/2015/02/23/on-moving-to-io.js/), in part because of frustration with Node's slower release cycle, because the inclusion of more ES6 features without the need for the `--harmony` flag, and because they felt changes from 0.10.0 to 0.12.0 weren't very big.
* **Anand Mani Sankar's _Node.js vs io.js: Why the fork?!?_**: Anand wrote a good, for the most part objective, [post about the recent history of io.js](http://anandmanisankar.com/posts/nodejs-iojs-why-the-fork/#.VO82hE60PVw.twitter), and what we hope to achieve with it. A good read for people who aren't engaged in the community to catch up with.
* **iojs-jp - New io.js Japanese Blog**: The iojs-jp community has created a [localized io.js related blog](http://blog.iojs.jp/) to disseminate content in their language. If you're interested, take a look!
* **iojs-cn - New io.js Chinese Blog**: Similarly to the iojs-jp community, the iojs-cn community created a [localized blog](http://cn.iojs.org/) to publish posts about io.js to in their language. Make sure to visit if you're curious about iojs-cn or Chinese news about io.js!
* **[Roadmap Slides Review](https://www.youtube.com/watch?v=etI_UD4wXlo)** - A review of the roadmap slides before they were released to ensure they met with the message the project upholds.

# io.js Support Added
* **[Wallby.js](http://wallabyjs.com/)**, a while-you-write testing library for JavaScript, hit version 1.0 and [added support for io.js](http://dm.gl/2015/02/23/wallaby-version-one/)!
* **[jsdom](https://github.com/tmpvar/jsdom)**, an implementation of the WHATWG DOM and HTML standards, just hit [version 4.0.0](https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400), which added a _requirement_ of io.js.
* **[give](https://github.com/mmalecki/give)**'s creator [tweeted](https://twitter.com/maciejmalecki/status/569629100215816192) that newer versions of give support io.js. Give is a git-based node.js/io.js version manager.
* The **Firebase Realtime Client**, the official web/node.js JavaScript client for Firebase, [tweeted](https://twitter.com/FirebaseRelease/status/570000737343647744) that they added support for io.js in [version 2.2.1](https://www.firebase.com/docs/web/changelog.html#section-realtime-client)
* **Semaphore**, a hosted continuous integrations service, [tweeted](https://twitter.com/semaphoreapp/status/570987355005431809) about added io.js support in their [Platform update on February 24th, 2015](https://semaphoreapp.com/blog/2015/02/17/platform-update-on-february-24th.html?utm_source=twitter&utm_medium=social&utm_content=platform_update_launch&utm_campaign=platformupdate).
# 社群更新

* [**和解提案**](https://github.com/iojs/io.js/issues/978)：io.js 著手開始進行對於 Node.js 基金會的和解草案。目前還是初期草案階段，因此來自社群的意見是非常重要的，請大家踴躍反饋。
* **New internal C++ Streams API**：一個全新的 [C++ Streams API] 在這週增加到 io.js 之中，允許你可以將 TLS stream 包裝成另一個 TLS stream。
* **io.js 路徑圖**：[路徑圖](https://github.com/iojs/io.js/blob/v1.x/ROADMAP.md) 是對 io.js 未來的規劃。它描述關於穩定性策略的規劃以及列出 io.js 的當務之急。
* **路徑圖的投影片已經完成等待翻譯**：一系列之於 io.js 路徑圖的投影片已經[完成可以進行翻譯](https://github.com/iojs/roadmap/issues/18)。你覺得你可以向周遭的群體做簡報嗎？留下你的意見，我們會與你協作幫你預備好簡報！
* **Microsoft io.js How-To for Azure Websites**: 微軟 發佈一篇關於他們 Azure 平台的[入門教程](http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/)，描述如何在 Azure 上使用 io.js。
* **Floobits moves to io.js**: 配對編程軟體 Floobits [將他們的平台轉移到 io.js](https://news.floobits.com/2015/02/23/on-moving-to-io.js/)，因為對於 Node 過於緩慢的釋出感到挫折，對於可以開始使用 ES6 的新功能而又不需要增加 `--harmony` 的參數，他們也覺得從 0.10.0 到 0.12.0 的改動並不是非常明顯。
* **Anand Mani Sankar's _Node.js vs io.js: Why the fork?!?_**: Anand 寫了一篇很不錯也相當客觀的 [io.js 近期歷史的文章](http://anandmanisankar.com/posts/nodejs-iojs-why-the-fork/#.VO82hE60PVw.twitter)，也提及我們希望藉由 io.js 實現什麼。可以幫助哪些沒有參與到社群之中的人可以瞭解目前的狀況。
* **iojs-jp - New io.js Japanese Blog**: iojs-jp 社群建立了[本地化的部落格](http://blog.iojs.jp/)，用當地的語言來傳遞 io.js 的消息。如果你感興趣，快去看看吧！
* **iojs-cn - New io.js Chinese Blog**: 類似於 iojs-jp 社群，iojs-cn 社群也成立了[本地化的部落格](http://cn.iojs.org/)，用中文來發佈關於 io.js 的文章。如果你對於 iojs-cn 或 iojs 中文新聞感到興趣的話，請不要錯過！
* **[檢閱路徑圖投影片](https://www.youtube.com/watch?v=etI_UD4wXlo)** - 在釋出前對 io.js 路徑圖簡報的檢閱，確保它有符合專案的目標。

# 對 io.js 的支援增加
* **[Wallby.js](http://wallabyjs.com/)**，一個 JavaScript 的即時測試函式庫，釋出了 1.0 版本並[增加對 io.js 的支援](http://dm.gl/2015/02/23/wallaby-version-one/)！
* **[jsdom](https://github.com/tmpvar/jsdom)**，針對 WHATWG DOM 和 HTML 標準的實作，剛釋出了 [4.0.0 版本](https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400) 並且加入了 io.js 的依賴需求。
* **[give](https://github.com/mmalecki/give)** 的作者[發了一則推文](https://twitter.com/maciejmalecki/status/569629100215816192) 宣布新版的 give 將會增加對 io.js 的支援。Give 是基於 git 的 node.js/io.js 版本控制器。
* **Firebase Realtime Client**，Firebase 官方的 web/node.js 客戶端，[宣布](https://twitter.com/FirebaseRelease/status/570000737343647744) 他們將於 [2.2.1](https://www.firebase.com/docs/web/changelog.html#section-realtime-client) 開始支援 io.js。
* **Semaphore**，提供持續整合服務商，在 [2015/2/24 平台更新](https://semaphoreapp.com/blog/2015/02/17/platform-update-on-february-24th.html?utm_source=twitter&utm_medium=social&utm_content=platform_update_launch&utm_campaign=platformupdate)中[宣布](https://twitter.com/semaphoreapp/status/570987355005431809)將會支援 io.js。

0 comments on commit ac07c11

Please sign in to comment.