tustvold commented on PR #3191: URL: https://github.com/apache/arrow-datafusion/pull/3191#issuecomment-1219960771
> next_release I think the intention is not to have a single next_release branch, but a staging point for the features that require the upstream change. Changes that don't will continue to target master (or potentially another integration branch). IMO this just formalises the process we've effectively adopted thus far, using a dedicated branch instead of a draft PR. I therefore think this makes sense and is workable. > A possible solution is to do the reverse The downside with having git refs in master, which we used to have previously for arrow, is repos that track datafusion by git sha then have a non-trivial job tracking the correct upstream versions, and are prevented from using patch to override dependencies. It's also not clear what happens if it comes time to cut a release, but there is still a pinned git sha on master? -- 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]
