Skip to content

Commit 24d18ef

Browse files
joyeecheungaduh95
joyeecheung
authored and
aduh95
committed
doc: clarify that V8 major upgrade uses stable release
Along with Chrome, V8 has several different release channels. A V8 release only reaches stable after the stable cut has been rolled out and tested in several Chrome release channels, where regressions and bugs are discovered and fixed. This patch clarifies that we follow the _stable release_ of main branch to reduce the amount of churn needed. The V8 stable releases are already battle tested in Chrome and generally contain fewer regressions/bugs that would require another refresh to address. Signed-off-by: Joyee Cheung <[email protected]> PR-URL: #67106 Reviewed-By: Chengzhong Wu <[email protected]> Reviewed-By: Gürgün Dayıoğlu <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Tierney Cyren <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ulises Gascón <[email protected]>
1 parent 7a24b2b commit 24d18ef

1 file changed

Lines changed: 9 additions & 2 deletions

File tree

‎doc/contributing/maintaining/maintaining-V8.md‎

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -327,8 +327,15 @@ Revision_ from the 5.4 branch that can be useful in the update process above.
327327

328328
### Major updates
329329

330-
We upgrade the version of V8 in Node.js `main` whenever a V8 release goes stable
331-
upstream, that is, whenever a new release of Chrome comes out.
330+
Along with Chrome, V8 has several
331+
[different release channels](https://chromium.googlesource.com/chromium/src/+/lkgr/docs/process/release_cycle.md).
332+
A V8 release only reaches stable after the stable cut has been rolled out and tested
333+
in several Chrome release channels, where regressions and bugs are discovered and fixed.
334+
335+
In the Node.js `main` branch, we typically upgrade the version of V8 whenever a
336+
release of V8 finishes stable promotion and a _stable release_ is out.
337+
The schedule of V8 release cycles can be found
338+
[here](https://chromiumdash.appspot.com/schedule).
332339

333340
V8 updates can require a `NODE_MODULE_VERSION` bump if they change the native
334341
addon ABI. See the release process documentation for when

0 commit comments

Comments
 (0)