Skip to content

Commit

Permalink
lts: remove -breaking and clarify allowed lts changes
Browse files Browse the repository at this point in the history
  • Loading branch information
jasnell committed Jul 2, 2015
1 parent da5d234 commit f7208d3
Showing 1 changed file with 6 additions and 11 deletions.
17 changes: 6 additions & 11 deletions README.md
Expand Up @@ -27,24 +27,19 @@ basic details are as follows:
6. There will be no LTS releases cut from the nodejs/io.js stream.
7. Once a release enters LTS, no new features may be added to that release.
Changes are limited to bug fixes, security updates, documentation updates,
performance improvements, etc. Semver-minor changes are only permitted if
certain performance improvements that can be demonstrated to not break
existing applications, etc. Semver-minor changes are only permitted if
required for bug fixes. Semver-major changes are only permitted if required
for critical security and bug fixes.
8. Once a release moves into Maintenance mode, only ***critical*** bugs,
***critical*** security fixes, and documentation updates will be permitted.
9. *semver-major* bumps are permitted *between* LTS releases. The LTS release
will be cut from the last release before a *semver-major* bump. The
will be cut from the last stable release before a *semver-major* bump. The
implication of this is that the *semver-major* bump should be timed to
roughly coincide with the regular yearly LTS release schedule.

Note that *semver-major* changes that happen to land *within* an LTS release
cause a *semver-minor* increase rather than a *semver-major* increase. This is
to prevent such changes in the LTS from clashing with the master release
stream. When *semver-major* occur, however, a `-breaking` build metadata would
be added to the release version. For example, if the current LTS release
version is `v4.4.1`, and a new semver-major change is required to address a
critical security issue, the fixed LTS version would become `v4.5.0-breaking`.
**(LTS WG and TSC members... please weigh in on this idea)**
10. Note that while it is possible that critical security and bug fixes may
lead to *semver-major* changes landing within an LTS stream, such
situations will be rare and will land as *semver-minor* bumps.

## Example

Expand Down

0 comments on commit f7208d3

Please sign in to comment.