Better to revert than lose a community that is invested in your ecosystem that starts looking elsewhere. I congratulate the team in acknowledging and doing the right thing. As a developer myself, I know it is a painful thing to do but important to listen to the community.
Did someone not understand what went in? Might someone have offloaded their thinking to some external tool? Did people stop caring? Did someone not plan or design a feature in full? Were the timelines unrealistic? Maybe with so many reverts timelines should be revised?
Better to revert than lose a community that is invested in your ecosystem that starts looking elsewhere. I congratulate the team in acknowledging and doing the right thing. As a developer myself, I know it is a painful thing to do but important to listen to the community.
Reverts kind of suck when it's your feature getting reverted, no doubt. But for something as foundational as Postgres, the more reverts the better...
But why were they reverted?
Did someone not understand what went in? Might someone have offloaded their thinking to some external tool? Did people stop caring? Did someone not plan or design a feature in full? Were the timelines unrealistic? Maybe with so many reverts timelines should be revised?
I wonder
Well I have a document for you to read on this very question!
_Load bearing intensifies_