Our organization is in the process of developing our release management strategy, which is an interesting new paradigm given the inability to branch code so-to-speak. We are planning a very standard movement of solutions from a DEV online instance to a QA online instance for UAT and then to PROD. The challenge occurs when during UAT an issue is found on -- say -- day 3 of UAT and during days 1 and 2 changes have been ongoing in DEV. Now you have to decide to either go forward with the release with the known issue so the other work items can be released, or pull the whole thing back. But then how do you get back to the state the environment was in when you exported it the first time?
I'm interested in hearing how others are managing their releases and whether the Microsoft backup/restore feature through the portal is being utilized in the process?
Thank you!