Hi Raúl, Thanks for starting this discussion. To be totally clear, is the proposal also to split JS into a separate repository too, or just releasing independently?
Neal On Tue, Apr 15, 2025 at 4:09 AM Raúl Cumplido <rau...@apache.org> wrote: > Hi, > > This is a similar discussion to the "[DISCUSS] Split Go release process" > thread[1], the "[DISCUSS] Split Java release process" thread[2], the > "[DISCUSS] Split R release process" thread[3] and the "[DISCUSS] Split C# > release process" thread [4]: > > [1] https://lists.apache.org/thread/fstyfvzczntt9mpnd4f0b39lzb8cxlyf > [2] https://lists.apache.org/thread/b99wp2f3rjhy09sx7jqvrfqjkqn9lnyy > [3] https://lists.apache.org/thread/6xl7zzf9y71dpjv5dvmn3fcm7rppggzx > [4] https://lists.apache.org/thread/xbtq1ndjnljyo9jpm4ozblq9wx7hrc7y > > We've split Go, Java and they were released from separated repositories. We > are in the process of splitting .NET (C#) and we decided to not split R for > now. > > We started a discussion on GitHub about the possibility to split JS and it > gathered positive feedback [5]. > > [5] https://github.com/apache/arrow/discussions/45943 > > I propose JS as the next candidate because: > > * We don't need to update the major version frequently. > * This is the main reason. The release process for apache/arrow will be > simplified by removing building/verifying/testing JS and uploading packages > to npm. > * It's a native implementation not bindings > * The current JS release process is simple and part of it is already > automated (we could automate signing and uploading binaries without needing > to rebuild but this can be done afterwards). > 1. Upload source and sign > 2. Automatic verification via GitHub actions > 3. Vote > 4. Download voted source code, build JS packages and push them to npm > > * I think that Paul or Dominik can request new releases as we do with Julia > and either me or Kou can act as release managers. > > What do you think about this? > > > Thanks, > Raúl >
