|
|
| Line 1: |
Line 1: |
| = Node.js 8.x =
| |
|
| |
|
| == Summary ==
| |
| Fedora 27 will be updated to Node.js 8.x, the latest LTS release of the platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications.
| |
|
| |
| == Owner ==
| |
|
| |
| * Name: [[User:zvetlik|Zuzana Svetlikova]]
| |
| * Email: [mailto:zsvetlik@redhat.com zsvetlik@redhat.com]
| |
| * Release notes owner: [[User:Immanetize|Pete Travis]] ([[User talk:Immanetize|talk]])
| |
| <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
| |
| * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
| |
| -->
| |
| <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
| |
| * Product:
| |
| * Responsible WG:
| |
| -->
| |
|
| |
| == Current status ==
| |
| * Targeted release: [[Releases/27 | Fedora 27 ]]
| |
| * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
| |
| <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
| |
| Bugzilla states meaning as usual:
| |
| NEW -> change proposal is submitted and announced
| |
| ASSIGNED -> accepted by FESCo with on going development
| |
| MODIFIED -> change is substantially done and testable
| |
| ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)
| |
| CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
| |
| -->
| |
| * Tracker bug: <will be assigned by the Wrangler>
| |
|
| |
| == Detailed Description ==
| |
|
| |
| Node.js has seen many changes between v6.x and v8.x.<!-- [There is a listing of changes documented on the wiki for [[https://github.com/nodejs/node/wiki/Breaking-changes-between-v4-and-v5 5.x] and [https://github.com/nodejs/node/wiki/Breaking-changes-between-v5-and-v6 6.x]--> Note that this release includes API updates that may require dependency updates.
| |
|
| |
| Upstream maintains an exhaustive list of interesting changes [https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md here].
| |
|
| |
| Node.js 8.x will be under active development until October 2017, at which time it will enter its long-term stable release, which will be maintained actively through April 2019 and for security issues until December 2019.
| |
|
| |
| == Benefit to Fedora ==
| |
|
| |
| Developers of Node.js applications who use Fedora and community members who package Node.js software for Fedora benefits from the new features and stability improvements in this release. Furthermore, it promotes Fedora's "First" Foundation, by being one of the first distributions to ship this new LTS release.
| |
|
| |
| == Scope ==
| |
| * Proposal owners:
| |
| ** Update nodejs
| |
| ** Rebuild all binary modules, apply patches as necessary
| |
|
| |
| * Other developers:
| |
| ** Other Node.js packagers' attention may be required if the update causes issues for their packages.
| |
|
| |
| * Release engineering: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here.
| |
| Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook -->
| |
|
| |
| * Policies and guidelines:
| |
| ** No expected changes
| |
|
| |
| * Trademark approval: N/A (not needed for this Change)
| |
| <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
| |
|
| |
| == Upgrade/compatibility impact ==
| |
| Node.js 8.x breaks compatibility in a limited number of cases, which may affect third-party software. (See the Detailed Description above.) Due to the fact that 8.x is will be a long-term stable release by upstream, we expect these to be of minimal impact and third-parties to adapt to support it.
| |
|
| |
| == How To Test ==
| |
| Run your favorite Node.js applications and make sure they still work.
| |
|
| |
| == User Experience ==
| |
| There are no changes for end users of applications that use Node.js. There are limited changes for programmers, as stated in the Detailed Description above.
| |
|
| |
| == Dependencies ==
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| N/A (not a System Wide Change)
| |
|
| |
| == Contingency Plan ==
| |
| <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
| |
| * Contingency mechanism: Bump epoch and revert to nodejs 6.x LTS (which will continue to be supported for security updates only through April 2019). Note: this contingency mechanism will be considered an absolute last resort, as downgrading to 6.x may require considerably more effort (including a mass-rebuild) than would be worthwhile.
| |
| <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. -->
| |
| * Contingency deadline: Beta Freeze
| |
| <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
| |
| * Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| * Blocks product? N/A <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
| |
|
| |
| == Documentation ==
| |
| * [http://blog.nodejs.org Upstream release announcements]
| |
| * [https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md Changelog for Node.js v8]
| |
| <!--* [https://github.com/nodejs/node/wiki/Breaking-changes-between-v4-and-v5 API changes in 5.x]
| |
| * [https://github.com/nodejs/node/wiki/Breaking-changes-between-v5-and-v6 API changes in 6.x] -->
| |
|
| |
| == Release Notes ==
| |
| <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
| |
| <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.
| |
|
| |
| Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
| |
| -->
| |
|
| |
| Fedora 27 features Node.js 8, the latest long-term stable version of the platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Developers may notice several API changes.
| |
|
| |
| [[Category:ChangeAcceptedF25]]
| |
| <!-- When your change proposal page is completed and ready for review and announcement -->
| |
| <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
| |
| <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
| |
| <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
| |
|
| |
| <!-- Select proper category, default is Self Contained Change -->
| |
| <!-- [[Category:SelfContainedChange]] -->
| |
| [[Category:SelfContainedChange]]
| |
|
| |
| [[Category:ChangePageIncomplete]]
| |
