To elaborate a little on this, we ran into issues that could not be foreseen late in the deployment procedure. Due to that we only had about half an hour to try and resolve the situation or cancel publishing the patch. That's the reason we had a full downtime without actually deploying.
However since we have now run pretty much all the procedures and tests we need to run for a patch deployment, we can deploy it very soon, and then we don't need as long a downtime.
Also, the issues encountered were not with the patch or code itself, but rather with our distribution mechanics for the patches. That's being worked on now and will hopefully be resolved later today or tomorrow.
Прикол в том что ща им надо было 5 часов и они не смогли но вот в следующий раз уже надо будет не 5 а меньше ... я чет не догоняю, их там, как обычно, просветлило? И теперь то они "точно знают все о сервере"?
