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 Long Term Support (LTS) version.
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 robust, complete, stable and should be used for:
- Platforms in production.
- Projects in development, going live before our next Long Term Support release.
Developer (non-LTS)
Every three weeks, for our APIs, we ship new code to production. This can be new features, in-development features, or bug fixes since the last 'developer' release, etc. These releases are bleeding edge, and should be used for:
- New projects in development, targeting our next Long Term Support releases (see below).
- Proof of Concept code, taking advantage of forthcoming major releases.
Release support lifecycle
Here's what you can expect from each of the release types above:
| developer | 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 sixteen-month lifespan for general security updates, performance updates and bug fixes. After that, they will only receive critical security updates, performance updates and bug fixes until their end of life date, at 24 months from the initial release.
After that, they transition into an End of Life (EOL) phase.
Figure 1: chart of the Learnosity LTS version lifecycle
Lifecycle for 2022 LTS Versions
LTS version |
Promotional release date |
Deprecation - critical patches only |
End of life |
|---|---|---|---|
|
v2022.1.LTS |
23rd February 2022 |
June 2023 |
February 2024 |
|
v2022.2.LTS |
29th June 2022 |
October 2023 |
July 2024 |
Lifecycle for 2021 LTS Versions
LTS version |
Promotional release date |
Deprecation - critical patches only |
End of life |
|---|---|---|---|
|
v2021.3.LTS |
13th October 2021 |
March 2023 |
November 2023 |
|
v2021.2.LTS |
30th June 2021 |
October 2022 |
July 2023 |
|
v2021.1.LTS |
24th February 2021 |
June 2022 |
February 2023 |
Lifecycle for 2020 LTS Versions
LTS version |
Promotional release date |
Deprecation - critical patches only |
End of life |
|---|---|---|---|
|
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 |
Long Term Support FAQ
What is the LTS version naming convention?
LTS release naming follows this convention - vYYYY.X.LTS
- YYYY is the year the version was released,
- X is an incremental number starting at 1 each year, and
- LTS is a suffix to identify these versions.
How do I select a Long Term Support (LTS) version?
Simply choose the LTS version you want to use and pass that in the <script> tag.
e.g.: <script src="https://items-va.learnosity.com?v2022.1.LTS"></script>
For Data API, pass it in the URL of the endpoint you wish to send a request to.
e.g.: https://data-va.learnosity.com/v2022.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 (compared to the more reliable LTS releases).
To access the latest release for any API, simply pass developer as the version in the script tag.
e.g.: <script src="https://items-va.learnosity.com?developer"></script>
For the Data API only, pass developer in the URL of the endpoint you wish to send a request to.
e.g.: https://data-va.learnosity.com/developer/itembank/items
How do I track the most recent Long Term Support (LTS) version?
To move forward with the most recent Long Term Support (LTS) version, pass latest-lts as the version in the script tag.
e.g.: <script src="https://items-va.learnosity.com?latest-lts"></script>
Note: this setting is intended for development and testing, not production use. When deploying to production, select a specific LTS version.
What is the LTS version structure?
Use the following examples when calling LTS versions:
| Description | Example |
|---|---|
| Template for API request URL - YYYY: four-digit year of release - X: incremental number identifying release in year - LTS: Moniker flagging long term support Note: Data API doesn't have a question mark (?) in the URL |
https://items.learnosity.com/?vYYYY.X.LTS https://authorapi.learnosity.com/?vYYYY.X.LTS https://reports.learnosity.com/?vYYYY.X.LTS https://data.learnosity.com/vYYYY.X.LTS |
| Lock to 2022.2 Long Term Supported version of APIs | https://items.learnosity.com/?v2022.2.LTS https://authorapi.learnosity.com/?v2022.2.LTS https://reports.learnosity.com/?v2022.2.LTS https://data.learnosity.com/v2022.2.LTS |
| Track the latest release available of the API | Items API Release Logs Author API Release Logs Reports API Release Logs Data API Release Logs |
For further information and frequently asked questions, you can read our Easier Versioning for Learnosity APIs Blog Article.