1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: make the background section concise and improve its formality

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/18928
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
This commit is contained in:
Wilson 2018-02-21 22:49:23 -08:00 committed by Matheus Marchini
parent 4eb45b884d
commit a27e6d7321
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/guides/maintaining-V8.md
View File

@ -3,15 +3,14 @@
## Background ## Background
V8 follows the Chromium release schedule. The support horizon for Chromium is V8 follows the Chromium release schedule. The support horizon for Chromium is
very different from the support horizon that Node.js needs to provide to its different compared to the support horizon for Node.js. As a result, Node.js
users. As a result Node.js needs to support a version of V8 for quite a bit needs to support multiple versions of V8 longer than what upstream needs
longer than what upstream needs to support. Since V8 doesn't have an LTS to support. V8 branches in Node.js lack of an official maintenance process due
supported branch, there is no official process around how the V8 branches in to a missing LTS supported branch.
Node.js are maintained.
This document attempts to document the current processes and proposes a workflow This document attempts to outline the current maintenance processes, proposes
for maintaining the V8 branches in Node.js LTS and Current releases and how the a workflow for maintaining the V8 branches in both Node.js LTS and current
Node.js and V8 teams at Google can help. releases, and discusses how the Node.js and V8 teams at Google can help.
## V8 Release Schedule ## V8 Release Schedule