lukechilds
/
node
mirror of https://github.com/lukechilds/node.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

doc: update LTS info for current releases 

The COLLABORATOR_GUIDE was still listing v0.10 and v0.12 as LTS when
they are EOL now.

PR-URL: https://github.com/nodejs/node/pull/10720
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
v7.x
Evan Lucas 8 years ago
committed by Italo A. Casas
parent
3f1775707e
commit
9c89b2f704
1 changed files with 6 additions and 11 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 17
      COLLABORATOR_GUIDE.md

17
COLLABORATOR_GUIDE.md
View File

@ -319,9 +319,8 @@ CTC for further discussion.
#### How are LTS Branches Managed? #### How are LTS Branches Managed?
There are currently three LTS branches: `v4.x`, `v0.10`, and `v0.12`. Each There are currently two LTS branches: `v6.x` and `v4.x`. Each of these is paired
of these is paired with a "staging" branch: `v4.x-staging`, `v0.10-staging`, with a "staging" branch: `v6.x-staging` and `v4.x-staging`.
and `v0.12-staging`.
As commits land in `master`, they are cherry-picked back to each staging As commits land in `master`, they are cherry-picked back to each staging
branch as appropriate. If the commit applies only to the LTS branch, the branch as appropriate. If the commit applies only to the LTS branch, the
@ -342,18 +341,14 @@ please feel free to include that information in the PR thread.
Several LTS related issue and PR labels have been provided: Several LTS related issue and PR labels have been provided:
* `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 * `lts-watch-v4.x` - tells the LTS WG that the issue/PR needs to be considered
for landing in the `v4.x-staging` branch. for landing in the `v4.x-staging` branch.
* `lts-watch-v0.10` - tells the LTS WG that the issue/PR needs to be considered * `land-on-v6.x` - tells the release team that the commit should be landed
for landing in the `v0.10-staging` branch. in a future v6.x release
* `lts-watch-v0.12` - tells the LTS WG that the issue/PR needs to be considered
for landing in the `v0.12-staging` branch.
* `land-on-v4.x` - tells the release team that the commit should be landed * `land-on-v4.x` - tells the release team that the commit should be landed
in a future v4.x release in a future v4.x release
* `land-on-v0.10` - tells the release team that the commit should be landed
in a future v0.10 release
* `land-on-v0.12` - tells the release team that the commit should be landed
in a future v0.12 release
Any collaborator can attach these labels to any PR/issue. As commits are Any collaborator can attach these labels to any PR/issue. As commits are
landed into the staging branches, the `lts-watch-` label will be removed. landed into the staging branches, the `lts-watch-` label will be removed.

Write Preview
Loading…
Cancel
Save