When a valid upstream patch breaks downstream, the right thing to do is to file a weather report including explanation why the change is required and some pointers on how to fix the potential failures. This gives a chance for downstream projects to evaluate and accept the change as well as to prepare the required patches to minimize the impact.

In this particular case the breakage was unintentional or unexpected so no weather was fired. However instead of reverting the patch, we went ahead with it because it turned out to be an "elaborated" revert and we wanted to unblock projects as soon as possible.

While the "elaborated" revert argument is valid in exceptional situations like this one, this should not be by any means the way upstream changes get pushed in downstream and therefore this grievance is filed to make sure this practice is avoided in future.