alamb commented on issue #16622: URL: https://github.com/apache/datafusion/issues/16622#issuecomment-6531213615
> 31\. > Maybe we could try the API stability thing for a release and see how bad it would be. I am not sure we'll know if we try it > > For example, we could say that for the 4 week-6week release cycle after DataFusion 56 is released, we won't commit breaking changes to `main` and then release 56.1.x directly from main 🤔 > > > I'm wondering if we should take the 56 release as an opportunity to also 'hold' on major features for a release as it already has been pointed out in other tickets/mailing list that the # of bug fixes coming in from ai agents is overwhelming to reviewers. 56 could be a stabilization release then, and 57 could be where the community once again starts adding features and improvements. I think it is a good idea and likely what is going to happen organically (there really aren't that many features in Datafusion 56 and in theory we are going to make a release next week cc @xudong963 ) -- 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]
