Commit 512feaa
doc: remove outdated sections from maintaining-v8
PR-URL: #46137
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>1 parent 874054f commit 512feaa
1 file changed
Lines changed: 8 additions & 110 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -15,20 +15,10 @@ releases, and discusses how the Node.js and V8 teams at Google can help. | |||
| 15 | 15 | ## V8 release schedule | |
| 16 | 16 | ||
| 17 | 17 | V8 and Chromium follow a | |
| 18 | - [roughly 6-week release cadence][ChromiumReleaseCalendar]. At any given time | ||
| 19 | - there are three V8 branches that are **active**. | ||
| 20 | - | ||
| 21 | - For example, at the time of this writing: | ||
| 22 | - | ||
| 23 | - * **Stable**: V8 5.4 is currently shipping as part of Chromium stable. This | ||
| 24 | - branch was created approx. 6 weeks before from when V8 5.3 shipped as stable. | ||
| 25 | - * **Beta**: V8 5.5 is currently in beta. It will be promoted to stable next; | ||
| 26 | - approximately 6 weeks after V8 5.4 shipped as stable. | ||
| 27 | - * **Master**: V8 tip-of-tree corresponds to V8 5.6. This branch gets regularly | ||
| 28 | - released as part of the Chromium **canary** builds. This branch will be | ||
| 29 | - promoted to beta next when V8 5.5 ships as stable. | ||
| 30 | - | ||
| 31 | - All older branches are abandoned and are not maintained by the V8 team. | ||
| 18 | + [roughly 4-week release cadence][ChromiumReleaseCalendar]. At any given time | ||
| 19 | + there are several V8 branches that are **active**, see the | ||
| 20 | + [V8 release process](https://v8.dev/docs/release-process). All older branches | ||
| 21 | + are abandoned and are not maintained by the V8 team. | ||
| 32 | 22 | ||
| 33 | 23 | ### V8 merge process overview | |
| 34 | 24 | ||
@@ -51,97 +41,8 @@ documented [on the V8 wiki][V8MergingPatching]. The summary of the process is: | |||
| 51 | 41 | ## Node.js support requirements | |
| 52 | 42 | ||
| 53 | 43 | At any given time Node.js needs to be maintaining a few different V8 branches | |
| 54 | - for the various Current, LTS, and nightly releases. At present this list | ||
| 55 | - includes the following branches:[^1] | ||
| 56 | - | ||
| 57 | - <table> | ||
| 58 | - <tr> | ||
| 59 | - <td><strong>Release</strong> | ||
| 60 | - </td> | ||
| 61 | - <td><strong>Support Start</strong> | ||
| 62 | - </td> | ||
| 63 | - <td><strong>Support End</strong> | ||
| 64 | - </td> | ||
| 65 | - <td><strong>V8 version</strong> | ||
| 66 | - </td> | ||
| 67 | - <td><strong>V8 branch released</strong> | ||
| 68 | - </td> | ||
| 69 | - <td><strong>V8 branch abandoned</strong> | ||
| 70 | - </td> | ||
| 71 | - </tr> | ||
| 72 | - <tr> | ||
| 73 | - <td>Node.js 4.x | ||
| 74 | - </td> | ||
| 75 | - <td>2015-10-01 | ||
| 76 | - </td> | ||
| 77 | - <td>April 2018 | ||
| 78 | - </td> | ||
| 79 | - <td>4.5 | ||
| 80 | - </td> | ||
| 81 | - <td>2015-09-01 | ||
| 82 | - </td> | ||
| 83 | - <td>2015-10-13 | ||
| 84 | - </td> | ||
| 85 | - </tr> | ||
| 86 | - <tr> | ||
| 87 | - <td>Node.js 6.x | ||
| 88 | - </td> | ||
| 89 | - <td>2016-04-01 | ||
| 90 | - </td> | ||
| 91 | - <td>April 2019 | ||
| 92 | - </td> | ||
| 93 | - <td>5.1 | ||
| 94 | - </td> | ||
| 95 | - <td>2016-05-31 | ||
| 96 | - </td> | ||
| 97 | - <td>2016-06-26 | ||
| 98 | - </td> | ||
| 99 | - </tr> | ||
| 100 | - <tr> | ||
| 101 | - <td>Node.js 8.x | ||
| 102 | - </td> | ||
| 103 | - <td>2017-05-30 | ||
| 104 | - </td> | ||
| 105 | - <td>December 2019 | ||
| 106 | - </td> | ||
| 107 | - <td>6.1 (soon to be 6.2) | ||
| 108 | - </td> | ||
| 109 | - <td>2017-10-17 (6.2) | ||
| 110 | - </td> | ||
| 111 | - <td>~2017-12-05 (6.2) | ||
| 112 | - </td> | ||
| 113 | - </tr> | ||
| 114 | - <tr> | ||
| 115 | - <td>Node.js 9.x | ||
| 116 | - </td> | ||
| 117 | - <td>2017-10-31 | ||
| 118 | - </td> | ||
| 119 | - <td>April 2018 | ||
| 120 | - </td> | ||
| 121 | - <td>6.2 | ||
| 122 | - </td> | ||
| 123 | - <td>2017-10-17 | ||
| 124 | - </td> | ||
| 125 | - <td>~2017-12-05 | ||
| 126 | - </td> | ||
| 127 | - </tr> | ||
| 128 | - <tr> | ||
| 129 | - <td>master | ||
| 130 | - </td> | ||
| 131 | - <td>N/A | ||
| 132 | - </td> | ||
| 133 | - <td>N/A | ||
| 134 | - </td> | ||
| 135 | - <td>6.2 | ||
| 136 | - </td> | ||
| 137 | - <td>2017-10-17 | ||
| 138 | - </td> | ||
| 139 | - <td>~2017-12-05 | ||
| 140 | - </td> | ||
| 141 | - </tr> | ||
| 142 | - </table> | ||
| 143 | - | ||
| 144 | - The versions of V8 used in Node.js v4.x, v6.x, and 8.x have already been | ||
| 44 | + for the various Current, LTS, and nightly releases. | ||
| 45 | + The versions of V8 used in Node.js may have already been | ||
| 145 | 46 | abandoned by upstream V8. However, Node.js needs to continue supporting | |
| 146 | 47 | these branches for many months (Current branches) or several | |
| 147 | 48 | years (LTS branches). | |
@@ -280,7 +181,7 @@ See [`git-node-v8-backport`][] for more documentation and additional options. | |||
| 280 | 181 | * Run the Node.js [V8 CI][] in addition to the [Node.js CI][]. | |
| 281 | 182 | The CI uses the `test-v8` target in the `Makefile`, which uses | |
| 282 | 183 | `tools/make-v8.sh` to reconstruct a git tree in the `deps/v8` directory to | |
| 283 | - run V8 tests.[^2] | ||
| 184 | + run V8 tests.[^1] | ||
| 284 | 185 | ||
| 285 | 186 | Here are the steps for the bug mentioned above: | |
| 286 | 187 | ||
@@ -463,10 +364,7 @@ This would require some tooling to: | |||
| 463 | 364 | promoted from `nodejs/v8` to `nodejs/node`. | |
| 464 | 365 | * Enabled the V8-CI build in Jenkins to build from the `nodejs/v8` fork. | |
| 465 | 366 | ||
| 466 | - [^1]: Node.js 0.12 and older are intentionally omitted from this document | ||
| 467 | - as their support has ended. | ||
| 468 | - | ||
| 469 | - [^2]: On macOS, the V8 tests require a full Xcode install, not just the "command | ||
| 367 | + [^1]: On macOS, the V8 tests require a full Xcode install, not just the "command | ||
| 470 | 368 | line tools" for Xcode. | |
| 471 | 369 | ||
| 472 | 370 | [ChromiumReleaseCalendar]: https://www.chromium.org/developers/calendar | |
0 commit comments