j5 Product end-of-life policy - j5 - 28.0 - Reference - Hexagon

j5 Hardware and Software Requirements

Language
English
Product
j5
Search by Category
Reference
j5 Version
2019

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

-

-

-

Dec 2023

j5 2018

26.0

Oct 2018

-

-

-

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

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.

Compatibility with j5 Mobile

j5 Mobile is compatible with j5 Server v30 and 28.0, and j5 Framework 26.0. Unfortunately, this compatibility limits the functional, performance, and security enhancements available to j5 Mobile, and so a compatibility end date must be set.

Compatibility testing for j5 Mobile updates will stop for:

  • j5 Framework 26.0, and j5 Server 28.0 update 39 and earlier, after j5 v30 update 14 (May 2024).

  • j5 Server 28.0 update 40 after December 2024.

All customers must take one of the following actions by then, to either:

  1. Upgrade to j5 Server v30, or

  2. Turn off automatic app updates on mobile devices used for j5 Mobile.

Failure to do so will result in j5 Mobile not operating correctly at some point, without warning.

This is particularly important for customers using iOS devices because apps can't be downgraded or side loaded. If an iOS device upgrades to a version of j5 Mobile that is incompatible with the j5 Server / Framework version being used, the only recovery route is to upgrade to j5 Server v30, which may not be achievable in a short time frame.