Skip to content
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

add lts annoucement #79

Merged
merged 1 commit into from
Nov 26, 2018
Merged

add lts annoucement #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 14 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@

**NOTE: The loopback-sdk-angular-cli module supersedes [loopback-angular-cli](https://www.npmjs.org/loopback-angular-cli). Please update your package.json accordingly.**

This module is in Active LTS mode, new features are no longer accepted.
(See [Module Long Term Support Policy](#module-long-term-support-policy) below.)
LoopBack 3 users looking for new features are encouraged to upgrade to LoopBack 4. Refer to [loopback-next#1849](https://github.com/strongloop/loopback-next/issues/1849) for more information on how to upgrade.

CLI tools for the [LoopBack AngularJS SDK](https://github.com/strongloop/loopback-sdk-angular).

See the official [LoopBack AngularJS SDK documentation](https://loopback.io/doc/en/lb2/AngularJS-JavaScript-SDK.html)
Expand All @@ -11,3 +15,13 @@ for more information.

Discuss features and ask questions on [LoopBack Forum](https://groups.google.com/forum/#!forum/loopbackjs).

## Module Long Term Support Policy

This module adopts the [Module Long Term Support (LTS)](http://github.com/CloudNativeJS/ModuleLTS) policy, with the following End Of Life (EOL) dates:

| Version | Status | Published | EOL |
| ------- | --------------- | --------- | -------- |
Copy link
Member

Choose a reason for hiding this comment

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

After a second thought, I wonder how that Apr / Dec 2019 come up?
According to the node.js LTS schedule https://github.com/nodejs/Release,

  • when 1.x was out (jul 2014), the "current" Node.js version at that time should be 0.10. -> EOL already
  • when 2.x was out (dec 2015), the "current" Node.js version at that time should be 4.x. -> EOL already
  • when 3.x was out (feb 2017), the "current" Node.js version at that time should be 6.x -> EOL April 2019.

Are the LTS schedules proposed in this PR based on the fact that we should allow some time for users to update to a more current version so it is not exactly matching the Node.js LTS schedule? If yes, I'm good with it.

Copy link
Member

Choose a reason for hiding this comment

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

I was discussing EOL times with Chris and the rule for determining EOL is slightly different. We need to find all pairs of (Node version N.x, Module version M.x) that passed the following condition at some point in time: N.x was the latest LTS version of Node, M.x was the latest version of the module. For each of these pairs, M.x must be supported until N.x goes EOL.

So for example, because loopback-sdk-angular-cli 2.x was released in Dec 2015, after Node.js 4.x went LTS, we must assume that some people may have picked loopback-sdk-angular-cli 1.x to use with Node.js 4.x, an therefore loopback-sdk-angular-cli must be supported at least as long as Node.js 4.x is in LTS.

Here are the current LTS versions of Node.js:

  • 6.x in LTS from 2016-10-18
  • 8.x in LTS from 2017-10-31
  • 10.x in LTS from 2018-10-30

When Node.js 6.x entered LTS, the latest angular-cli version was 2.x, therefore we need to support 2.x until April 2019.

When Node.js 8.x entered LTS, the latest angular-cli version was 3.x, therefore we need to support 3.x until Dec 2019.

There is no need to support 1.x version any more.

Copy link
Member

Choose a reason for hiding this comment

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

+1 - no need to support 1.x version

| 3.x | Active LTS | Feb 2017 | Dec 2019 |
| 2.x | Maintenance LTS | Dec 2015 | Apr 2019 |

Learn more about our LTS plan in the [docs](https://loopback.io/doc/en/contrib/Long-term-support.html).