Re: [RESULT][VOTE] Split C# release process

2025-05-22 Thread Sutou Kouhei
kou In <20250423.161348.1822813613714377052@clear-code.com> "Re: [RESULT][VOTE] Split C# release process" on Wed, 23 Apr 2025 16:13:48 +0900 (JST), Sutou Kouhei wrote: > Hi, > > It makes sense. Let's complete the followings in > apache/arrow before we

Re: [RESULT][VOTE] Split C# release process

2025-04-23 Thread Sutou Kouhei
otnet.) >> >> For example, should we complete "GH-44800: [C#] Implement >> Flight SQL Client" >> https://github.com/apache/arrow/pull/44783 in apache/arrow? >> Or should we continue it in apache/arrow-dotnet? >> >> >> Thanks, >> -- >>

Re: [RESULT][VOTE] Split C# release process

2025-04-22 Thread Curt Hagenlocher
ache/arrow? > Or should we continue it in apache/arrow-dotnet? > > > Thanks, > -- > kou > > In <20250331.120021.2046206843285859352@clear-code.com> > "Re: [RESULT][VOTE] Split C# release process" on Mon, 31 Mar 2025 > 12:00:21 +0900 (JST), > Suto

Re: [RESULT][VOTE] Split C# release process

2025-04-22 Thread Sutou Kouhei
de.com> "Re: [RESULT][VOTE] Split C# release process" on Mon, 31 Mar 2025 12:00:21 +0900 (JST), Sutou Kouhei wrote: > Hi, > > I've created https://github.com/apache/arrow-dotnet and > opened an issue for importing commits from apache/arrow: > https://gith

Re: [RESULT][VOTE] Split C# release process

2025-03-30 Thread Sutou Kouhei
lude the C# implementation but the next release of it will not include the C# implementation. Thanks, -- kou In <20250324.143530.31638564000205432@clear-code.com> "Re: [RESULT][VOTE] Split C# release process" on Mon, 24 Mar 2025 14:35:30 +0900 (JST), Sutou Kouhei wrote: >

[RESULT][VOTE] Split C# release process

2025-03-27 Thread Sutou Kouhei
Hi, The vote carries with 5 +1 binding votes. Let's discuss the new repository name as suggested by Bryce. Should we use arrow-dotnet not arrow-csharp? FYI: The number of GitHub repositories that include "dotnet" or "csharp" in their name: * "dotnet": 164K https://github.com/search?q=dotnet&t

Re: [RESULT][VOTE] Split C# release process

2025-03-23 Thread Sutou Kouhei
Hi, Thanks for sharing your opinions. Let's use arrow-dotnet. If there are any people who want to work on this, I'll help them. Otherwise, I'll work on this like I did for apache/arrow-go and apache/arrow-java. Thanks, -- kou In "Re: [RESULT][VOTE] Split C# release pro

Re: [RESULT][VOTE] Split C# release process

2025-03-20 Thread Adam Reeve
I'd also prefer arrow-dotnet, as I think the fact it's for use on the .NET platform is the more important factor to highlight rather than the language it's written in. The majority of users will be using C# but I'm sure there are some F# users of Arrow out there. That said, I don't feel that stron

Re: [RESULT][VOTE] Split C# release process

2025-03-20 Thread Curt Hagenlocher
Yes, but can we weight each repository by the number of stars it has? :P I think arrow-dotnet is a better name, but it's a mild preference at best. On Thu, Mar 20, 2025 at 6:01 PM Sutou Kouhei wrote: > Hi, > > The vote carries with 5 +1 binding votes. > > Let's discuss the new repository name a