+1 Krisztián Szűcs <szucs.kriszt...@gmail.com> schrieb am Di., 20. Mai 2025, 20:14:
> +1 > > > On 2025. May 20., at 19:55, Wes McKinney <wesmck...@gmail.com> wrote: > > > > +1 > > > > On Tue, May 20, 2025 at 1:49 AM Raúl Cumplido <rau...@apache.org> wrote: > > > >> +1 > >> > >> El mar, 20 may 2025 a las 4:14, Neal Richardson (< > >> neal.p.richard...@gmail.com>) escribió: > >> > >>> +1 > >>> > >>> On Mon, May 19, 2025 at 10:06 PM Ruoxi Sun <zanmato1...@gmail.com> > >> wrote: > >>> > >>>> +1 > >>>> > >>>> *Regards,* > >>>> *Rossi SUN* > >>>> > >>>> > >>>> On Mon, May 19, 2025 at 6:48 PM Bryce Mecum <bryceme...@gmail.com> > >>> wrote: > >>>> > >>>>> +1 > >>>>> > >>>>> On Mon, May 19, 2025 at 6:24 PM Sutou Kouhei <k...@clear-code.com> > >>> wrote: > >>>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I would like to propose splitting the Swift implementation > >>>>>> to its own repository. > >>>>>> > >>>>>> Motivation: > >>>>>> > >>>>>> * We want to make the Swift implementation Swift Package > >>>>>> Manager compatible. > >>>>>> * It requires a top-level Package.swift. > >>>>>> See also: https://www.swift.org/documentation/package-manager/ > >>>>>> > >>>>>> Approach: > >>>>>> > >>>>>> 1. Extract swift/ in apache/arrow to apache/arrow-swift like > >>>>>> we did for apache/arrow-go. > >>>>>> * Filter swift/ related commits from apache/arrow and > >>>>>> create apache/arrow-swift with them like we did for > >>>>>> apache/arrow-go. > >>>>>> * Remove swift/ related codes from apache/arrow. > >>>>>> 2. Prepare CI. > >>>>>> 3. Prepare release scripts based on apache/arrow-go and > >>>>>> apache/arrow-java. > >>>>>> > >>>>>> See also the discussion of this: > >>>>>> https://lists.apache.org/thread/dp8ovo34o3vs0tc3w0rnh8ttkqtonkzc > >>>>>> > >>>>>> [ ] +1 Accept this proposal > >>>>>> [ ] +0 > >>>>>> [ ] -1 Do not accept this proposal because... > >>>>>> > >>>>>> > >>>>>> Thanks, > >>>>>> -- > >>>>>> kou > >>>>> > >>>> > >>> > >> > >
