|
Version name |
Version code |
Release date |
Frequent updates |
Full fixes support |
Long-term fixes support |
Discontinued fixes support |
|---|---|---|---|---|---|---|
|
j5 30 |
30 |
Dec 2022 |
Y |
- |
- |
- |
|
j5 2019 |
28.0 |
Dec 2019 |
- |
- |
Y |
Dec 2023 1, 2 |
|
j5 2018 |
26.0 |
Oct 2018 |
- |
- |
Y |
Oct 2023 |
|
j5 2017.2 |
25.0 |
Nov 2017 |
- |
- |
- |
Nov 2021 |
|
j5 2017 |
24.0 |
Jun 2017 |
- |
- |
- |
Jun 2021 |
|
j5 2016.2 |
23.0 |
Nov 2016 |
- |
- |
- |
Nov 2020 |
|
j5 2016 |
22.0 |
Jun 2016 |
- |
- |
- |
Jul 2020 |
|
j5 2015.2 |
21.0 |
Oct 2015 |
- |
- |
- |
Oct 2019 |
|
j5 2015 |
20.0 |
Jan 2015 |
- |
- |
- |
Jan 2019 |
|
j5 1.16 (and prior) |
May 2014 |
- |
- |
- |
May 2018 |
Frequent update cycle
1 j5 30 is updated on a frequent update cycle. This means that fixes and feature enhancements are included in our regular and frequent updates.
We recommend that you adopt the most recent update for any solution on a frequent update cycle. This ensures that you are getting the most from the solution in terms of value-added features, performance, and fixes for any security vulnerabilities and other defects.
Solutions for issues logged with Hexagon that result in bug reports (that we agree
to resolve) will be provided in a future update.
2 j5 2019 (version 28.0) won't receive new features after j5 version 30 is released. However, j5 2019 will continue to receive regular fixes for critical defects, critical security vulnerabilities, and high-priority customer-reported defects until December 2023. All other items requested during this period will need special motivation. After December 2023, only critical defects will be considered in exceptional circumstances.