To be clear the fork needed to happen ASAP, and exchanges were looking for a solution. We knew that doing the update so quickly was not ideal, this was not something we had wanted. However, given the options and the state of the network it was the best way forward to provide stability and allow products and applications to continue functioning normally. Especially given that exchanges were looking for updates.
That's too bad anyway that you let this situation happen and eventually were in position of emergency hard fork.
You should think in advance how to improve network stability and act proactively.
We have actually been working on an update to the network for a while. This update is larger (so more time consuming), but it would have happened in a month or two.
To be clear, our network was stable for a very long time (up until 2 weeks ago). We didn't have any reason to believe that our difficulty algorithm would experience issues so suddenly.