Re: [ANNOUNCE] New Arrow PMC member: Jacob Wujciak

2025-03-16 Thread David Li
Congrats Jacob! On Mon, Mar 17, 2025, at 14:39, Ruoxi Sun wrote: > Congratulations Jacob! > > *Regards,* > *Rossi SUN* > > > On Mon, Mar 17, 2025 at 1:26 PM Gang Wu wrote: > >> Congrats Jacob! >> >> On Mon, Mar 17, 2025 at 1:23 PM Sutou Kouhei wrote: >> >> > The Project Management Committee (PMC

[ANNOUNCE] New Arrow PMC member: Jacob Wujciak

2025-03-16 Thread Sutou Kouhei
The Project Management Committee (PMC) for Apache Arrow has invited Jacob Wujciak to become a PMC member and we are pleased to announce that Jacob Wujciak has accepted. Congratulations and welcome!

Re: [ANNOUNCE] New Arrow PMC member: Jacob Wujciak

2025-03-16 Thread Gang Wu
Congrats Jacob! On Mon, Mar 17, 2025 at 1:23 PM Sutou Kouhei wrote: > The Project Management Committee (PMC) for Apache Arrow has invited > Jacob Wujciak to become a PMC member and we are pleased to announce > that Jacob Wujciak has accepted. > > Congratulations and welcome! > > >

Re: [VOTE] Split C# release process

2025-03-16 Thread Curt Hagenlocher
+1 On Sun, Mar 16, 2025 at 6:22 PM Sutou Kouhei wrote: > +1 > > In <20250317.101329.2226182884160584389@clear-code.com> > "[VOTE] Split C# release process" on Mon, 17 Mar 2025 10:13:29 +0900 > (JST), > Sutou Kouhei wrote: > > > Hi, > > > > I would like to propose splitting C# release pr

Re: [VOTE] Split C# release process

2025-03-16 Thread Sutou Kouhei
+1 In <20250317.101329.2226182884160584389@clear-code.com> "[VOTE] Split C# release process" on Mon, 17 Mar 2025 10:13:29 +0900 (JST), Sutou Kouhei wrote: > Hi, > > I would like to propose splitting C# release process. > > Motivation: > > * We want to reduce needless major releases be

[VOTE] Split C# release process

2025-03-16 Thread Sutou Kouhei
Hi, I would like to propose splitting C# release process. Motivation: * We want to reduce needless major releases because major releases require users' change Approach: 1. Extract csharp/ in apache/arrow to apache/arrow-csharp like apache/arrow-go * Filter csharp/ related commits from

Re: [DISCUSS] Split C# release process

2025-03-16 Thread Sutou Kouhei
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 wrote: > Hi

[ANNOUNCE] Apache Arrow Go v18.2.0 Released

2025-03-16 Thread Matt Topol
The Apache Arrow community is pleased to announce a new release of the Apache Arrow Go libraries. It includes 21 commits from 7 distinct contributors, and contains libraries for Arrow, Flight, FlightSQL, and Parquet versioned at 'v18.2.0'. The release is available now from [1]. Release notes are

Re: [VOTE][RESULT][Go] Release Apache Arrow Go 18.2.0 RC1

2025-03-16 Thread Matt Topol
The vote passes with: 5 +1 binding votes (Raul, Kou, David, Dewey, Bryce) 1 +1 non-binding vote (Saurabh) Thank you everyone! I'm gonna do the release tasks now. --Matt On Thu, Mar 13, 2025 at 2:17 PM Dewey Dunnington wrote: > +1! (binding) > > I ran dev/release/verify_rc.sh 18.2.0 1 on MaOS

Re: [DISCUSS] Do we want to enable GitHub Discussions for apache/arrow?

2025-03-16 Thread Jacob Wujciak
I have opened a PR that will enable discussions: https://github.com/apache/arrow/pull/45811 Am So., 16. März 2025 um 15:22 Uhr schrieb Antoine Pitrou : > > > We can start with users@ and, if the experience is subpar, switch to > something else. > > Regards > > Antoine. > > > Le 16/03/2025 à 15:04,

Re: [DISCUSS] Do we want to enable GitHub Discussions for apache/arrow?

2025-03-16 Thread Antoine Pitrou
We can start with users@ and, if the experience is subpar, switch to something else. Regards Antoine. Le 16/03/2025 à 15:04, Weston Pace a écrit : +1 A possible reason for hesitation is that it provides us yet another stream that requires maintainer attention I had been lukewarm on di

Re: [DISCUSS] Do we want to enable GitHub Discussions for apache/arrow?

2025-03-16 Thread Weston Pace
+1 > A possible reason for hesitation is that it provides us yet another stream that requires maintainer attention I had been lukewarm on discussions in the past partly because of this and partly because they cannot be "closed" and grow forever. However, I have since learned that the latter conc