GeezerVison

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

GeezerVison is showing github.com — doc: update mark release line lts on release guide · nodejs/node@17380a1

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

doc/contributing
- releases.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

`‎doc/contributing/releases.md‎`

Copy file name to clipboardExpand all lines: doc/contributing/releases.md

+37Lines changed: 37 additions & 0 deletions

Display the source diff
Display the rich diff

Original file line number	Diff line number	Diff line change
`@@ -961,6 +961,31 @@ _In whatever form you do this..._`
`961`	`961`
`962`	`962`	`### Marking a release line as LTS`
`963`	`963`
	`964`	`+The process of marking a release line as LTS has been automated using`
	`965`	`+[node-core-utils](https://github.com/nodejs/node-core-utils).`
	`966`	`+`
	`967`	`+Start by checking out the staging branch for the release line that is going to`
	`968`	`+be marked as LTS, e.g:`
	`969`	`+`
	`970`	+```console
	`971`	`+$ git checkout v1.x-staging`
	`972`	+```
	`973`	`+`
	`974`	`+Next, make sure you have node-core-utils installed:`
	`975`	`+`
	`976`	+```console
	`977`	`+$ npm i -g node-core-utils`
	`978`	+```
	`979`	`+`
	`980`	`+Run the prepare LTS release command:`
	`981`	`+`
	`982`	+```console
	`983`	`+$ git node release --prepare --startLTS`
	`984`	+```
	`985`	`+`
	`986`	`+<details>`
	`987`	`+<summary>Manual steps for reference.</summary>`
	`988`	`+`
`964`	`989`	`To mark a release line as LTS, the following changes must be made to`
`965`	`990`	`src/node_version.h`:
`966`	`991`
`@@ -989,6 +1014,18 @@ For example:`
`989`	`1014`
`990`	`1015`	`The changes must be made as part of a new semver-minor release.`
`991`	`1016`
	`1017`	`+Updating changelogs to properly reflect the changes between Current and`
	`1018`	`+Long Term Support is also necessary, along with adding a reference to the`
	`1019`	`+current LTS codename in its release line changelog file.`
	`1020`	`+`
	`1021`	+The `test/parallel/test-process-release.js` file might also need to be updated.
	`1022`	`+`
	`1023`	+In case you can not run the automated `node-core-utils` command and you are
	`1024`	`+currently running these steps manually it's a good idea to refer to previous`
	`1025`	`+LTS proposal PRs and make sure all required changes are covered.`
	`1026`	`+`
	`1027`	`+</details>`
	`1028`	`+`
`992`	`1029`	`### Update release labels`
`993`	`1030`
`994`	`1031`	The `lts-watch-vN.x` issue label must be created, with the same color as other

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.