Apologies for being late to this discussion. There is a hybrid option to consider here where we add the arrow2 code into the arrow crate as a separate module, so we release one crate containing the "old" API (which we can mark as deprecated) as well as the new API. Java did a similar thing a long time ago with "java.io" versus "java.nio" (new IO).
I agree that the versioning wouldn't be ideal, but this seems like it might be a pragmatic compromise? Thanks, Andy. On Tue, Jul 20, 2021 at 5:41 AM Andrew Lamb <al...@influxdata.com> wrote: > What I meant is that when you decide arrow2 is suitable for release to > existing arrow users, I stand ready to help you incorporate it into arrow. > > All the feedback I have heard so far from the rest of the community is that > we are ready. One might even say we are anxious to do so :) > > Andrew >
