Skip to content

Commit

Permalink
doc: clarify maintenance period for odd releases
Browse files Browse the repository at this point in the history
i.e. that there isn't one.

This was agreed in the LTS meeting: nodejs#213

PR-URL: nodejs#220
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
  • Loading branch information
gibfahn authored and ChALkeR committed Jun 30, 2018
1 parent 93391e6 commit 61b75a1
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,9 @@ on the Periodic Table of Elements. For each upcoming LTS release, the LTS
Working Group will select a handful of candidate names and submit those for a
collaborator vote.

An odd-numbered major release will cease to be actively updated when the
subsequent even-numbered major release is cut.

## LTS Staging Branches

Every LTS major version has two branches in the GitHub repository: a release
Expand Down

0 comments on commit 61b75a1

Please sign in to comment.