reply below. We're moving into a world where we will likely more frequently modify the > mainline branch with new functionality to integrate with ecosystem changes > (sidecar, analytics, drivers?). It's probably at least worth a conversation > as to whether our current policy (improvements and new features main branch > only) is optimal across everything equally or if there should be nuance for > ecosystem integrations. >
This also incentivises intentionally not introducing support for that api in older mainlines. We KISS, if the user wants that ecosystem benefit they need to upgrade to at least mainline X. Once older mainlines have it then we have this problem. An alternative to the risk of having to always update all the mainlines, is to let the ecosystem branch to provide support for the different mainlines as/when needed. Both are painful.
