gabotechs commented on issue #16622: URL: https://github.com/apache/datafusion/issues/16622#issuecomment-5775377265
Giving my two cents: I can imagine how there's a subset of people that are fine with long-term LTS branches, because their system might not need a heavy use of new additions to the public API, their DataFusion-based systems might be on maintenance mode, or something similar. However, the public API of DataFusion is wide, and all the breaking changes introduced to it in the last year seem legitimate and valuable, something that "heavy" DataFusion users will likely want to benefit sooner rather than later. Even if I see the value in LTS releases, I'd be fine with just not having them if that allows the project to move measurably faster. My impression is that DataFusion's public API is not mature enough to easily afford LTS releases without a big impact on development speed, which is something that could be steered with some discipline in public API design, and revisited in the future. If breaking changes are properly documented in an upgrade guide (which is the case today), typically just throwing an LLM to it easily one-shot a full upgrade, so (at least IME) frequent breaking changes are not that bad. -- 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]
