Locking the email editor during AJO releases/updates

We often run into all kind of problems with the email designer during a AJO upgrade/release. Created content disappears, variable settings used in fragments changes/disappears, Image sizes changes etc etc. All this things come back from the users as bug reports. When investigating the issues, we often need to conclude that the error/experienced behavior most come from hickup in the code during the code upgrade. Suddenly all is back to normal again, the day after, without changing anything. 

Out theory is that a AJO upgrade/code change possible has some impacted on the use of the email designer during the code upgrade. Maybe it is hard or difficult to store things at the same time the source code is been updated. At least we experience that it might be a challenge here.   

We would therefor like to have the option to “lock” the email editor and other components that creates things in AJO during an update . The lock could explain that this feature is temporary locked caused by an code upgrade that will take xxxxx minutes/hours. That would probably cause less frustration and reduced feedback about strange behavior reported as a bug. 

It might also be other parts of the platform that suffers the same, like creation of audiences and offers.