System Upgrade - Best practice for fixes post Upgrade Plan on sub-prod instance(s)

[TerrenC]

Hello,

I had a question regarding the best practice for a specific scenario during a system upgrade. We have 3 instances - DEV, TEST, PROD - and we will be using the Upgrade Plan to implement our upgrade. We have some time scheduled between DEV and TEST upgrade in order to resolve skipped records, make fixes, etc. in DEV before moving to TEST. In this scenario, we have published the Upgrade Plan from DEV and upgraded TEST using that Upgrade Plan, but found some bugs on TEST that were, for some reason (lack of verification, etc.), not found on DEV. In this case, we would like to go back to DEV, make necessary changes, then move and verify those changes on TEST.

What would be the best way to go about this? Are these changes captured by the Upgrade Plan if it is refreshed on DEV? If so, is there any way to verify that on TEST before upgrading PROD? If not, should the fixes be captured in Update Sets and moved that way?

Any advice is appreciated, thanks!

[Mark Manders]

If your upgrade plan is already moved to test, just fix it in an update set (or several and batch them together) and move the fixes like that.