Hi Kou,
Le 18/07/2024 à 11:33, Sutou Kouhei a écrit :
Here is my idea how to proceed this:
1. Extract go/ in apache/arrow to apache/arrow-go like
apache/arrow-rs
* Filter go/ related commits from apache/arrow and create
apache/arrow-go with them like we did for apache/arrow-rs
* Remove go/ related codes from apache/arrow
2. Prepare integration test CI like apache/arrow-rs does:
https://github.com/apache/arrow-rs/blob/master/.github/workflows/integration.yml
3. Prepare release script based on apache/arrow-julia,
apache/arrow-adbc and/or apache/arrow-flight-sql-postgresql
I think this is a good idea, but I'm not part of the Go maintainers.
Cons of this idea:
* This is a backward incompatible change
* Users need to change their "import" to
"github.com/apache/arrow-go/arrow" from
"github.com/apache/arrow/go/arrow"
Is there no way to leave some kind of alias or redirection in the
apache/arrow repository?
Regards
Antoine.
