Upgrade Process Query

[Kiran Kumar 76]

we have a scenario

we have clone down temporary instance over prod and upgraded and analysed skipped changes and captured them in updatesets.

Now looking down the next path ,we are thinking to clone down dev over temporary instance as we have already analyzed skipped updates 

Question 1 :

can we clone down dev with the temporary instance where we have made our analysis ?

or 

clone down dev again over prod upgrade it and analyse skipped changes again by looking at temporary instance

Question 2:

If we clone down dev with temporary instance what checks we need to keep in place ,will the analysed skipped updatesets copy over clone from temporary instance

Path we are looking at

Clone dev over temporary instance(latest clone of prod upgraded and analysed skipped changes)

upgrade test and move skipped changes from dev

upgrade prod and move skipped changes from test

Thanks

[merry678gar]

Hello,

Question 1:
Can we clone down dev with the temporary instance where we have made our analysis?
Yes, you can clone down dev with the temporary instance where you've performed the analysis of skipped changes. This approach ensures that the temporary instance (which has already been upgraded and analyzed) will serve as the reference for your dev environment. It will allow you to directly carry forward the skipped updates without reanalyzing them.

However, it's important to note the following considerations:

The skipped updates (from the temporary instance) must be captured in update sets and properly moved to dev.
Ensure that the dev environment doesn't conflict with the existing updates made during the upgrade analysis on the temporary instance. You'll want to ensure consistency between the environments to avoid duplicating analysis.
Question 2:
If we clone down dev with the temporary instance, what checks do we need to keep in place? Will the analyzed skipped update sets copy over from the temporary instance?

When cloning dev from the temporary instance, the following checks should be in place:

Confirm Update Set Transfer:   Hall pass login
After cloning, manually check that the update sets containing the skipped changes (
Best Regards
merry867

[Kiran Kumar 76]

Thanks @merry678gar 

The skipped updates (from the temporary instance) must be captured in update sets and properly moved to dev.
Ensure that the dev environment doesn't conflict with the existing updates made during the upgrade analysis on the temporary instance ==> I would like more explanation 

In current scenario we have captured skipped updates in updatesets and expect them to carry over to dev if we clone

when you said ensure

Ensure that the dev environment doesn't conflict with the existing updates made during the upgrade analysis on the temporary instance 

Are you referring to configurations made in dev during upgrade analysis in dev?