GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — doc: update collaborator guide with LTS labels · nodejs/node@85f9201

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

COLLABORATOR_GUIDE.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

`‎COLLABORATOR_GUIDE.md‎`

Copy file name to clipboardExpand all lines: COLLABORATOR_GUIDE.md

+13-9Lines changed: 13 additions & 9 deletions

Display the source diff
Display the rich diff

Original file line number	Diff line number	Diff line change
`@@ -794,8 +794,8 @@ TSC for further discussion.`
`794`	`794`
`795`	`795`	`#### How are LTS Branches Managed?`
`796`	`796`
`797`		-There are multiple LTS branches, e.g. `v8.x` and `v6.x`. Each of these is paired
`798`		-with a staging branch: `v8.x-staging` and `v6.x-staging`.
	`797`	+There are multiple LTS branches, e.g. `v10.x` and `v8.x`. Each of these is
	`798`	+paired with a staging branch: `v10.x-staging` and `v8.x-staging`.
`799`	`799`
`800`	`800`	`As commits land on the master branch, they are cherry-picked back to each`
`801`	`801`	`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][].`
`817`	`817`
`818`	`818`	`Several LTS related issue and PR labels have been provided:`
`819`	`819`
`820`		-* `lts-watch-v6.x` - tells the LTS WG that the issue/PR needs to be considered
`821`		- for landing in the `v6.x-staging` branch.
`822`		-* `lts-watch-v4.x` - tells the LTS WG that the issue/PR needs to be considered
`823`		- for landing in the `v4.x-staging` branch.
	`820`	+* `lts-watch-v10.x` - tells the LTS WG that the issue/PR needs to be
	`821`	+ considered for landing in the `v10.x-staging` branch.
	`822`	+* `lts-watch-v8.x` - tells the LTS WG that the issue/PR needs to be
	`823`	+ considered for landing in the `v8.x-staging` branch.
	`824`	+* `lts-watch-v6.x` - tells the LTS WG that the issue/PR needs to be
	`825`	+ considered for landing in the `v6.x-staging` branch.
	`826`	+* `land-on-v10.x` - tells the release team that the commit should be landed
	`827`	`+ in a future v10.x release.`
	`828`	+* `land-on-v8.x` - tells the release team that the commit should be landed
	`829`	`+ in a future v8.x release.`
`824`	`830`	* `land-on-v6.x` - tells the release team that the commit should be landed
`825`		`- in a future v6.x release`
`826`		-* `land-on-v4.x` - tells the release team that the commit should be landed
`827`		`- in a future v4.x release`
	`831`	`+ in a future v6.x release.`
`828`	`832`
`829`	`833`	`Any Collaborator can attach these labels to any PR/issue. As commits are`
`830`	`834`	landed into the staging branches, the `lts-watch-` label will be removed.

0 commit comments

Comments

0 (0)

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.