Upgrade Best Practices - Reverting Skipped Files

[Tyson3]

Hi,

I'm looking for some quick best practice guidance on the upgrade from Quebec to San Diego which we are currently working on. We have two sub instances ("Dev" and "Test") which we have already upgraded to San Diego. We are planning on upgrading our production instance to San Diego in July.

We are currently reviewing skipped files in our lowest instance "Dev" and are wondering about the best practice way to handle "Reverting to Base System" option. If we choose to revert a business rule for example, this change is tracked via an update set and then we can move the update set to the next sub environment "Test".  Should this update set be moved before or after we have upgrade our next instance? 

I have read some community posts with mixed signals with some saying you should move the update set to the next instance, and then upgrade.  Other ones say you should upgrade and then move the update set.   

Our assumption is the best practice is to track the skipped file in an update set first in your lowest environment and then move this update set to the next environments after it's already been upgraded.

Any clarification on this would be much helpful. Thanks!

[Terri Kouba]

Hi Cliff11,

We haven't tried applying the update set to production BEFORE the upgrade in production.  In our upgrade update set, we often have 'reverts' and 'merges' in the same update set, and the latter definitely need to be done after the upgrade because the new code this is in the merge is provided during the upgrade.

I think of it as when I'm painting a wall.  The big brush is the upgrade and allows you to apply a wide swath of changes (or paint a wide swath of a wall a new color).  The post-upgrade update set is a tiny touch-up brush that includes only a few tweaks (or a thin brush to do touch-up work on the wall).

I hope that helps.

Thanks,

Terri