Fix Redis Drama

Can someone explain this?

Is this just Patrick just arbitrarily reverting the license change without buy-in from Redis Inc.? Or have the MBAs at Redis somehow magically “seen the light”?

If it’s the former, then what exactly is the point, other than protest?

I’m still trying to decide what to do next when I move our Redis cluster to Kubernetes, so am in a bit of a holding pattern waiting for the dust to settle on this mess.