Skip to content
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

Jump to bottom

docs: edit LTS labels section #24369

Closed
wants to merge 7 commits into from
Closed

docs: edit LTS labels section #24369

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
5fa001c
doc: add v8 and v10 tags in the LTS section
cfanoulis Nov 14, 2018
10a6a35
http: else case is not reachable
Nov 6, 2018
af864b8
test: deep object to table not covered
ovhemert Nov 8, 2018
92beff9
Revert "util: change util.inspect depth default"
devsnek Nov 12, 2018
887c490
timers: fix priority queue removeAt
apapirovski Nov 12, 2018
37205b3
lib: improved conditional check in zlib
dYale Nov 6, 2018
c0cd39b
test: add typeerror for vm/compileFunction params
dYale Nov 6, 2018
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
12 changes: 10 additions & 2 deletions COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -794,8 +794,8 @@ TSC for further discussion.

#### How are LTS Branches Managed?

There are multiple LTS branches, e.g. `v8.x` and `v6.x`. Each of these is paired
with a staging branch: `v8.x-staging` and `v6.x-staging`.
There are multiple LTS branches, e.g. `v10.x, `v8.x` and `v6.x`. Each of these is paired
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
There are multiple LTS branches, e.g. `v10.x, `v8.x` and `v6.x`. Each of these is paired
There are multiple LTS branches, e.g. `v10.x`, `v8.x` and `v6.x`. Each of these is paired

with a staging branch: `v10.x-staging`, `v8.x-staging` and `v6.x-staging`.

As commits land on the master branch, they are cherry-picked back to each
staging branch as appropriate. If the commit applies only to the LTS branch, the
Expand All @@ -817,10 +817,18 @@ on backporting, please see the [backporting guide][].

Several LTS related issue and PR labels have been provided:

* `lts-watch-v10.x` - tells the LTS WG that the issue/PR needs to be considered
for landing in the `v10.x-staging` branch.
* `lts-watch-v8.x` - tells the LTS WG that the issue/PR needs to be considered
for landing in the `v8.x-staging` branch.
* `lts-watch-v6.x` - tells the LTS WG that the issue/PR needs to be considered
for landing in the `v6.x-staging` branch.
* `lts-watch-v4.x` - tells the LTS WG that the issue/PR needs to be considered
for landing in the `v4.x-staging` branch.
* `land-on-v10.x` - tells the release team that the commit should be landed
in a future v10.x release
* `land-on-v8.x` - tells the release team that the commit should be landed
in a future v8.x release
* `land-on-v6.x` - tells the release team that the commit should be landed
in a future v6.x release
* `land-on-v4.x` - tells the release team that the commit should be landed
Expand Down