doc: update collaborator guide with LTS labels

PR-URL: #24379 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
nodejs · Nov 15, 2018 · 85f92016871c626d52d2ed74c610c851cda64cfd · 85f9201
1 parent c5e32fd
commit 85f92016871c626d52d2ed74c610c851cda64cfd
Unified Split

Showing with 13 additions and 9 deletions.

+13 −9 COLLABORATOR_GUIDE.md
diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md
@@ -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` and `v8.x`. Each of these is
+  
+paired with a staging branch: `v10.x-staging` and `v8.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
@@ -817,14 +817,18 @@ on backporting, please see the [backporting guide][].
 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
-  
-  for landing in the `v4.x-staging` branch.
+  
+* `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.
+  
+* `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
-  
-  in a future v4.x release
+  
+  in a future v6.x release.
 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.