Skip to content

doc: V8 branch used in 8.x not active anymore #18155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fhinkel wants to merge 1 commit into from
Closed

doc: V8 branch used in 8.x not active anymore #18155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions doc/guides/maintaining-V8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,10 @@ includes the following branches<sup>1</sup>:
</table>


The versions of V8 used in Node.js v4.x and v6.x have already been abandoned by
upstream V8. However, Node.js needs to continue supporting these branches for
many months (Current branches) or several years (LTS branches).
The versions of V8 used in Node.js v4.x, v6.x, and 8.x have already been
Copy link
Contributor

@evanlucas evanlucas Jan 15, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we make this consistent? Either 4.x, 6.x, and 8.x or v4.x, v6.x, and v8.x?

Copy link
Member Author

@fhinkel fhinkel Jan 15, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deliberately without the v, because starting with 8, we refer to Node as Node 8. But I'm happy to change it if we prefer consistency.

Copy link
Contributor

@evanlucas evanlucas Jan 15, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah yea, that's right. I'm indifferent :]

Copy link
Member

@mhdawson mhdawson Jan 15, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it make sense to list the versions and continually update? Wondering if we could just use some wording like "The versions of V8 used in Node.js have most often already been abanded by upstream V8."

abandoned by upstream V8. However, Node.js needs to continue supporting
these branches for many months (Current branches) or several
years (LTS branches).

## Maintenance Process

Expand Down