alamb opened a new issue, #63: URL: https://github.com/apache/arrow-rs-object-store/issues/63
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** We are now being careful about breaking changes (see https://github.com/apache/arrow-rs/blob/master/CONTRIBUTING.md#breaking-changes) This means we can't merger PRs with breaking API changes to `main` until early August However there are now three potentially large parquet changes that could conflict with each other and have API changes: * https://github.com/apache/arrow-rs/pull/5486 from @etseidl * https://github.com/apache/arrow-rs/pull/5933 from @progval * https://github.com/apache/arrow-rs/pull/6000 from @adriangb **Describe the solution you'd like** Some way to avoid a massive set of merge conflicts when we start merging changes to `master` for parquet 53 I would also love to be able to review and merge smaller PRs rather than keep several large ones outstanding **Describe alternatives you've considered** I would like to propose we create a feature branch (e.g. `parquet-53.0.0`) in the arrow-rs repo that we can merge parquet API changes to and develop new features Once main opens for 53 (in early August) we can merge the branch to main This approach does require maintenance of the parquet 53 branch and runs the risk of accumulating merge conflicts as it diverges from master. I am willing to help do the proces **Additional context** <!-- Add any other context or screenshots about the feature request here. --> -- 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...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
