Hi, Thanks for sharing you opinions. Let's try this.
I'll start a vote for this like we did for Java and Go. Thanks, -- kou In <20250313.114905.1826865576440968529....@clear-code.com> "[DISCUSS] Split C# release process" on Thu, 13 Mar 2025 11:49:05 +0900 (JST), Sutou Kouhei <k...@clear-code.com> wrote: > Hi, > > This is a similar discussion to the "[DISCUSS] Split Go > release process" thread[1], the "[DISCUSS] Split Java > release process" thread[2] and the "[DISCUSS] Split R release > process" thread[3]: > > [1] https://lists.apache.org/thread/fstyfvzczntt9mpnd4f0b39lzb8cxlyf > [2] https://lists.apache.org/thread/b99wp2f3rjhy09sx7jqvrfqjkqn9lnyy > [3] https://lists.apache.org/thread/6xl7zzf9y71dpjv5dvmn3fcm7rppggzx > > We've split Go and Java and they were released from > separated repositories. We don't split R for now. > > Let's discuss the next target. > > I propose C# as the next candidate because: > > * It seems that we don't need to update major version > frequency > * This is the main reason. Release process for > apache/arrow will not be simplified so much. > * It's a native implementation not bindings > * We may add bindings of C++'s dataset[4] > * C# release process is simple and already automated > 1. Build .nuget/.snuget on GitHub Actions > (Built .nuget/.snuget are uploaded to GitHub release > automatically) > 2. Sign built .nuget/.snuget and upload them to GitHub release > 3. Vote > 4. Download voted .nuget/.snuget and push them > * I think that Curt can act as a release manager > (and we (at least I) can help) > > [4] https://lists.apache.org/thread/5jfk0fcqy90cl8w6v45ny50pwrgfpp1y > > > What do you think about this? > > > Thanks, > -- > kou
