Lines Matching full:branches

8 to support. V8 branches in Node.js lack of an official maintenance process due
12 a workflow for maintaining the V8 branches in both Node.js LTS and current
19 there are three V8 branches that are **active**.
31 All older branches are abandoned and are not maintained by the V8 team.
35 The process for backporting bug fixes to active branches is officially
38 * V8 only supports active branches. There is no testing done on any branches
53 At any given time Node.js needs to be maintaining a few different V8 branches
55 includes the following branches<sup>1</sup>:
146 these branches for many months (Current branches) or several
147 years (LTS branches).
157 * Fixed, but needs backport. The bug may need porting to one or more branches.
158   * Backporting to active branches.
159   * Backporting to abandoned branches.
176   branches that are still active or are branches that Node.js cares about.
179 ### Backporting to active branches
181 If the bug exists in any of the active V8 branches, we may need to get the fix
182 backported. At any given time, there are [two active branches][V8ActiveBranches]
187 * Identify if any active V8 branches still contain the bug:
193     * Attach *merge-request-x.x* labels to the bug for any active branches
202   to Abandoned branches'.
206 ### Backporting to abandoned branches
208 Abandoned V8 branches are supported in the Node.js repository. The fix needs
238   --directory=deps/v8`. If the branches have diverged significantly, this may
271   backport to `v6.x` as the other LTS branches weren't affected by this bug.
276 that might be applicable to the abandoned branches in use by Node.js. This is
285   applicable to abandoned branches in use by Node.js. This list if regularly
382 branches. This has several benefits:
385   the tips of various V8 branches in `nodejs/v8`.
386 * It would simplify cherry-picking and porting of fixes between branches as the
426 [V8ActiveBranches]: https://build.chromium.org/p/client.v8.branches/console