Not expressing an opinion on the original question, but if the problem is "not getting everything right the first time", what can be done to reduce the likelihood of getting things wrong? Other languages/implementations have extensive CI and nightly builds, some of which test different packaging scenarios and integration testing with other projects (e.g. spark, dask) that we don't want to break support with. Are there additional JS builds we could add that would increase our confidence in the quality of our releases?
Neal On Thu, Nov 4, 2021 at 12:04 PM Dominik Moritz <domor...@apache.org> wrote: > Dear Arrow Devs, > > We would like to ask to have independent patch releases for the Arrow JS > library. Having independent patch releases will help us resolve issues that > only become visible when people start to use the library. The JS ecosystem > is diverse and only recently has become more standardized. Therefore, it > has been difficult to get everything right the the first time, which had > led to frustrations by many users. It would really help us if we could make > patch releases to fix critical issues without waiting for other libraries > to be ready for a new release as well. > > Thank you for considering the request, > Dominik for the Arrow JS devs >
