Skip to content

LTS: rename LTS to Active LTS to avoid confusion #720

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bajtos merged 6 commits into from
Aug 2, 2018
Merged

LTS: rename LTS to Active LTS to avoid confusion #720

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
362bf87
LTS: rename LTS to Active LTS to avoid confusion
bajtos Aug 1, 2018
09bd637
fixup! fix numbering style
bajtos Aug 1, 2018
a78f742
fixup! remove min 6 months for Maintenance LTS
bajtos Aug 2, 2018
ae9064f
fixup! markdown table formatting
bajtos Aug 2, 2018
368bf7d
fixup! more tweaks
bajtos Aug 2, 2018
6933065
fixup! fix typo
bajtos Aug 2, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
60 changes: 43 additions & 17 deletions pages/en/contrib/LTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,25 +5,26 @@ tags: [contributing, community]
keywords: LoopBack, versioning, long-term support
sidebar: home_sidebar
permalink: /doc/en/contrib/Long-term-support.html
summary: LoopBack maintains a current version, a long-term support (LTS) version, and a maintenance version.
summary: LoopBack maintains a Current version, an Active long-term support (LTS) version, and one or more Maintenance LTS versions.
---

## Overview

In general, LoopBack version numbers adhere to [semantic versioning](http://semver.org/) conventions.
LoopBack adheres to [semantic versioning](http://semver.org/) conventions and
implements [Module LTS policy](https://github.com/CloudNativeJS/ModuleLTS).

The LoopBack project implements [Module LTS
policy](https://github.com/CloudNativeJS/ModuleLTS) and maintains:
The project maintains:

- A _Current_ version where most of the development occurs.
- A _Long-term support (LTS)_ version that does not add new features but gets bug fixes.
- One or more _maintenance_ versions that receive only critical bug fixes.
- An _Active LTS_ (Long-Term Support) version that does not add new features but gets bug fixes.
- One or more _Maintenance LTS_ versions that receive only critical bug fixes.


## LTS versions
## Active LTS

A major LoopBack version (for example, 3.x) enters LTS when the next major version is
released (for example, 4.0) and stays in LTS mode for at least six months.
A major LoopBack version (for example, 3.x) enters Active LTS when the next
major version is released (for example, 4.0) and stays in Active LTS mode for
at least six months.

Once a release enters LTS, no new features may be added to that release.
Changes are limited to:
Expand All @@ -32,22 +33,47 @@ Changes are limited to:

2. Security updates;

3. Non-semver-major npm updates;
3. Relevant documentation updates;

4. Relevant documentation updates;

5. Certain performance improvements where the risk of breaking existing
4. Certain performance improvements where the risk of breaking existing
applications is minimal;

6. Changes that introduce large amount of code churn where the risk of breaking
5. Changes that introduce large amount of code churn where the risk of breaking
existing applications is low and where the change in question may significantly
ease the ability to backport future changes due to the reduction in diff noise.
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.

## Maintenance versions
Support for new major Node.js versions may be added if the required changes
have a low risk of breaking existing applications.

## Maintenance LTS

When a new major version (for example, 4.0) is released, the oldest LTS version (for example, 2.x) enters maintenance mode, where it will stay at least for another six months and so long as the Node.js LTS versions available at release time are maintained by the Node.js project.
When a new major version (for example, 4.0) is released, the oldest Active LTS
version (for example, 2.x) enters Maintenance LTS mode, where it will stay for
as long as the Node.js LTS versions available at release time are maintained by
the Node.js project.

Once a release moves into maintenance mode, only critical bugs, critical
Once a release moves into Maintenance LTS mode, only critical bugs, critical
security fixes, and documentation updates will be permitted.

Specifically, adding support for new major Node.js versions is not permitted.

## Examples

In August 2018, there were two major Node.js versions covered by the LTS plan:
6.x and 8.x; and two supported LoopBack versions: 2.x and 3.x.

Framework | Status | Published | EOL | Runtime | GA | EOL
-- | -- | -- | -- | -- | -- | --
Loopback 3 | Current | Dec 2016 | Dec 2019<br/>_(minimum)_ | Node 8 | Oct 2017 | Dec 2019
Loopback 2 | Active LTS | Jul 2014 | Apr 2019 | Node 6 | Oct 2016 | Apr 2019

Assuming LoopBack 4.0 is released in October 2018 to align with Node.js 10.x
entering LTS:

Framework | Status | Published | EOL | Runtime | GA | EOL
-- | -- | -- | -- | -- | -- | --
LoopBack 4 | Current | Oct 2018 | Apr 2021<br/>_(minimum)_| Node 10 | Oct 2018 | Apr 2021
Loopback 3 | Active LTS | Dec 2016 | Dec 2019 | Node 8 | Oct 2017 | Dec 2019
Loopback 2 | Maintenance LTS | Jul 2014 | Apr 2019 | Node 6 | Oct 2016 | Apr 2019