Ashrem
Oh Wise One
The earlier in the process it gets to them, the more likely it is that they can make changes without interrupting their next sprint. The information was available on Beta, and people had an opportunity to comment there before it went live here. In beta, it's a question of them deciding to proceed, cancel, or delay and rework. Here, it's a question of rolling back.
also here, they have to work with the knowledge that the majority of the people who are going to throw up their hands and walk away because of this issue will have already done so before their next chance to deploy and test new code. They aren't going to get those people back, so they have less incentive to change it.
also here, they have to work with the knowledge that the majority of the people who are going to throw up their hands and walk away because of this issue will have already done so before their next chance to deploy and test new code. They aren't going to get those people back, so they have less incentive to change it.