Skip to content

Update LTS policy to adhere to Module LTS policy #715

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 2 commits into from
Jul 30, 2018
Merged

Update LTS policy to adhere to Module LTS policy #715

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
13060ff
Move LTS to home_sidebar
bajtos Jul 26, 2018
0f9e8e7
Update LTS policy to honour Module LTS policy
bajtos Jul 26, 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
4 changes: 0 additions & 4 deletions _data/sidebars/contrib_sidebar.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,6 @@ children:
url: Reporting-issues.html
output: web, pdf

- title: Long-term support
url: Long-term-support.html
output: web

- title: Contributing code
url: code-contrib.html
output: web, pdf
Expand Down
4 changes: 4 additions & 0 deletions _data/sidebars/home_sidebar.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,7 @@ children:
- title: Contributing to LoopBack
url: /doc/en/contrib/index.html
output: web

- title: Long-term support
url: /doc/en/contrib/Long-term-support.html
Copy link
Contributor

@virkt25 virkt25 Jul 26, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this map to the previous URL that was in the contrib_sidebar.yml?

Copy link
Member Author

@bajtos bajtos Jul 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it does.

My commit is moving "Long-term support" from "Contributing" sidebar to the main/home sidebar in order to give it more visibility.

output: web
17 changes: 10 additions & 7 deletions pages/en/contrib/LTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,23 +3,27 @@ title: Long-term support
lang: en
tags: [contributing, community]
keywords: LoopBack, versioning, long-term support
sidebar: contrib_sidebar
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.
---

## Overview

In general, LoopBack version numbers adhere to [semantic versioning](http://semver.org/) conventions.

The LoopBack project maintains:
The LoopBack project implements [Module LTS
policy](https://github.com/CloudNativeJS/ModuleLTS) and 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.
- One or more _maintenance_ versions that receive only critical bug fixes.


## LTS versions

A major LoopBack version (for example, 2.x) enters LTS when the next major version is
released (for example, 3.x) and stays in LTS mode for at least six months.
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.

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

## Maintenance versions

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 for another six months at
minimum.
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.

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