If releases were costless to make, I'd be all for it, but it's not clear to me that it's worth the diversion from other priorities to make a release right now. Nothing on https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%200.16.1 jumps out to me as super urgent--what are you seeing as critical?
If we did decide to go forward, would it be possible to do a release that is limited to the affected implementations (say, do a Python-only release)? That might reduce the cost of building and verifying enough to make it reasonable to consider. Neal On Thu, Mar 5, 2020 at 8:19 AM Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote: > On Thu, Mar 5, 2020 at 5:07 PM Wes McKinney <wesmck...@gmail.com> wrote: > > > > hi folks, > > > > There have been a number of critical issues reported (many of them > > fixed already) since 0.16.0 was released. Is there interest in > > preparing a patch 0.16.1 release (with backported patches onto a > > maint-0.16.x branch as with 0.15.1) since the next major release is a > > minimum of 6-8 weeks away from general availability? > > > > Did the 0.15.1 patch release helper script that Krisztian wrote get > > contributed as a PR? > Not yet, but it is available at > https://gist.github.com/kszucs/b2743546044ccd3215e5bb34fa0d76a0 > > > > Thanks > > Wes >
