doc: add guide for maintaining V8 #9777
Conversation
doc/guides/maintaining-V8.md
Outdated
There was a problem hiding this comment.
"now the broweser" should be "not the browser"
doc/guides/maintaining-V8.md
Outdated
There was a problem hiding this comment.
authors? people to ask for help? something else?
There was a problem hiding this comment.
It was authors, but I have removed that line.
doc/guides/maintaining-V8.md
Outdated
doc/guides/maintaining-V8.md
Outdated
There was a problem hiding this comment.
is this different from backporting to active branches? doesn't v8 backport to active?
There was a problem hiding this comment.
I have tried to clarify this a bit further. The idea was that there are three classes of bugs, Node.js bugs that have (1) or have not (2) been fixed upstream, and bugs that have not been encountered by Node.js yet but upstream has identified as potentially interesting to Node (3).
doc/guides/maintaining-V8.md
Outdated
There was a problem hiding this comment.
where is this branch? I don't see it in nodejs/node.
There was a problem hiding this comment.
Thanks. Added link. FYI, it is at https://github.com/v8/node/tree/vee-eight-lkgr but we can bring this over to nodejs/node too if it is helpful.
doc/guides/maintaining-V8.md
Outdated
doc/guides/maintaining-V8.md
Outdated
There was a problem hiding this comment.
v6.x-staging is just an example, right? because backports might be necessary to any LTS staging branch
doc/guides/maintaining-V8.md
Outdated
There was a problem hiding this comment.
trace_event, or trace_event.h?
There was a problem hiding this comment.
trace event is a component. gtest_prod.h is just a file.
doc/guides/maintaining-V8.md
Outdated
ofrobots
force-pushed
the
maintaining-v8
branch
from
0983c42 to
f07f5c2
Compare
|
I will land this later today. |
|
Thanks. Landed as 11b0872. |
Ref: nodejs/Release#137 PR-URL: #9777 Reviewed-By: mhdawson - Michael Dawson <[email protected]> Reviewed-By: targos - Michaël Zasso <[email protected]>
Ref: nodejs/Release#137 PR-URL: #9777 Reviewed-By: mhdawson - Michael Dawson <[email protected]> Reviewed-By: targos - Michaël Zasso <[email protected]>
Ref: nodejs/Release#137 PR-URL: #9777 Reviewed-By: mhdawson - Michael Dawson <[email protected]> Reviewed-By: targos - Michaël Zasso <[email protected]>
Ref: nodejs/Release#137 PR-URL: #9777 Reviewed-By: mhdawson - Michael Dawson <[email protected]> Reviewed-By: targos - Michaël Zasso <[email protected]>
Ref: nodejs/Release#137 PR-URL: #9777 Reviewed-By: mhdawson - Michael Dawson <[email protected]> Reviewed-By: targos - Michaël Zasso <[email protected]>
Ref: nodejs/Release#137 PR-URL: #9777 Reviewed-By: mhdawson - Michael Dawson <[email protected]> Reviewed-By: targos - Michaël Zasso <[email protected]>
7 participants
Checklist
Affected core subsystem(s)
doc
Description of change
This document attempts to describe the processes for maintaining the V8 brances in Node.js LTS and Current releases.
Previously: nodejs/Release#137