In order to balance the needs for support of existing software versions against the demand for new functionality delivered in new releases, Infogix employs a phased product lifecycle policy by which older versions and functions are retired as new versions are released. Customers are encouraged to upgrade their software regularly so that they receive the most current feature set and all stability improvements. The following policies will help you to manage software versions optimally.
Support life policy
Having the current software version implemented allows you to take advantage of any new nodes available as well as the additional functionality offered with the latest core product.
Customers with an active Support Agreement are entitled to software version upgrades as well as interim node updates. Customers on the current release and the prior release will be provided support. This allows customers to coordinate upgrades in conjunction with their strategic initiatives.
The following table outlines the support status of the LAE product:
|Version||Support status||End of support date*|
|6||End of support||December 2019|
|5||End of support||October 2016|
|4||End of support||N/A|
* Tickets can be made for versions in the End of Support Phase; however, Infogix will
no longer provide new fixes to the software.
Functionality deprecation policy
As older implementations of functionality are replaced with improved versions, or some functionality is removed from the software, Infogix employs a deprecation mechanism to provide our customers with advanced notification of the forthcoming changes so they may plan accordingly. Deprecation is not itself the removal or replacement of functionality, but rather the signal that this use of the deprecated functionality should be limited and optimally transitioned to the newer alternative. Typically the deprecated functionality will no longer be available starting with the next major version of the software.
Library deprecation notification
In version 6.1 of the software, the basic.brg and simple.brg libraries were deprecated. Though they will continue to function, they will not be available in the next major version of the software. Customers should replace any nodes from this library with the equivalent nodes from the core.brg library.