alamb commented on PR #16397: URL: https://github.com/apache/datafusion/pull/16397#issuecomment-2971466770
> Relevant question to this text and the project is what the project's stance is wrt API stability? Merging fast means you're likely to ship something a little bit too quickly every now and then. I'm not saying it's a bad strategy, just wondering how you balance the tension between stability and velocity. I would say we "try not to do API churn but it happens every release". Indeed it has come up as a challenge for downstream users, though I would say it has been less of a challenge the last 6 months or so. There is more detail here - https://github.com/apache/datafusion/issues/13525 The policy is documented here: https://datafusion.apache.org/contributor-guide/api-health.html You can get a sense of the kinds of changes required by looking at https://datafusion.apache.org/library-user-guide/upgrading.html Basically at some point I expect users of DataFusion will care enough about non breaking releases that they will want to contribute to helping make some release vehicle that has stable APIs (e.g. backport stuff to a LTS release for example) But until that happens we just keep cranking on the code and change APIs every month -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
