End-of-Life Policy for Digital.ai Release
Products reach the end of their life cycle for a number of reasons. These reasons may be due to market demands, technology innovation and development driving changes in the product, or the products simply mature over time and are replaced by functionally richer technology. While this is an established part of the overall product life cycle, Digital.ai recognizes that end-of-life milestones often prompt companies to review the way in which such end-of-support and end-of-life milestones impact the Digital.ai products or its supported platforms. With that in mind, we have set out below Digital.ai's end-of-life policy to help customers better manage their end-of-life transition and to understand the role that Digital.ai can play in helping to migrate to alternative Digital.ai products, platforms and technologies. The general policy guidelines are:
- As a general rule, Digital.ai will provide six months' notice and we would send out regular notifications to all our customers through our Digital.ai blog, product notifications and/or support newsletter.
- We would End-Of-Life support for our products, platforms and software with our new version of our product release.
- We would continue to provide support to our products, platforms and software for our earlier supported product version.
- You will need to ensure that you have a current and fully paid support contract with Digital.ai to receive notifications on end of life. Please contact your Account Manager regarding fees payable during the end-of-life period so that we can support you right through the end-of-life transition period.
| Products, Platforms and Software | Description | When? |
|---|---|---|
| Digital.ai Deploy Active/Hot-standby JVM Cluster Setup | No support for Deploy Active/Hot-standby mode | We will not support the Digital.ai Deploy Active/Hot-standby JVM Cluster Setup from the designated deprecation date, which is the 1st of May, 2024. We will support only the Digital.ai Deploy Active-Active JVM Cluster Setup, and this is specific to Digital.ai Deploy. |
| Internet Explorer 11 | No support for Internet Explorer 11 | IE 11 supported by Digital.ai Release and Deploy 10.2 and earlier IE 11 not supported by Digital.ai Release and Deploy 10.3 and later |
| Windows Server 2016 | No support for Windows Server 2016 | Windows Server 2016 supported by Digital.ai Release and Deploy 23.1 and earlier Windows Server 2016 not supported by Digital.ai Release and Deploy 23.3 and later |
| Windows Server 2012 | No support for Windows Server 2012 | Windows Server 2016 supported by Digital.ai Release and Deploy 22.2 and earlier Windows Server 2016 not supported by Digital.ai Release and Deploy 22.3 and later |
| CentOS 8 | No support for CentOS 8 | CentOS 8 supported by Digital.ai Release and Deploy 10.3 and 22.0 CentOS 8 not supported by Digital.ai Release and Deploy 22.1 and later |
| IBM JDK 11 | No support for IBM JDK 11 | IBM JDK 11 supported by Digital.ai Release and Deploy 23.1 and earlier IBM JDK 11 not supported by Digital.ai Release and Deploy 23.3 and later |
| IBM JDK 8 | No support for IBM JDK 8 | IBM JDK 8 supported by Digital.ai Release and Deploy 10.0 and earlier IBM JDK 8 not supported by Digital.ai Release and Deploy 10.1 and later |
| Oracle JDK 11 (LTS) | No support for Oracle JDK 11 (LTS) | Oracle JDK 11 (LTS) supported by Digital.ai Release and Deploy 23.3 and earlier Oracle JDK 11 (LTS) not supported by Digital.ai Release and Deploy 24.1 and later |
| Oracle JDK 8 (LTS) | No support for Oracle JDK 8 (LTS) | Oracle JDK 8 (LTS) supported by Digital.ai Release and Deploy 10.0 and earlier Oracle JDK 8 (LTS) not supported by Digital.ai Release and Deploy 10.1 and later |