Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit d394e9e

Browse filesBrowse files
Myles Borinsjasnell
authored andcommitted
doc: add LTS info to COLLABORATOR_GUIDE.md
There is currently no information in the Collaborators guide regarding LTS. This commit adds some basic copy explaining what LTS is, what is considered for LTS, and a simple way collaborators can help. Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Steven R. Loomis <srloomis@us.ibm.com> PR-URL: #3442
1 parent 81f6b54 commit d394e9e
Copy full SHA for d394e9e

File tree

Expand file treeCollapse file tree

1 file changed

+39
-0
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+39
-0
lines changed
Open diff view settings
Collapse file

‎COLLABORATOR_GUIDE.md‎

Copy file name to clipboardExpand all lines: COLLABORATOR_GUIDE.md
+39Lines changed: 39 additions & 0 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@
88
* [Landing Pull Requests](#landing-pull-requests)
99
- [Technical HOWTO](#technical-howto)
1010
- [I Just Made a Mistake](#i-just-made-a-mistake)
11+
- [Long Term Support](#long-term-support)
1112

1213
This document contains information for Collaborators of the Node.js
1314
project regarding maintaining the code, documentation and issues.
@@ -227,3 +228,41 @@ messages. However, you are only allowed to force push to any Node.js
227228
branch within 10 minutes from your original push. If someone else
228229
pushes to the branch or the 10 minute period passes, consider the
229230
commit final.
231+
232+
### Long Term Support
233+
234+
#### What is LTS?
235+
236+
Long Term Support (often referred to as *LTS*) guarantees application developers
237+
a 30 month support cycle with specific versions of Node.js.
238+
239+
You can find more information [in the full LTS plan](https://github.com/nodejs/lts#lts-plan).
240+
241+
#### How does LTS work?
242+
243+
Once a stable branch enters LTS, no new features may be added to that release. Changes are
244+
limited to bug fixes, security updates, possible npm updates, documentation updates, and certain
245+
performance improvements that can be demonstrated to not break existing applications.
246+
Semver-minor changes are only permitted if required for bug fixes. Semver-major changes are only
247+
permitted if required for critical security and bug fixes.
248+
249+
Once a stable branch moves into Maintenance mode, only **critical** bugs, **critical** security fixes,
250+
and documentation updates will be permitted.
251+
252+
#### How can I help?
253+
254+
When you send your pull request, consider including information about
255+
whether your change is breaking. If you think your patch can be backported,
256+
please feel free to include that information in the PR thread.
257+
258+
#### Who is doing the backporting?
259+
260+
The current plan is for commits to cherry pick into a staging branch (e.g. v4.x-staging),
261+
which can be done by anyone. The preference would be for the individual landing the commit
262+
on master to backport to staging branches if it is appropriate.
263+
264+
#### How is an LTS release cut?
265+
266+
When the LTS working group determines that a new LTS release is required, selected commits
267+
will be picked from the staging branch to be included in the release. This process of making
268+
a release will be a collaboration between the LTS working group and the Release team.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.