How frequently does Learnosity release new versions?
As an agile company, Learnosity releases new versions of our products extremely regularly - in fact, in most cases, we're pushing out new features and functionality on a three-weekly basis!
While we maintain full backwards compatibility with every new release - for production systems we strongly recommend using a supported, stable, Long Term Support (LTS) version.
Latest
Every three weeks, for our APIs, we release new code to latest. This can be new features, in-development features, and bug fixes since the last 'latest' release, etc. These releases are bleeding edge, and should be used for:
- New in-development projects, targeting our next Long Term Support releases (see below).
- Proof of Concept code, taking advantage of forthcoming major releases.
Long Term Support (LTS)
Every four months, we release a major milestone release, to better match our customers’ development cadence. Every February, June and October we release production ready versions of our APIs that will be supported for two years. This applies across all of our core APIs.
Long Term Support releases are strong, complete, stable and should be used for:
- All in-production platforms
- In-development projects, going live before our next Long Term Support release.
Release support lifecycle
Here's what you can expect from each of the release types above:
| latest | Long Term Support (LTS) * | |
|---|---|---|
| Provides code stability | No | Yes |
| Receives security, performance and bug patches automatically | Yes | Yes |
| Receives new features or feature enhancements after initial release | Yes | No |
| Environments recommended for | Development or Proof of Concept | Production or QA |
| Receives general security, performance and bug fixes for | N/A | 16 months |
| Receives critical security, performance and bug fixes for | N/A | 24 months |
| Start of End of Life (EOL) | N/A | 24 months |
| Sunset date and removal | N/A | 30 months |
When do LTS versions go end of life (EOL)?
LTS versions have a 16 month lifespan for general security updates, performance updates and bug fixes. After that, they will receive critical security updates, performance updates and bug fixes until their end of life date at 24 months from first release.
For the first 16 months, LTS releases receive general security, performance and bug fixes.
After that, they transition into an End of Life (EOL) phase.
2020 LTS Versions Lifecycle
LTS version |
Promotional release date |
Critical patches only |
EOL |
|---|---|---|---|
|
v2020.3.LTS |
4th November 2020 |
4th March 2022 |
16th November 2022 |
|
v2020.2.LTS |
1st July 2020 |
27th October 2021 |
13th July 2022 |
|
v2020.1.LTS |
26th February 2020 |
23rd June 2021 |
16th February 2022 |
2019 LTS Versions Lifecycle
LTS version |
Promotional release date |
Critical patches only |
EOL |
|---|---|---|---|
|
v2019.3.LTS |
6th November 2019 |
10th March 2021 |
17th November 2021 |
|
v2019.2.LTS |
3rd July 2019 |
7th October 2020 |
14th July 2021 |
|
v2019.1.LTS |
27th February 2019 |
24th June 2020 |
17th February 2021 |
2018 LTS Versions Lifecycle
LTS version |
Actual release date |
Critical patches only |
EOL |
|---|---|---|---|
|
v2018.2.LTS |
3rd Oct 2018 |
29th Jan 2020 |
7th Oct 2020 |
|
v2018.2.preview1 |
1st Aug 2018 |
N/A |
1st Nov 2018 |
|
v2018.1.LTS |
6th Jun 2018 |
9th Oct 2019 |
3rd Jun 2020 |
Long Term Support FAQ
What is the LTS version naming convention?
LTS release naming will follow the following convention - vYYYY.X.LTS
- YYYY is the year the version was released
- X is an incremental number starting at 1 each year
- LTS is a suffix to identify these versions
How do I move to Long Term Support (LTS) versions?
Via the usual upgrade process. Simply choose the LTS version you want to use and pass that in the <script> tag.
Eg: <script src="https://items-va.learnosity.com?v2020.1.LTS"></script>
For Data API, pass it in the URL of the endpoint you wish to send a request to.
Eg: https://data-va.learnosity.com/v2020.1.LTS/itembank/items
Can I still access the latest API (non-LTS) releases and product features?
Latest releases will still be available every three weeks, but these will contain in-development, less stable features, while we’ll be spending more time communicating the significant changes every four months rather than a three-weekly deluge.
To access the latest release for any API, simply pass latest as the version in the script tag.
Eg: <script src="https://items-va.learnosity.com?latest"></script>
For the Data API only, pass v1 in the URL of the endpoint you wish to send a request to.
Eg: https://data-va.learnosity.com/v1/itembank/items
When can I move to Long Term Support (LTS) versions?
For any core API, when upgrading, you will need to use the new LTS naming convention.
How do the support arrangements differ between legacy versions and Long Term Support?
Legacy (pre-June 2018) API versions are currently supported for critical or security issues. We always recommended upgrading as often as practical, but contact Learnosity support if you have any questions.