Re: [DISCUSS] Versioning and releases for apache/arrow components

2024-04-08 Thread Jacob Wujciak
Thanks for the eager discussion, great to see that we are aligned on the broad strokes! In general I think that this is not something we neither need to nor want to implement from 0 to 100. Incrementally evolving and evaluating our process is key for sucsh a core change > I think C#, JS, [Java], a

[RESULT][VOTE] Bulk ingestion support for Flight SQL (vote #2)

2024-04-08 Thread David Li
The vote passes with 3 binding, 4 non-binding +1 votes. Thanks Joel! On Sat, Apr 6, 2024, at 17:56, Andrew Lamb wrote: > +1 > > On Sat, Apr 6, 2024 at 3:48 AM wish maple wrote: > >> +1 (non binding) >> >> Best, >> Xuwei Fu >> ulk ingestion support for Flight SQL >> >> David Li 于2024年4月5日周五 16:38

Re: [DISCUSS] Versioning and releases for apache/arrow components

2024-04-08 Thread Weston Pace
> Probably major versions should match between C++ and PyArrow, but I guess > we could have diverging minor and patch versions. Or at least patch > versions given that > a new minor version is usually cut for bug fixes too. I believe even this would be difficult. Stable ABIs are very finicky in C

Re: [DISCUSS] Versioning and releases for apache/arrow components

2024-04-08 Thread Alessandro Molina
On Sun, Apr 7, 2024 at 3:06 PM Andrew Lamb wrote: > > We have had separate releases / votes for Arrow Rust (and Arrow DataFusion) > and it has served us quite well. The version schemes have diverged > substantially from the monorepo (we are on version 51.0.0 in arrow-rs, for > example) and it doe