Release Update Studio

Overview

The Release Update Studio allows customers to be truly evergreen, take advantage IFS’s constant innovation and get fast access to new technology. The studio is designed to ensure customers and partners experience a repeatable and predicable process during the Release Update – from analyzing changes, through to applying the updates.

Taking a Release Update to a Build Place With Customizations

If there are additional files other than the mandatory files existing in the customer solution repository of the release-update branch, your Build Place will be categorized as a "Build Place With Customizations"*. These Build Places are used by customers who are implementing customizations or configurations within their Build Place. Hence, they will be taken through the full flow of the Release Update process.

Note

• Mandatory files are version.txt, solutionset.yaml, and translationusage.json.

Such customers can follow the Taking a Release Update to a Build Place With Customizations section of the documentation.

Taking a Release Update to a Build Place Without Customizations (Applicable for 22R2 and Beyond)

If the customer solution repository of the release-update branch consists of only the mandatory files, your Build Place will be categorized as a "Build Place Without Customizations". These Build Places are used by customers who are not implementing any customizations or configurations within their Build Place. Hence, they will be taken through the shorter path of the Release Update process. Note that this is only applicable for core-cust separated Build Places (i.e. Release Update version you are planning to take is 22R2 or higher).

Such customers can follow the Taking a Release Update to a Build Place Without Customizations section of the documentation.