|
|
|
|
|
by buchanmilne
1798 days ago
|
|
> Is there another level of patches below point releases for backported security patches No, because its unecessary (in my experience) > or are your options to upgrade to something that adds new features and may be backwards incompatible It won't be backwards incompatible, otherwise they would leave the change for a new minor release. Why would you not want a new feature (e.g. the new "clone plugin") if it gives you value now without any migration required (because of incompatibilities that may arise if all new features are left for minor versions which are reserved for incompatibilities)? |
|
Assuming that is true, this sounds like a normalcy bias to me (https://en.wikipedia.org/wiki/Normalcy_bias).
> Why would you not want a new feature (e.g. the new "clone plugin")
Because features can introduce bugs or performance regressions. Sure you can say that's rare, but I still might not want to take that risk with some of the most critical infrastructure in my app.