andygrove commented on issue #16622: URL: https://github.com/apache/datafusion/issues/16622#issuecomment-3019338793
I favor option 2 (as already pointed out in the original issue). I don't think that we should artificially slow down development against the `main` branch. We already have a [documented process](https://github.com/apache/datafusion/blob/main/dev/release/README.md) for backporting PRs to release branches (e.g. `branch-48`) and creating future 48.x.x releases without breaking changes. We always release from the release branches, not the `main` branch. This is the same model that Apache Spark uses. We just haven't been proactive in backporting PRs to the release branches most of the time. The idea of holding off on merging PRs to `main` sounds like a nightmare to me. In Comet, we often temporarily point to a fixed revision of DataFusion's `main` branch so that we can gradually upgrade to the next version, testing all recently merged PRs. If breaking change PRs are all sitting in a queue until just before the next major DataFusion release, then I'm not sure how we can gradually upgrade. -- 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
