You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Raúl Cumplido <ra...@apache.org> on 2025/05/12 08:28:06 UTC
[RESULT][Vote] Split JS implementation and Release Process
Hi,
The vote passes with 8 binding +1 votes and 1 +1 non-binding vote. No 0 or
-1 votes. Thanks all!
Binding votes:
- Antoine Pitrou
- David Li
- Neal Richardson
- Jacob Wujciak
- Bryce Mecum
- Sutou Kouhei
- Krisztián Szücs
- Raúl Cumplido
Non-binding votes:
- Brian Hulette
Thanks,
Raúl
El jue, 8 may 2025 a las 12:30, Raúl Cumplido (<ra...@apache.org>)
escribió:
> +1 (binding)
>
> El jue, 8 may 2025 a las 11:46, Krisztián Szűcs (<
> szucs.krisztian@gmail.com>) escribió:
>
>> +1 (binding)
>>
>> > On 2025. May 8., at 7:53, Sutou Kouhei <ko...@clear-code.com> wrote:
>> >
>> > +1 (binding)
>> >
>> > In <CA...@mail.gmail.com>
>> > "[VOTE] Split JS implementation and Release Process" on Wed, 7 May
>> 2025 10:48:40 +0200,
>> > Raúl Cumplido <ra...@apache.org> wrote:
>> >
>> >> Hi,
>> >>
>> >> I would like to propose splitting the JS implementation and the
>> >> corresponding release process to its own repository.
>> >>
>> >> Motivation:
>> >>
>> >> * We want to reduce needless major releases to avoid unnecessary user
>> >> burden.
>> >> * We want to avoid needless release tasks when releasing apache/arrow
>> if it
>> >> is not necessary.
>> >>
>> >> Approach:
>> >>
>> >> 1. Extract js/ in apache/arrow to apache/arrow-js like we did for
>> >> apache/arrow-go
>> >> * Filter js/ related commits from apache/arrow and create
>> >> apache/arrow-js with them like we did for apache/arrow-go
>> >> * Remove js/ related codes from apache/arrow
>> >> 2. Prepare integration test CI like apache/arrow-go does:
>> >>
>> https://github.com/apache/arrow-go/blob/21de5d0b84289a0d37974fa6bd0852407d2c0d00/.github/workflows/test.yml#L347-L402
>> >> 3. Prepare release scripts based on apache/arrow-go and
>> apache/arrow-java.
>> >>
>> >> New release process:
>> >>
>> >> * apache/arrow-js will be released separated from apache/arrow
>> >> * JS committers will ask for a new Release as apache/arrow-julia
>> committers
>> >> do today: https://github.com/apache/arrow-julia/pull/530. There are
>> some
>> >> PMC members who will help with the apache/arrow-js release tasks as we
>> do
>> >> for apache/arrow-julia today
>> >> * apache/arrow releases a new major version every 3 months but
>> >> apache/arrow-js will use a more appropriate major release cycle based
>> on
>> >> their needs
>> >> * apache/arrow-js can use more minor/patch releases than apache/arrow
>> >>
>> >> See also the discussion of this:
>> >> https://lists.apache.org/thread/qpjt8ypmw1h8j1445kmn8s7wqml0cwoy
>> >>
>> >>
>> >> The vote will be open for at least 72 hours.
>> >>
>> >> [ ] +1 Accept this proposal
>> >> [ ] +0
>> >> [ ] -1 Do not accept this proposal because...
>> >>
>> >>
>> >> Thanks,
>> >> Raúl
>>
>>
Re: [RESULT][Vote] Split JS implementation and Release Process
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
I've created apache/arrow-js: https://github.com/apache/arrow-js
I opened a new issue that imports commits from apache/arrow:
https://github.com/apache/arrow-js/issues/1
If anyone can help this, please open issues on
apache/arrow-js and apache/arrow and work on them.
Thanks,
--
kou
In <CA...@mail.gmail.com>
"[RESULT][Vote] Split JS implementation and Release Process" on Mon, 12 May 2025 10:28:06 +0200,
Raúl Cumplido <ra...@apache.org> wrote:
> Hi,
>
> The vote passes with 8 binding +1 votes and 1 +1 non-binding vote. No 0 or
> -1 votes. Thanks all!
>
> Binding votes:
> - Antoine Pitrou
> - David Li
> - Neal Richardson
> - Jacob Wujciak
> - Bryce Mecum
> - Sutou Kouhei
> - Krisztián Szücs
> - Raúl Cumplido
>
> Non-binding votes:
> - Brian Hulette
>
> Thanks,
> Raúl
>
> El jue, 8 may 2025 a las 12:30, Raúl Cumplido (<ra...@apache.org>)
> escribió:
>
>> +1 (binding)
>>
>> El jue, 8 may 2025 a las 11:46, Krisztián Szűcs (<
>> szucs.krisztian@gmail.com>) escribió:
>>
>>> +1 (binding)
>>>
>>> > On 2025. May 8., at 7:53, Sutou Kouhei <ko...@clear-code.com> wrote:
>>> >
>>> > +1 (binding)
>>> >
>>> > In <CA...@mail.gmail.com>
>>> > "[VOTE] Split JS implementation and Release Process" on Wed, 7 May
>>> 2025 10:48:40 +0200,
>>> > Raúl Cumplido <ra...@apache.org> wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> I would like to propose splitting the JS implementation and the
>>> >> corresponding release process to its own repository.
>>> >>
>>> >> Motivation:
>>> >>
>>> >> * We want to reduce needless major releases to avoid unnecessary user
>>> >> burden.
>>> >> * We want to avoid needless release tasks when releasing apache/arrow
>>> if it
>>> >> is not necessary.
>>> >>
>>> >> Approach:
>>> >>
>>> >> 1. Extract js/ in apache/arrow to apache/arrow-js like we did for
>>> >> apache/arrow-go
>>> >> * Filter js/ related commits from apache/arrow and create
>>> >> apache/arrow-js with them like we did for apache/arrow-go
>>> >> * Remove js/ related codes from apache/arrow
>>> >> 2. Prepare integration test CI like apache/arrow-go does:
>>> >>
>>> https://github.com/apache/arrow-go/blob/21de5d0b84289a0d37974fa6bd0852407d2c0d00/.github/workflows/test.yml#L347-L402
>>> >> 3. Prepare release scripts based on apache/arrow-go and
>>> apache/arrow-java.
>>> >>
>>> >> New release process:
>>> >>
>>> >> * apache/arrow-js will be released separated from apache/arrow
>>> >> * JS committers will ask for a new Release as apache/arrow-julia
>>> committers
>>> >> do today: https://github.com/apache/arrow-julia/pull/530. There are
>>> some
>>> >> PMC members who will help with the apache/arrow-js release tasks as we
>>> do
>>> >> for apache/arrow-julia today
>>> >> * apache/arrow releases a new major version every 3 months but
>>> >> apache/arrow-js will use a more appropriate major release cycle based
>>> on
>>> >> their needs
>>> >> * apache/arrow-js can use more minor/patch releases than apache/arrow
>>> >>
>>> >> See also the discussion of this:
>>> >> https://lists.apache.org/thread/qpjt8ypmw1h8j1445kmn8s7wqml0cwoy
>>> >>
>>> >>
>>> >> The vote will be open for at least 72 hours.
>>> >>
>>> >> [ ] +1 Accept this proposal
>>> >> [ ] +0
>>> >> [ ] -1 Do not accept this proposal because...
>>> >>
>>> >>
>>> >> Thanks,
>>> >> Raúl
>>>
>>>