; release verification script passes on a snapshot of master)
>
> On Thu, Mar 15, 2018 at 2:06 AM, Kouhei Sutou wrote:
> > https://github.com/apache/arrow/pull/1752 will solve this.
> >
> > --
> > kou
> >
> > In <20180315.135146.1891617944364686374
row/pull/1752 will solve this.
>
> --
> kou
>
> In <20180315.135146.1891617944364686374....@clear-code.com>
> "Re: Working towards getting 0.9.0 release candidate up next week" on Thu,
> 15 Mar 2018 13:51:46 +0900 (JST),
> Kouhei Sutou wrote:
>
>>
https://github.com/apache/arrow/pull/1752 will solve this.
--
kou
In <20180315.135146.1891617944364686374@clear-code.com>
"Re: Working towards getting 0.9.0 release candidate up next week" on Thu, 15
Mar 2018 13:51:46 +0900 (JST),
Kouhei Sutou wrote:
> Sure. Plea
Sure. Please wait for a while.
--
kou
In
"Re: Working towards getting 0.9.0 release candidate up next week" on Thu, 15
Mar 2018 00:49:02 -0400,
Wes McKinney wrote:
> I ran into another problem:
>
> https://issues.apache.org/jira/browse/ARROW-2313
>
> @Kou, coul
;>
>>>>>>>>>> Thanks
>>>>>>>>>> Wes
>>>>>>>>>>
>>>>>>>>>> On Mon, Mar 12, 2018 at 12:03 AM, Wes McKinney
>>>>>>>>>> wrote:
>>>>>>>>>>&g
>>>>>> I've done a pass over the remaining JIRAs -- I think we're going to
>>>>>>>>>> need at least another full day to get things buttoned up, so I would
>>>>>>>>>> say we're looking at an RC on Tuesday.
>>>>&
ull day to get things buttoned up, so I would
>>>>>>>>> say we're looking at an RC on Tuesday.
>>>>>>>>>
>>>>>>>>> In progress:
>>>>>>>>> - ARROW-1425: Patch up, needs some editing, may be moved to 0.10.0
>>
;> >>>> In progress:
>>>> >>>> - ARROW-1425: Patch up, needs some editing, may be moved to 0.10.0
>>>> >>>> - ARROW-2282: Patch up, needs some test cases
>>>> >>>> - ARROW-1974: Patch in review in apache
h up, needs some test cases
>>> >>>> - ARROW-1974: Patch in review in apache/parquet-cpp -- may want to
>>> >>>> move this JIRA to the Parquet project
>>> >>>> - ARROW-2122: Patch to be reviewed
>>> >>>> - ARROW-2135: Pa
project
>> >>>> - ARROW-2122: Patch to be reviewed
>> >>>> - ARROW-2135: Patch to be merged
>> >>>>
>> >>>> TODO
>> >>>> - ARROW-2082: Parquet segfault <- to be investigated, may be moved to
>> >>
merged
> >>>>
> >>>> TODO
> >>>> - ARROW-2082: Parquet segfault <- to be investigated, may be moved to
> >>>> 0.10.0
> >>>> - ARROW-2118: Fix rough edge with reading length-0 files
> >>>> - ARROW-2227: Bug with creating chunk
creating chunked arrays in Table.from_pandas
>>>> - ARROW-2292: Deprecation / renaming a Python method
>>>>
>>>> Out of the two items in TODO, ARROW-2118 and ARROW-2292 are small
>>>> matters, so I will take care of them. ARROW-2227 may not be fixable
>>>> wi
gt;>>>- Updating pip packages for C++ and Python
>>>>>>
>>>>>> Can we try adding PyArrow source package to PyPI at the
>>>>>> 0.9.0?
>>>>>>
>>>>>> I want to install PyArrow with Arrow C++ installed by .deb
&g
>> matters, so I will take care of them. ARROW-2227 may not be fixable
>> within ~1 day but it would be useful to have a diagnosis in case the
>> fix is easy -- multiple users hit this bug.
>>
>> Thanks,
>> Wes
>>
>> On Thu, Mar 8, 2018 at 8:47 PM, Kou
> matters, so I will take care of them. ARROW-2227 may not be fixable
> within ~1 day but it would be useful to have a diagnosis in case the
> fix is easy -- multiple users hit this bug.
>
> Thanks,
> Wes
>
> On Thu, Mar 8, 2018 at 8:47 PM, Kouhei Sutou wrote:
>> Tha
1 day but it would be useful to have a diagnosis in case the
fix is easy -- multiple users hit this bug.
Thanks,
Wes
On Thu, Mar 8, 2018 at 8:47 PM, Kouhei Sutou wrote:
> Thanks!
>
> --
> kou
>
> In
> "Re: Working towards getting 0.9.0 release candidate up nex
Thanks!
--
kou
In
"Re: Working towards getting 0.9.0 release candidate up next week" on Thu, 8
Mar 2018 20:44:14 -0500,
Wes McKinney wrote:
> hi Kou -- yes, I think this is a good idea. It will require a little
> bit of work to be able to produce a viable standalon
I, I can install PyArrow with
> Arrow C++ installed by .deb or .rpm by "pip --no-binary
> pyarrow".
>
> Red Arrow can also use Arrow C++ installed by .deb or .rpm.
>
>
> Thanks,
> --
> kou
>
> In
> "Re: Working towards getting 0.9.0 relea
by "pip --no-binary
pyarrow".
Red Arrow can also use Arrow C++ installed by .deb or .rpm.
Thanks,
--
kou
In
"Re: Working towards getting 0.9.0 release candidate up next week" on Thu, 8
Mar 2018 11:25:32 -0800,
Siddharth Teotia wrote:
> All,
>
> I plan t
Thanks, Wes. Let's shoot for Monday.
On Thu, Mar 8, 2018 at 11:31 AM, Wes McKinney wrote:
> Since almost all of the items in TODO are C++ or Python issues, I can
> do a final review today to remove anything that isn't absolutely
> necessary for 0.9.0. We have a couple of nasty bugs still in TODO
Since almost all of the items in TODO are C++ or Python issues, I can
do a final review today to remove anything that isn't absolutely
necessary for 0.9.0. We have a couple of nasty bugs still in TODO that
we should try to fix -- in the event that they cannot be fixed, we may
need to do a 0.9.1 in
All,
I plan to get RC out over the weekend or early Monday. Is that fine with
everybody?
We have 6 items in progress --
https://issues.apache.org/jira/projects/ARROW/versions/12341707#release-report-tab-body.
How do people feel about completing these JIRAs by tomorrow? I am
completely fine with d
hey Sidd,
The Python backlog is still in pretty rough shape. I'd like to see if
we can make an RC by Friday but if not we can defer to Monday/Tuesday
the following week (3/12 or 13). I will trim as much as possible out
of the current backlog to get things down to the essential
- Wes
On Sun, Feb
Sounds good.
Thanks
Sidd
On Feb 24, 2018 6:24 PM, "Wes McKinney" wrote:
Hi Sidd,
I think we have too many bugs to make an RC this coming week. I suggest we
defer to the following week.
Thanks
Wes
On Feb 24, 2018 7:09 PM, "Siddharth Teotia" wrote:
Hi All,
We currently have 10 issues in pro
Hi Sidd,
I think we have too many bugs to make an RC this coming week. I suggest we
defer to the following week.
Thanks
Wes
On Feb 24, 2018 7:09 PM, "Siddharth Teotia" wrote:
Hi All,
We currently have 10 issues in progress and PRs are available for 8 of
them. In interest of getting a release
Hi All,
We currently have 10 issues in progress and PRs are available for 8 of
them. In interest of getting a release candidate next week, I would request
people to review PRs as soon as they can to help make progress and close
out as many JIRAs as we can.
There are 32 issues in TODO list and 25
26 matches
Mail list logo
