ML Updates - Implementation timelines ? Update from Pega 7.1.5 to 7.1.8
1) We are seeing an ML update every 3 months, and it's hard to keep the Pega version current considering the implementation timelines. Does any one has insight into the actual implementation timelines for an ML Update? We are currently planning to update from Pega 7.1.5 to 7.1.8.
2) For a major version upgrade, it is recommended to Skim the code base to a major version. Is skimming required for the minor version upgrades/updates?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
ML to ML updates are light weight and if the application is fully compliant to Pega 7 and HTML5/CSS3 standards then the impact is said to be none or minimal.
The skimming for ML to ML updates is not mandatory, if the versions have become too many / heavy from the project or implementation standpoint them they can be skimmed while considering the ML to ML update.
You can read through the release notes of the ML which you are planning for update to understand better and also foresee the level of impact at a high level.
Pega 7.1.9 is a new distribution kit that contains all cumulative fixes and enhancements since Pega 7.1.0. Therefore, unless you've received a hotfix that was made after 7.1.9, you do not need to re-install the hotfixes. The Pega 71.9 Update Guide includes information about rolling back an update. See the Pega 71.9 Update Guide on the PDN at Support > Deployments & Updates > Deployment Guides.
The update from 7.1.5 to 7.18 is lightweight and a smooth process as said by Chaitra. We could finish this in 2 days.
However, we are seeing UI related issues (missing vertical scroll bars, button layouts and alignments) after the update and these may be because of the Custom Skins we have in the application. I will keep this thread posted after the analysis of issues.