It seems that ARROW-1282 is causing some users problems. We have the option of making a 0.5.1 release, but given how much work has reached master (or is about to reach master) I would be in favor of accelerating 0.6.0, cutting a release candidate within the next couple of days. We could aim for another release within 2-3 weeks after completing the Plasma IP clearance.
Thoughts? On Tue, Aug 1, 2017 at 9:44 AM, Uwe L. Korn <uw...@xhochy.com> wrote: > Hello, > > from my side we're mostly fine for a 0.6.0 release. Currently I'm facing > a problem with https://issues.apache.org/jira/browse/ARROW-1302 in the > 0.5.0 OSX wheels. We need to fix this before 0.6.0. Also I would like to > look a bit more into the jemalloc issues that came up with 0.5.0 to get > some of them solved in the next release. > > Uwe > > On Mon, Jul 31, 2017, at 04:55 PM, Wes McKinney wrote: >> hi all, >> >> We're already 40 patches into the next Arrow version. I just created >> https://issues.apache.org/jira/browse/ARROW-1297 as a tracking issue >> so that any blocking issues can be tracked as we push forward to 0.6.0 >> >> You can track the status of the release here (accessible from the >> "Projects" tab --> Releases in JIRA): >> >> https://issues.apache.org/jira/projects/ARROW/versions/12341088 >> >> We don't have any more data types slated for integration testing for >> this release, but it might be nice to try to finish one or more of >> them in the next week or two: >> >> - Fixed size binary >> - Fixed size lists >> - Decimal >> - Union >> >> As far as timeline for 0.6.0, I would like to push for an RC the week >> of 8/14 at latest (assuming we are ready to ship the Plasma C++ code), >> reducing scope if needed. Any contributions of code, documentation, or >> JIRA prioritization would be much appreciated. >> >> Thanks, >> Wes
