You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Wes McKinney <we...@gmail.com> on 2017/04/03 18:25:02 UTC
Arrow 0.3 release timeline
hi folks,
We've been making excellent progress toward the 0.3 release -- 123
patches in since 0.2, which was released a little over 6 weeks ago.
Here is the JIRA to help track related issues:
https://issues.apache.org/jira/browse/ARROW-670
Once ARROW-510 (https://github.com/apache/arrow/pull/475, thanks
Leif!) has been resolved, we'll have all of the date and time types
reconciled which was one of the major goals for the release. It would
be nice to get the fixed size binary working end to end (ARROW-634),
but if that slips to 0.4, I don't think it's a big deal.
I know there are a number of other Java patches in flight; I will let
others comment on their status.
What remains on the C++ and Python side
* Decimal patch (ARROW-655)
* Some date and time compatibility with pandas
* Packaging issues on Linux / OS X, e.g. wheels for pyarrow that can
be compiled against / linked to by thirdparties
* Windows support for Python
* Some miscellanea parquet-cpp integration improvements
If all goes well, we may be able to cut an RC next week or the week after.
Is there anything else that others would like to see go into the 0.3
release? I think we may be able to make the 0.4 release more quickly
(~1 month or less after 0.3) as we finish out some of the additional
compatibility issues (dictionaries in IPC stream/file format is a
significant one).
Thanks
Wes
Re: Arrow 0.3 release timeline
Posted by Julien Le Dem <ju...@dremio.com>.
I reviewed the currently pending PRs on the java side.
I opened 2 PRs for the opened java JIRAs from the list: ARROW-777, ARROW-720
On Fri, Apr 14, 2017 at 12:55 PM, Julien Le Dem <ju...@dremio.com> wrote:
> I'm looking through them
>
> On Fri, Apr 14, 2017 at 9:26 AM, Wes McKinney <we...@gmail.com> wrote:
>
>> hi all,
>>
>> I'm working to close out the remaining Python and C++ stuff we wanted
>> to get in to 0.3 for the sake of other Python projects that want to
>> use Arrow.
>>
>> There are 8 patches up that touch the Java codebase. If we can get all
>> these closed out then I think we should be able to cut a release
>> candidate sometime next week.
>>
>> Thanks
>> Wes
>>
>> On Mon, Apr 10, 2017 at 12:38 PM, Wes McKinney <we...@gmail.com>
>> wrote:
>> > With the Easter holiday and long weekend, we probably will not be able
>> > to do an RC until next week at earliest.
>> >
>> > In the meantime, there are a lot of patches in review. Please keep the
>> > release JIRA (https://issues.apache.org/jira/browse/ARROW-670) updated
>> > with blocking issues so we can track what patches are in progress or
>> > still TODO.
>> >
>> > Thanks!
>> > Wes
>> >
>> > On Wed, Apr 5, 2017 at 10:38 AM, Julien Le Dem <ju...@dremio.com>
>> wrote:
>> >> The current 0.3 goal is good for me.
>> >>
>> >> On Mon, Apr 3, 2017 at 11:25 AM, Wes McKinney <we...@gmail.com>
>> wrote:
>> >>
>> >>> hi folks,
>> >>>
>> >>> We've been making excellent progress toward the 0.3 release -- 123
>> >>> patches in since 0.2, which was released a little over 6 weeks ago.
>> >>>
>> >>> Here is the JIRA to help track related issues:
>> >>>
>> >>> https://issues.apache.org/jira/browse/ARROW-670
>> >>>
>> >>> Once ARROW-510 (https://github.com/apache/arrow/pull/475, thanks
>> >>> Leif!) has been resolved, we'll have all of the date and time types
>> >>> reconciled which was one of the major goals for the release. It would
>> >>> be nice to get the fixed size binary working end to end (ARROW-634),
>> >>> but if that slips to 0.4, I don't think it's a big deal.
>> >>>
>> >>> I know there are a number of other Java patches in flight; I will let
>> >>> others comment on their status.
>> >>>
>> >>> What remains on the C++ and Python side
>> >>>
>> >>> * Decimal patch (ARROW-655)
>> >>> * Some date and time compatibility with pandas
>> >>> * Packaging issues on Linux / OS X, e.g. wheels for pyarrow that can
>> >>> be compiled against / linked to by thirdparties
>> >>> * Windows support for Python
>> >>> * Some miscellanea parquet-cpp integration improvements
>> >>>
>> >>> If all goes well, we may be able to cut an RC next week or the week
>> after.
>> >>>
>> >>> Is there anything else that others would like to see go into the 0.3
>> >>> release? I think we may be able to make the 0.4 release more quickly
>> >>> (~1 month or less after 0.3) as we finish out some of the additional
>> >>> compatibility issues (dictionaries in IPC stream/file format is a
>> >>> significant one).
>> >>>
>> >>> Thanks
>> >>> Wes
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Julien
>>
>
>
>
> --
> Julien
>
--
Julien
Re: Arrow 0.3 release timeline
Posted by Julien Le Dem <ju...@dremio.com>.
I'm looking through them
On Fri, Apr 14, 2017 at 9:26 AM, Wes McKinney <we...@gmail.com> wrote:
> hi all,
>
> I'm working to close out the remaining Python and C++ stuff we wanted
> to get in to 0.3 for the sake of other Python projects that want to
> use Arrow.
>
> There are 8 patches up that touch the Java codebase. If we can get all
> these closed out then I think we should be able to cut a release
> candidate sometime next week.
>
> Thanks
> Wes
>
> On Mon, Apr 10, 2017 at 12:38 PM, Wes McKinney <we...@gmail.com>
> wrote:
> > With the Easter holiday and long weekend, we probably will not be able
> > to do an RC until next week at earliest.
> >
> > In the meantime, there are a lot of patches in review. Please keep the
> > release JIRA (https://issues.apache.org/jira/browse/ARROW-670) updated
> > with blocking issues so we can track what patches are in progress or
> > still TODO.
> >
> > Thanks!
> > Wes
> >
> > On Wed, Apr 5, 2017 at 10:38 AM, Julien Le Dem <ju...@dremio.com>
> wrote:
> >> The current 0.3 goal is good for me.
> >>
> >> On Mon, Apr 3, 2017 at 11:25 AM, Wes McKinney <we...@gmail.com>
> wrote:
> >>
> >>> hi folks,
> >>>
> >>> We've been making excellent progress toward the 0.3 release -- 123
> >>> patches in since 0.2, which was released a little over 6 weeks ago.
> >>>
> >>> Here is the JIRA to help track related issues:
> >>>
> >>> https://issues.apache.org/jira/browse/ARROW-670
> >>>
> >>> Once ARROW-510 (https://github.com/apache/arrow/pull/475, thanks
> >>> Leif!) has been resolved, we'll have all of the date and time types
> >>> reconciled which was one of the major goals for the release. It would
> >>> be nice to get the fixed size binary working end to end (ARROW-634),
> >>> but if that slips to 0.4, I don't think it's a big deal.
> >>>
> >>> I know there are a number of other Java patches in flight; I will let
> >>> others comment on their status.
> >>>
> >>> What remains on the C++ and Python side
> >>>
> >>> * Decimal patch (ARROW-655)
> >>> * Some date and time compatibility with pandas
> >>> * Packaging issues on Linux / OS X, e.g. wheels for pyarrow that can
> >>> be compiled against / linked to by thirdparties
> >>> * Windows support for Python
> >>> * Some miscellanea parquet-cpp integration improvements
> >>>
> >>> If all goes well, we may be able to cut an RC next week or the week
> after.
> >>>
> >>> Is there anything else that others would like to see go into the 0.3
> >>> release? I think we may be able to make the 0.4 release more quickly
> >>> (~1 month or less after 0.3) as we finish out some of the additional
> >>> compatibility issues (dictionaries in IPC stream/file format is a
> >>> significant one).
> >>>
> >>> Thanks
> >>> Wes
> >>>
> >>
> >>
> >>
> >> --
> >> Julien
>
--
Julien
Re: Arrow 0.3 release timeline
Posted by Wes McKinney <we...@gmail.com>.
hi all,
I'm working to close out the remaining Python and C++ stuff we wanted
to get in to 0.3 for the sake of other Python projects that want to
use Arrow.
There are 8 patches up that touch the Java codebase. If we can get all
these closed out then I think we should be able to cut a release
candidate sometime next week.
Thanks
Wes
On Mon, Apr 10, 2017 at 12:38 PM, Wes McKinney <we...@gmail.com> wrote:
> With the Easter holiday and long weekend, we probably will not be able
> to do an RC until next week at earliest.
>
> In the meantime, there are a lot of patches in review. Please keep the
> release JIRA (https://issues.apache.org/jira/browse/ARROW-670) updated
> with blocking issues so we can track what patches are in progress or
> still TODO.
>
> Thanks!
> Wes
>
> On Wed, Apr 5, 2017 at 10:38 AM, Julien Le Dem <ju...@dremio.com> wrote:
>> The current 0.3 goal is good for me.
>>
>> On Mon, Apr 3, 2017 at 11:25 AM, Wes McKinney <we...@gmail.com> wrote:
>>
>>> hi folks,
>>>
>>> We've been making excellent progress toward the 0.3 release -- 123
>>> patches in since 0.2, which was released a little over 6 weeks ago.
>>>
>>> Here is the JIRA to help track related issues:
>>>
>>> https://issues.apache.org/jira/browse/ARROW-670
>>>
>>> Once ARROW-510 (https://github.com/apache/arrow/pull/475, thanks
>>> Leif!) has been resolved, we'll have all of the date and time types
>>> reconciled which was one of the major goals for the release. It would
>>> be nice to get the fixed size binary working end to end (ARROW-634),
>>> but if that slips to 0.4, I don't think it's a big deal.
>>>
>>> I know there are a number of other Java patches in flight; I will let
>>> others comment on their status.
>>>
>>> What remains on the C++ and Python side
>>>
>>> * Decimal patch (ARROW-655)
>>> * Some date and time compatibility with pandas
>>> * Packaging issues on Linux / OS X, e.g. wheels for pyarrow that can
>>> be compiled against / linked to by thirdparties
>>> * Windows support for Python
>>> * Some miscellanea parquet-cpp integration improvements
>>>
>>> If all goes well, we may be able to cut an RC next week or the week after.
>>>
>>> Is there anything else that others would like to see go into the 0.3
>>> release? I think we may be able to make the 0.4 release more quickly
>>> (~1 month or less after 0.3) as we finish out some of the additional
>>> compatibility issues (dictionaries in IPC stream/file format is a
>>> significant one).
>>>
>>> Thanks
>>> Wes
>>>
>>
>>
>>
>> --
>> Julien
Re: Arrow 0.3 release timeline
Posted by Wes McKinney <we...@gmail.com>.
With the Easter holiday and long weekend, we probably will not be able
to do an RC until next week at earliest.
In the meantime, there are a lot of patches in review. Please keep the
release JIRA (https://issues.apache.org/jira/browse/ARROW-670) updated
with blocking issues so we can track what patches are in progress or
still TODO.
Thanks!
Wes
On Wed, Apr 5, 2017 at 10:38 AM, Julien Le Dem <ju...@dremio.com> wrote:
> The current 0.3 goal is good for me.
>
> On Mon, Apr 3, 2017 at 11:25 AM, Wes McKinney <we...@gmail.com> wrote:
>
>> hi folks,
>>
>> We've been making excellent progress toward the 0.3 release -- 123
>> patches in since 0.2, which was released a little over 6 weeks ago.
>>
>> Here is the JIRA to help track related issues:
>>
>> https://issues.apache.org/jira/browse/ARROW-670
>>
>> Once ARROW-510 (https://github.com/apache/arrow/pull/475, thanks
>> Leif!) has been resolved, we'll have all of the date and time types
>> reconciled which was one of the major goals for the release. It would
>> be nice to get the fixed size binary working end to end (ARROW-634),
>> but if that slips to 0.4, I don't think it's a big deal.
>>
>> I know there are a number of other Java patches in flight; I will let
>> others comment on their status.
>>
>> What remains on the C++ and Python side
>>
>> * Decimal patch (ARROW-655)
>> * Some date and time compatibility with pandas
>> * Packaging issues on Linux / OS X, e.g. wheels for pyarrow that can
>> be compiled against / linked to by thirdparties
>> * Windows support for Python
>> * Some miscellanea parquet-cpp integration improvements
>>
>> If all goes well, we may be able to cut an RC next week or the week after.
>>
>> Is there anything else that others would like to see go into the 0.3
>> release? I think we may be able to make the 0.4 release more quickly
>> (~1 month or less after 0.3) as we finish out some of the additional
>> compatibility issues (dictionaries in IPC stream/file format is a
>> significant one).
>>
>> Thanks
>> Wes
>>
>
>
>
> --
> Julien
Re: Arrow 0.3 release timeline
Posted by Julien Le Dem <ju...@dremio.com>.
The current 0.3 goal is good for me.
On Mon, Apr 3, 2017 at 11:25 AM, Wes McKinney <we...@gmail.com> wrote:
> hi folks,
>
> We've been making excellent progress toward the 0.3 release -- 123
> patches in since 0.2, which was released a little over 6 weeks ago.
>
> Here is the JIRA to help track related issues:
>
> https://issues.apache.org/jira/browse/ARROW-670
>
> Once ARROW-510 (https://github.com/apache/arrow/pull/475, thanks
> Leif!) has been resolved, we'll have all of the date and time types
> reconciled which was one of the major goals for the release. It would
> be nice to get the fixed size binary working end to end (ARROW-634),
> but if that slips to 0.4, I don't think it's a big deal.
>
> I know there are a number of other Java patches in flight; I will let
> others comment on their status.
>
> What remains on the C++ and Python side
>
> * Decimal patch (ARROW-655)
> * Some date and time compatibility with pandas
> * Packaging issues on Linux / OS X, e.g. wheels for pyarrow that can
> be compiled against / linked to by thirdparties
> * Windows support for Python
> * Some miscellanea parquet-cpp integration improvements
>
> If all goes well, we may be able to cut an RC next week or the week after.
>
> Is there anything else that others would like to see go into the 0.3
> release? I think we may be able to make the 0.4 release more quickly
> (~1 month or less after 0.3) as we finish out some of the additional
> compatibility issues (dictionaries in IPC stream/file format is a
> significant one).
>
> Thanks
> Wes
>
--
Julien