The project maintains:
- A Current version where most of the development occurs.
- 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.
Below is the LTS schedule on the LoopBack versions:
|LoopBack 4||Current||Oct 2018||Apr 2021
|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|
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:
Relevant documentation updates;
Certain performance improvements where the risk of breaking existing applications is minimal;
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.
Support for new major Node.js versions may be added if the required changes have a low risk of breaking existing applications.
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 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.