alamb commented on issue #16622: URL: https://github.com/apache/datafusion/issues/16622#issuecomment-5655575969
> [@alamb](https://github.com/alamb) High-level, an LTS in some form could definitely make sense. Coming from the more traditional database world, the fact that we have thus far gotten away with shipping API-breaking releases every 6-8 weeks is a little surprising 😅 Indeed! > 1. Six months is a pretty short support duration for an LTS release. Is that long enough that it will sufficiently ease downstream pain? I think it would ease downstream pain compared to 1.5 months we have now 😅 -- but for sure the longer we supported releases the easier it would be for downstream projects to sync. > 3. What should the criteria be for backporting changes to the LTS branch? I would initially propose a pretty lenient policy (basically anything that doesn't have API changes and is not deemed "too risky" by maintainers). For example, we probably wouldn't backport refactors or major new features like `AS OF` Joins. However, if we find we are introducing too many regressions we could tighten up the backport policy. > But maybe coding agents make it more feasible to do aggressive backporting? This is my thesis and I think we could try it for a while > 6. Should we consider shipping DataFusion releases less often? This is also a possibility (though I would personally suggest we go to the major/minor release model described in this issue's description as it has worked well for arrow). I think it would work just as well, but would shift the burden as it would restrict development on `main` > I typically update our internal datafusion version every 3rd or 4th release as I just don't have the bandwidth to test every single release. I'd love a LTS version for that reason if the release cycle for that was every 6-12 months. @Omega359 we have basically done this at InfluxData too (not deliberately, but this is what has sort of happened organically) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
