hi Neal, Thanks for helping coordinate. I agree we should be in a position to release sometime next week.
Can folks from the Rust and Java side review issues in the backlog? According to the dashboard there are 19 Rust issues open and 7 Java issues. Thanks On Tue, Mar 24, 2020 at 10:01 AM Neal Richardson <neal.p.richard...@gmail.com> wrote: > > Hi all, > A few weeks ago, there seemed to be consensus (lazy, at least) for a 0.17 > release at the end of the month. Judging from > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.17.0+Release, it > looks like we're getting closer. > > I'd encourage everyone to review their backlogs and (1) bump from 0.17 > scope any tickets they don't plan to finish this week, and (2) if there are > any issues that should block release, make sure they are flagged as > "blockers". > > Neal > > On Tue, Mar 10, 2020 at 7:39 AM Wes McKinney <wesmck...@gmail.com> wrote: > > > It seems like the consensus is to push for a 0.17.0 major release > > sooner rather than doing a patch release, since releases in general > > are costly. This is fine with me. I see that a 0.17.0 milestone has > > been created in JIRA and some JIRA gardening has begun. Do you think > > we can be in a position to release by the week of March 23 or the week > > of March 30? > > > > On Thu, Mar 5, 2020 at 8:39 PM Wes McKinney <wesmck...@gmail.com> wrote: > > > > > > If people are generally on board with accelerating a 0.17.0 major > > > release, then I would suggest renaming "1.0.0" to "0.17.0" and > > > beginning to do issue gardening to whittle things down to > > > critical-looking bugs and high probability patches for the next couple > > > of weeks. > > > > > > On Thu, Mar 5, 2020 at 11:31 AM Wes McKinney <wesmck...@gmail.com> > > wrote: > > > > > > > > I recall there are some other issues that have been reported or fixed > > > > that are critical and not yet marked with 0.16.1. > > > > > > > > I'm also OK with doing a 0.17.0 release sooner > > > > > > > > On Thu, Mar 5, 2020 at 11:31 AM Neal Richardson > > > > <neal.p.richard...@gmail.com> wrote: > > > > > > > > > > I would also be more supportive of doing 0.17 earlier instead of a > > patch > > > > > release. > > > > > > > > > > Neal > > > > > > > > > > > > > > > On Thu, Mar 5, 2020 at 9:29 AM Neal Richardson < > > neal.p.richard...@gmail.com> > > > > > wrote: > > > > > > > > > > > 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 > > > > > >> > > > > > > > >
