Affects Version/s: 0.9.182
Fix Version/s: 0.9.183
Sometimes we want to deploy as quickly as possible, this is planned to be a change to the deploy branch. It can be reverted afterwards so we go back to the slow deploy.
i'm not completely sure i follow the intention behind this pull?
this changes the deploy process, and then we have another deploy to change it back?
now for the why <.<
( Well it will not be a revert as I will leave the intelligence in unicorn_reload )
Because I have a 30 minute window and the deploy takes above 50 minutes right now.
why can't we always deploy in under 30 minutes?
i.e. why change it back after
because there is much disruption when we do that
this is for deploys with downtime?