skipping a minor version of RAP . Is it the correct way ?
We are using Pega 7.3.1.
We have an upcoming PROD release where it includes Plan A and Plan B . Plan A is to deploy 01.10 version of the application , if successful , good , else , go for Plan B
Plan B - deploy 01.11 version of the application into PROD .
This is to reduce the risk of backout of an application ( I will just save the explanation for now ) .
My question here is -
Both Plan A and Plan B is already on Dev and QA and it is only a matter of deploying it to Prod . Meaning 01.10 and 01.11 both are on prod .
If Plan A deployment is successful on prod - is it wise to go with 01.12 app version for the next release , while 01.12 will also have the 01.10 version of rules saved again just to make the 01.11 changes not reflect .
Is this the only way to go ? or does anyone have a better way to go about this ?
If I have understood your query fine, I guess that there is a need of two colors of same application, when 01.10 is fine you would be continuing with it or else you would go with 01.11. If you are using 01.10 and want to create next version 01.12, you would have to skim all the rules from 10.10 and make further changes as there is a version (01.11) in between these which is different.
So basically in our use case, if we want updated version of each color we have to skim [If 01.12 needed of 01.10 color or if 01.13 needed of 01.11 color] the current version of that color.
I guess this is the only way we can go with if both colors of application are needed in same application context.
Hope I have not missed anything, kindly let me know if there is something.