Joseph Tkach

In the future, would it be possible to communicate to your customers before rolling out potentially breaking changes like this?

Maybe send an email giving us some heads up like, "Hey, on jan 25. we are rolling out a bunch of potentially breaking changes, we understand that this has the potential to disrupt your development cycle so here is our release schedule."

When I have worked on software of this scale in the past, we always had to have disaster plan in the case of a bad deployment so that we could immediately mitigate any problems we caused. This seems to happen routinely, and it would be really helpful if we had more transparency.