Yes, check the windows wheels please. We test them in a conda
env [1], so theoretically they should be fine.
[1]:
https://github.com/apache/arrow/blob/master/dev/tasks/python-wheels/win-build.bat#L76-L88
On Wed, Mar 27, 2019 at 10:09 PM Wes McKinney wrote:
> That's definitely a problem, we can'
That's definitely a problem, we can't ship broken wheels. I can take a
look at the wheels locally in the next couple of hours if that helps,
but getting them tested again in CI would be the best thing
On Wed, Mar 27, 2019 at 4:03 PM Antoine Pitrou wrote:
>
>
> Forgot the link, sorry:
> https://gi
Forgot the link, sorry:
https://github.com/apache/arrow/pull/4015
Regards
Antoine.
Le 27/03/2019 à 22:02, Antoine Pitrou a écrit :
>
> Unsure this is related, but there is also a problem that Windows wheels
> are not tested anymore on AppVeyor (and actually fail if you re-enable
> the test).
Unsure this is related, but there is also a problem that Windows wheels
are not tested anymore on AppVeyor (and actually fail if you re-enable
the test).
Regards
Antoine.
Le 27/03/2019 à 22:00, Wes McKinney a écrit :
> Thanks Kou. This is a good learning experience. We will continue to do
> b
Thanks Kou. This is a good learning experience. We will continue to do
better with each release
On Wed, Mar 27, 2019 at 3:57 PM Kouhei Sutou wrote:
>
> Hi,
>
> > What controls do you think we can put in place to prevent the issues
> > you had with RC0-2? For example, I merged a patch that affecte
che/arrow/pull/4040
* https://github.com/apache/arrow/pull/4041
but I fixed them locally and continued RC creation. I sent
these pull requests when I found the RC0 has a problem.
Thanks,
--
kou
In
"Re: Timeline for 0.13 Arrow release" on Wed, 27 Mar 2019 07:42:42 -0500,
Wes McKinne
vious day of the release day.
* RC2 problem: I used the commit that doesn't include the
fix for the RC1 problem. :<
* I forgot to merge the upstream master into the local
master before I create RC. It's a human error...
Thanks,
--
kou
In
"Re: Timeline for 0.13 Arr
t; > > against RC3.
> > >
> > > We need to wait building and uploading packages:
> > >
> > > https://github.com/kou/crossbow/branches/all?query=build-71
> > >
> > >
> > > I'll be able to send vote e-mail in 12 hours...
&
ing packages:
> >
> > https://github.com/kou/crossbow/branches/all?query=build-71
> >
> >
> > I'll be able to send vote e-mail in 12 hours...
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In
> > "Re: Timeline f
rossbow/branches/all?query=build-71
>
>
> I'll be able to send vote e-mail in 12 hours...
>
>
> Thanks,
> --
> kou
>
> In
> "Re: Timeline for 0.13 Arrow release" on Tue, 26 Mar 2019 12:51:05 -0700,
> Javier Luraschi wrote:
>
> > Great, than
erge. Thank you!
>> >
>> > On Tue, Mar 26, 2019 at 12:38 PM Kouhei Sutou
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > We don't freeze anything.
>> > > We can merge pull requests when they are ready to merge as usual.
>>
27;t freeze anything.
> > > We can merge pull requests when they are ready to merge as usual.
> > >
> > >
> > > Thanks,
> > > --
> > > kou
> > >
> > > In <6531c437-6bf9-61cd-c7c6-7be06fa96...@python.org>
> > > "Re: Ti
we all think we can cut an RC by the end
> of
> > >>> the week? What are the blocking issues?
> > >>>
> > >>> Thanks
> > >>> Wes
> > >>>
> > >>> On Sat, Mar 16, 2019 at 9:57 PM Kouhei Sutou
> > wrote:
> > >
> We can merge pull requests when they are ready to merge as usual.
>
>
> Thanks,
> --
> kou
>
> In <6531c437-6bf9-61cd-c7c6-7be06fa96...@python.org>
> "Re: Timeline for 0.13 Arrow release" on Tue, 26 Mar 2019 14:58:06 +0100,
> Antoine Pitrou wr
Hi,
We don't freeze anything.
We can merge pull requests when they are ready to merge as usual.
Thanks,
--
kou
In <6531c437-6bf9-61cd-c7c6-7be06fa96...@python.org>
"Re: Timeline for 0.13 Arrow release" on Tue, 26 Mar 2019 14:58:06 +0100,
Antoine Pitrou wrote:
&
gt;>>>>
>>>>>
>>>>> Le 19/03/2019 à 15:46, Kouhei Sutou a écrit :
>>>>>> Hi,
>>>>>>
>>>>>> There are no blockers on GLib, Ruby and Linux packages.
>>>>>>
>>>>>> Can we
ipt into 0.13.0?
> > > > > If we include JavaScript into 0.13.0, we can remove
> > > > > codes to release JavaScript separately. For example, we can
> > > > > remove dev/release/js-*. We can enable version update code
> > > > > in d
move dev/release/js-*. We can enable version update code
> > > > in dev/release/00-prepare.sh:
> > > >
> > https://github.com/apache/arrow/blob/master/dev/release/00-prepare.sh#L67-L74
> > > >
> > > > We can merge "JavaScript Releases"
t; > in dev/release/00-prepare.sh:
> > >
> https://github.com/apache/arrow/blob/master/dev/release/00-prepare.sh#L67-L74
> > >
> > > We can merge "JavaScript Releases" document into our release
> > > document:
> > >
> https://
ent into our release
> > document:
> > https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-JavaScriptReleases
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In
> > "Re: Timeline for 0.13 Arrow
/release/00-prepare.sh#L67-L74
>
> We can merge "JavaScript Releases" document into our release
> document:
> https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-JavaScriptReleases
>
>
> Thanks,
> --
> kou
>
; > > wrote:
> > > >
> > > > > Hey,
> > > > >
> > > > > I'll gladly help Kou. You've postponed the the packaging issues,
> > > > > but at least the wheel builds must pass, I'm still working on it.
> > &g
p Kou. You've postponed the the packaging issues,
> > > > but at least the wheel builds must pass, I'm still working on it.
> > > >
> > > > - K
> > > >
> > > > On Mon, Mar 25, 2019 at 10:03 PM Kouhei Sutou
> > wrote:
> > &g
t;
> > > > Hi,
> > > >
> > > > It seems that nobody can be a release manager.
> > > > I'll be the release manager for 0.13.0. But I don't have
> > > > enough time. Could someone help me?
> > > >
> > > > Thanks,
>
r 25, 2019 at 10:03 PM Kouhei Sutou wrote:
> >
> > > Hi,
> > >
> > > It seems that nobody can be a release manager.
> > > I'll be the release manager for 0.13.0. But I don't have
> > > enough time. Could someone help me?
> > >
> &
>
> On Mon, Mar 25, 2019 at 10:03 PM Kouhei Sutou wrote:
>
> > Hi,
> >
> > It seems that nobody can be a release manager.
> > I'll be the release manager for 0.13.0. But I don't have
> > enough time. Could someone help me?
> >
> > Thanks,
&g
e the release manager for 0.13.0. But I don't have
> enough time. Could someone help me?
>
> Thanks,
> --
> kou
>
> In
> "Re: Timeline for 0.13 Arrow release" on Mon, 25 Mar 2019 15:37:46 +0100,
> Krisztián Szűcs wrote:
>
> > On Mon, Mar
Hi,
It seems that nobody can be a release manager.
I'll be the release manager for 0.13.0. But I don't have
enough time. Could someone help me?
Thanks,
--
kou
In
"Re: Timeline for 0.13 Arrow release" on Mon, 25 Mar 2019 15:37:46 +0100,
Krisztián Szűcs wrote:
> On
I
> > cannot
> > > do
> > > > > > > it
> > > > > > >
> > > > > > > - Wes
> > > > > > >
> > > > > > > On Tue, Mar 19, 2019 at 9:46 AM Kouhei Sutou <
> k...@clear-code.com
> > >
>
> > > > > >> Hi,
> > > > > >>
> > > > > >> There are no blockers on GLib, Ruby and Linux packages.
> > > > > >>
> > > > > >> Can we include JavaScript into 0.13.0?
> > >
y and Linux packages.
> > > > >>
> > > > >> Can we include JavaScript into 0.13.0?
> > > > >> If we include JavaScript into 0.13.0, we can remove
> > > > >> codes to release JavaScript separately. For example, we can
> > >
e, we can
> > > >> remove dev/release/js-*. We can enable version update code
> > > >> in dev/release/00-prepare.sh:
> > > >>
> >
> https://github.com/apache/arrow/blob/master/dev/release/00-prepare.sh#L67-L74
> > > >>
> > > >> We can merge "JavaScript
e
> > >> codes to release JavaScript separately. For example, we can
> > >> remove dev/release/js-*. We can enable version update code
> > >> in dev/release/00-prepare.sh:
> > >>
> https://github.com/apache/arrow/blob/master/dev/release/00-prepare.sh#L67
.sh#L67-L74
> >>
> >> We can merge "JavaScript Releases" document into our release
> >> document:
> >> https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-JavaScriptReleases
> >>
> >>
>
erge "JavaScript Releases" document into our release
document:
https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-JavaScriptReleases
Thanks,
--
kou
In
"Re: Timeline for 0.13 Arrow release" on Mon, 18 Mar 2019 20:51:12 -0500,
We
https://github.com/apache/arrow/blob/master/dev/release/00-prepare.sh#L67-L74
>
> We can merge "JavaScript Releases" document into our release
> document:
> https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-JavaScriptReleases
>
ld-452
>>
>> I've fixed .deb/.rpm packages: https://github.com/apache/arrow/pull/3934
>> It has been merged.
>> So .deb/.rpm packages are ready for release.
>>
>> Thanks,
>> --
>> kou
>>
>> In
>> "Re: Timeline for 0.13 Arrow
; >>>
> > >>> Thanks
> > >>> Wes
> > >>>
> > >>> On Sat, Mar 16, 2019 at 9:57 PM Kouhei Sutou
> wrote:
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>>> Submitt
> >>>>
> >>>> Hi,
> >>>>
> >>>>> Submitted the packaging builds:
> >>>>>
> >> https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
> >>>>
> >>>> I've f
at 9:57 PM Kouhei Sutou wrote:
>>>>
>>>> Hi,
>>>>
>>>>> Submitted the packaging builds:
>>>>>
>> https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
>>>>
>>>> I'
uhei Sutou wrote:
> >>
> >> Hi,
> >>
> >>> Submitted the packaging builds:
> >>>
> https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
> >>
> >> I've fixed .deb/.rpm packages:
> https://github.
t;
>>> Submitted the packaging builds:
>>> https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
>>
>> I've fixed .deb/.rpm packages: https://github.com/apache/arrow/pull/3934
>> It has been merged.
>> So .deb/.rpm package
> > > >
> > > > Hi,
> > > >
> > > > > Submitted the packaging builds:
> > > > >
> > >
> >
> https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
> > > >
> > > > I
e packaging builds:
> > > >
> >
> https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
> > >
> > > I've fixed .deb/.rpm packages:
> https://github.com/apache/arrow/pull/3934
> > > It has been merged.
> &g
the packaging builds:
> > >
> https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
> >
> > I've fixed .deb/.rpm packages: https://github.com/apache/arrow/pull/3934
> > It has been merged.
> > So .deb/.rpm packages are ready f
; Submitted the packaging builds:
> > https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
>
> I've fixed .deb/.rpm packages: https://github.com/apache/arrow/pull/3934
> It has been merged.
> So .deb/.rpm packages are ready for release.
>
> T
"Re: Timeline for 0.13 Arrow release" on Thu, 14 Mar 2019 16:24:43 +0100,
Krisztián Szűcs wrote:
> Submitted the packaging builds:
> https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
>
> On Thu, Mar 14, 2019 at 4:19 PM Wes McKinney wrote:
Out of the open / in-progress issues still in the backlog:
C++-related: 25
C#: 2
CI-related: 2
Dev tools: 2
Docs: 4
Flight: 3
Packaging: 4
Python: 23 (14 tagged as bugs)
Ruby: 1
Rust: 14
I'm going to try to grind out as many issues as I can in the next few
days, and at least get a sense of "how b
Submitted the packaging builds:
https://github.com/kszucs/crossbow/branches/all?utf8=%E2%9C%93&query=build-452
On Thu, Mar 14, 2019 at 4:19 PM Wes McKinney wrote:
> The CMake refactor is merged! Kudos to Uwe for 3+ weeks of hard labor on
> this.
>
> We should run all the packaging tasks and get
The CMake refactor is merged! Kudos to Uwe for 3+ weeks of hard labor on this.
We should run all the packaging tasks and get a full accounting of
what is broken so we aren't surprised during the release process
On Wed, Mar 13, 2019 at 9:39 AM Krisztián Szűcs
wrote:
>
> The proof of the pudding i
The proof of the pudding is in the eating. You convinced me.
On Wed, Mar 13, 2019 at 3:31 PM Wes McKinney wrote:
> Krisztian -- are you all right with proceeding with merging the CMake
> refactor? I'm pretty committed to helping fix the problems that come
> up. Since most consumers of the projec
Krisztian -- are you all right with proceeding with merging the CMake
refactor? I'm pretty committed to helping fix the problems that come
up. Since most consumers of the project don't test until _after_ a
release, we won't find out about some problems until we merge it and
release it. Thus, IMHO i
I've cleaned up my issues for Rust, moving most of them to 0.14.0.
I have two PRs in progress that I would appreciate reviews on:
https://github.com/apache/arrow/pull/3671 - [Rust] Table API (a.k.a
DataFrame)
https://github.com/apache/arrow/pull/3851 - [Rust] Parquet data source in
DataFusion
O
I disagree. I think we need a forcing function to create some urgency
to work out any of the problems that may come up. If we need to make a
0.13.1 to fix problems that are not caught during the release (and
producing binary artifacts) then I think that is okay
On Tue, Mar 12, 2019 at 9:53 AM Kris
> Having C# NuGet package working would be nice
I've opened https://issues.apache.org/jira/browse/ARROW-4839 for this and I
will be working on it this week. I'd like to see an official Arrow NuGet
package on www.nuget.org soon, so getting it in this release would work out
perfect from my side.
Hi,
The CMake refactor is huge enough to cause unexpected post-release
defects. I'd consider shipping it with the next release and let is stabilize
during the development of 0.14.
On Tue, Mar 12, 2019 at 3:41 PM Wes McKinney wrote:
> hi Uwe,
>
> I would be OK with trying to release next week.
hi Uwe,
I would be OK with trying to release next week. Let's see what others
think. Getting the CMake refactor in and packaging sorted out is the
big priority for the C++-using ecosystem. I haven't seen anything
hugely pressing in the other impls based on the recent patch flow.
Having C# NuGet pa
Hello,
two things come to my mind:
* I'm spending now some time again on the CMake refactor. The only blocker I
currently see is the issue with detecting the correct gtest libraries on
Windows. Otherwise this can go in. Being very confident about my work: This
will break things even though CI
hi folks,
I think we are on track to be able to release toward the end of this
month. My proposed timeline:
* This week (March 11-15): feature/improvement push mostly
* Next week (March 18-22): shift to bug fixes, stabilization, empty
backlog of feature/improvement JIRAs
* Week of March 25: propo
The timeline for the 0.13 release is drawing closer. I would say we
should consider a release candidate either the week of March 18 or
March 25, which gives us ~3 weeks to close out backlog items.
There are around 220 issues open or in-progress in
https://cwiki.apache.org/confluence/display/ARROW
See
https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide
The source release step is one of the places where problems occur.
On Sat, Feb 9, 2019, 10:33 AM
> > On Feb 8, 2019, at 9:19 AM, Uwe L. Korn wrote:
> >
> > We could dockerize some of the release steps to ensure that
> On Feb 8, 2019, at 9:19 AM, Uwe L. Korn wrote:
>
> We could dockerize some of the release steps to ensure that they run in the
> same environment.
I may be able to help with said Dockerization. If not for this release, then
for the next. Are there docs on which systems we wish to target and
hi,
On Fri, Feb 8, 2019 at 10:28 AM Uwe L. Korn wrote:
>
> Hello Wes,
>
>
> > As discussed last month I think we should aim for time-based releases.
> > I think a good release cadence for this project right now is
> > approximately every 2 months. So based on this a 0.13 release
> > candidate sho
Hello Wes,
> As discussed last month I think we should aim for time-based releases.
> I think a good release cadence for this project right now is
> approximately every 2 months. So based on this a 0.13 release
> candidate should be cut the week of March 18.
This sounds fine.
> I'll follow up o
64 matches
Mail list logo
