Hi All,

Based on the below documentation from IFS if we implement customization during the Release update process we need to re done in the release update branch what was the IFS recommended approach for this?

One of the suggestion I got from IFS  create the PR for for the changes(topic branches) in older version to release update branch.

If any one from IFS did this approach practically please provide the pros and cons. 

------------------------------------------------------------------------------------------------------------------------------------

Important Things to Consider Before Applying a Release Update¶

It is highly recommended to minimize customizations during the release update process due to the following reasons:

• Available environment quota will be shared between both the build place and release update studio. So, ordering environments to test the customizations will reduce the environment quota available for release-update related steps.
• If customizations are done after conducting an impact assessment or an impact analysis, the analysis needs to be conducted again to identify the impact accurately.
• Changes done in the master branch needs to be re-done in the release-update branch and re-tested, cause a re-work for the users.
• If the same file is changed in both master and release-update branches, there could be conflicts in the files.