Skip to content

Commit fc0aa50

Browse files
Trotttargos
authored andcommitted
doc: remove How Does LTS Work section from Collaborator Guide
The How Does LTS Work section duplicates material in the release plan, to which there is already a link in the doc. Unfortunately, it has gone out of sync with the release plan, resulting in incorrect material being in the Collaborator Guide. (The Release WG needs to approve certain changes, not LTS WG as the guide currently says. It used to be the LTS WG, but that changed.) Instead of duplicating material in the Collaborator Guide and risking that the two documents contradict each other again, instruct the reader to refer to the release plan as the canonical source of information. PR-URL: #26723 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
1 parent bc9f6d8 commit fc0aa50

File tree

1 file changed

+3
-14
lines changed

1 file changed

+3
-14
lines changed

COLLABORATOR_GUIDE.md

+3-14
Original file line numberDiff line numberDiff line change
@@ -639,20 +639,9 @@ git push upstream master
639639

640640
Long Term Support (LTS) guarantees 30-month support cycles for specific Node.js
641641
versions. You can find more information
642-
[in the full release plan](https://github.com/nodejs/Release#release-plan).
643-
644-
#### How does LTS work?
645-
646-
Once a Current branch enters LTS, changes in that branch are limited to bug
647-
fixes, security updates, possible npm updates, documentation updates, and
648-
certain performance improvements that can be demonstrated to not break existing
649-
applications. Semver-minor changes are only permitted if required for bug fixes
650-
and then only on a case-by-case basis with LTS WG and possibly Technical
651-
Steering Committee (TSC) review. Semver-major changes are permitted only if
652-
required for security-related fixes.
653-
654-
Once a Current branch moves into Maintenance mode, only **critical** bugs,
655-
**critical** security fixes, and documentation updates will be permitted.
642+
[in the full release plan](https://github.com/nodejs/Release#release-plan). Once
643+
a branch enters LTS, the release plan limits the types of changes permitted in
644+
the branch.
656645

657646
#### Landing semver-minor commits in LTS
658647

0 commit comments

Comments
 (0)