+1When upgrading v21, it would give peace of mind if it was possible to downgrade shortly afterwards.
One option could be to keep the pre-upgrade repository available for e.g. a couple of weeks, allowing for an “upgrade cooling off period”.
In v20 solutions, I always keep a backup of the repository before upgrading but that’s not an option in v21.
+8Hi
in v20 with the ODX Cloud repositories there is a similar situation because there is only one ODX coupled to a project. I have used the sandbox ODX project/environment because this is ‘usually’ (there might be a difference between specific 20.10.x versions) independent from the production projects/environments.
For v21 I do not know if instances/environments are independent. I guess you could add temporary instances, promote the current state to those and then upgrade the new instances to test.This would require that not all cloud repositories are upgraded at once.
+1Hi
I think something like this could work … but it’s a bit “involved” for a lazy bastard like me 😀 … I was hoping to get built-in functionality that allowed for a switch back to the prior project repository and v21 version … and just for a few weeks after upgrading as I understand we can’t store backups for everyone forever in the TX cloud.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
