comphead commented on issue #16622: URL: https://github.com/apache/datafusion/issues/16622#issuecomment-3151457662
Thanks @findepi This depends on the needs IMO. In Comet we used to refer to a specific tag or commit in main branch to test upcoming features, test our contributions, breaking changes etc. For frequent releases currently I can see a drawback related to not sufficient feedback on the release candidate. DF has a verification script which provides limited forecast on release adoption on the customer side. Frequent releases are definitely more useful in terms of: - broadcasting the code - changes documentation - final code state However to make it happen we need to solve some other tasks, namely get more feedback: - Increase fuzz testing. Comet is good for that, thanks @andygrove and Comet sometimes can capture in DF new releases. - Planner and other performance tests - Automatic Upgrade Guide -- 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
