+1 (binding)

> On 2025. May 8., at 7:53, Sutou Kouhei <k...@clear-code.com> wrote:
> 
> +1 (binding)
> 
> In <CAD1Rbrrd6m=TfcUoYo8Bvu4_cJ4SscR6Voe4snBLvBk-08MP=w...@mail.gmail.com>
>  "[VOTE] Split JS implementation and Release Process" on Wed, 7 May 2025 
> 10:48:40 +0200,
>  Raúl Cumplido <rau...@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

Reply via email to