andygrove commented on PR #3191: URL: https://github.com/apache/arrow-datafusion/pull/3191#issuecomment-1219728945
> I think as both crates have a fairly regular release cadence this is fine. The risk would be if any of these branches live longer than a couple of weeks, as then the opportunity for a potentially non-trivial, error-prone final integration increases. Agreed. I guess I am now volunteering to take on sqlparser releases on a more frequent schedule. The release process is mostly automated and there is no voting since it is outside of Apache, so this shouldn't be too much work. > FWIW I have typically just maintained draft PRs that build on each other for this purpose, and then rebased them individually to get them merged following the release. This works fine when one author is making the changes but recently there are more contributors making independent changes to sqlparser so this is harder to manage. > One thing that might be worth clarifying is how the final merge occurs, I presume we would rebase the integration branch and then do a fast forward merge? I ask as currently the only option would be a squash merge, which would lose any history from the integration branch (which may not be a problem but should be made explicit) Good points. I will address this. -- 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]
