ges.
Thanks!
>
> We need to look into -dbgsym packages problem but -debsym
> packages aren't important for normal use. They are needed
> only for debugging libraries by debugger. So we can ignore
> this in 0.14.1.
>
>
> Thanks,
> --
> kou
>
> In
> &quo
ugger. So we can ignore
this in 0.14.1.
Thanks,
--
kou
In
"Re: [DISCUSS] Need for 0.14.1 release due to Python package problems,
Parquet forward compatibility problems" on Wed, 17 Jul 2019 02:34:45 +0200,
Krisztián Szűcs wrote:
> Hi all!
>
> The release process was sort
On Wed, Jul 17, 2019 at 2:34 AM Krisztián Szűcs
wrote:
> Hi all!
>
> The release process was sort of fluid so far, except that the Java version
> strings were
> missing the -SNAPSHOT postfix in the pom files, which required some manual
> intervention.
>
> I'm waiting for the binary builds to pass
Hi all!
The release process was sort of fluid so far, except that the Java version
strings were
missing the -SNAPSHOT postfix in the pom files, which required some manual
intervention.
I'm waiting for the binary builds to pass before sending out the vote
email, but sadly a
couple of debian binary
On Sat, Jul 13, 2019 at 12:57 PM Wes McKinney wrote:
>
> OK, that's been merged and updated. Here's a Crossbow build
>
https://github.com/ursa-labs/crossbow/branches/all?utf8=%E2%9C%93&query=build-665
I'll keep an eye on CI. Anything else I can do to help get an RC out
please let me know
ready uploaded binary artifacts
> > https://github.com/apache/arrow/pull/4872
> > (This will be conflicted with https://github.com/apache/arrow/pull/4868 .)
> >
> >
> > They will be useful to release 0.14.1.
> >
> >
> > Thanks,
> >
tps://github.com/apache/arrow/pull/4872
> (This will be conflicted with https://github.com/apache/arrow/pull/4868 .)
>
>
> They will be useful to release 0.14.1.
>
>
> Thanks,
> --
> kou
>
> In
> "Re: [DISCUSS] Need for 0.14.1 release due to Python package pro
inary artifacts
https://github.com/apache/arrow/pull/4872
(This will be conflicted with https://github.com/apache/arrow/pull/4868 .)
They will be useful to release 0.14.1.
Thanks,
--
kou
In
"Re: [DISCUSS] Need for 0.14.1 release due to Python package problems,
Parquet forward compatibilit
gt; > > > > > On Thu, Jul 11, 2019 at 3:01 PM Eric Erhardt
> > > > > > wrote:
> > > > > > >
> > > > > > > The two C# fixes I'd like in the 0.14.1 release are:
> > > > > > >
> > > >
; > > > > >
> > > > > > The two C# fixes I'd like in the 0.14.1 release are:
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/ARROW-5887 - already
> > > marked with 0.1
t; > > > > Would anyone like to help with release management? I can
> > do so if
> > > > > > > > necessary, but I've already done a lot of release
> > management :)
> > > > > > > >
> > > > > &
gt; > > https://issues.apache.org/jira/browse/ARROW-5908 - hasn't been
> resolved yet. The PR https://github.com/apache/arrow/pull/4851 has one
> approver and the Rust failure doesn't appear to be caused by my change.
> > > >
> > > > I assum
rk ARROW-5908 with a 0.14.1 fix version until
the PR has been merged.
> > >
> > > -Original Message-----
> > > From: Neal Richardson
> > > Sent: Thursday, July 11, 2019 11:59 AM
> > > To: dev@arrow.apache.org
> > > Subject: Re:
ll/4851 has one approver
> > > and the Rust failure doesn't appear to be caused by my change.
> > >
> > > I assume I shouldn't mark ARROW-5908 with a 0.14.1 fix version until the
> > > PR has been merged.
> > >
> > > -Original Messa
gt; > I assume I shouldn't mark ARROW-5908 with a 0.14.1 fix version until the PR
> > has been merged.
> >
> > -Original Message-----
> > From: Neal Richardson
> > Sent: Thursday, July 11, 2019 11:59 AM
> > To: dev@arrow.apache.org
> > Subject: R
0.14.1 fix version until the PR
> has been merged.
>
> -Original Message-
> From: Neal Richardson
> Sent: Thursday, July 11, 2019 11:59 AM
> To: dev@arrow.apache.org
> Subject: Re: [DISCUSS] Need for 0.14.1 release due to Python package
> problems
nd a critical issue in the C# implementation
> that, if
> > > possible, I'd like to get included in a patch release.
> > > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > > github.com%2Fapache%2Farrow%2Fpull%2F4836&data=02%7C01%7CEric
we propose getting changes other than Python or Parquet related
> > > into this release?
> > > >>
> > > >> For example, I found a critical issue in the C# implementation
> that, if
> > > possible, I'd like to get included in a patch
; >>
> > >> For example, I found a critical issue in the C# implementation that, if
> > possible, I'd like to get included in a patch release.
> > https://github.com/apache/arrow/pull/4836
> > >>
> > >> Eric
> > >>
>
t;> For example, I found a critical issue in the C# implementation that, if
> possible, I'd like to get included in a patch release.
> https://github.com/apache/arrow/pull/4836
> >>
> >> Eric
> >>
> >> -Original Message-
> >> From: W
like to get included in a patch release.
>> https://github.com/apache/arrow/pull/4836
>>
>> Eric
>>
>> -Original Message-
>> From: Wes McKinney
>> Sent: Tuesday, July 9, 2019 7:59 AM
>> To: dev@arrow.apache.org
>> Subject: Re: [DISCUSS]
d in a patch release.
> https://github.com/apache/arrow/pull/4836
>
> Eric
>
> -Original Message-
> From: Wes McKinney
> Sent: Tuesday, July 9, 2019 7:59 AM
> To: dev@arrow.apache.org
> Subject: Re: [DISCUSS] Need for 0.14.1 release due to Python package
> probl
ssage-
From: Wes McKinney
Sent: Tuesday, July 9, 2019 7:59 AM
To: dev@arrow.apache.org
Subject: Re: [DISCUSS] Need for 0.14.1 release due to Python package problems,
Parquet forward compatibility problems
On Tue, Jul 9, 2019 at 12:02 AM Sutou Kouhei wrote:
>
> Hi,
>
> > If the prob
On Tue, Jul 9, 2019 at 12:02 AM Sutou Kouhei wrote:
>
> Hi,
>
> > If the problems can be resolved quickly, I should think we could cut
> > an RC for 0.14.1 by the end of this week. The RC could either be cut
> > from a maintenance branch or out of master -- any thoughts about this
> > (cutting fro
Hi,
> If the problems can be resolved quickly, I should think we could cut
> an RC for 0.14.1 by the end of this week. The RC could either be cut
> from a maintenance branch or out of master -- any thoughts about this
> (cutting from master is definitely easier)?
How about just releasing 0.15.0 f
I just pulled the manylinux2010 wheels from PyPI as they were broken
on many systems with an unbundled liblz4 shared library dependency
https://issues.apache.org/jira/browse/ARROW-5868
On Mon, Jul 8, 2019 at 11:53 AM Wes McKinney wrote:
>
> Given the SO versioning issue with 0.14.0 -> 1.0.0 I wo
Given the SO versioning issue with 0.14.0 -> 1.0.0 I would guess that
a maint-0.14.x branch would be a better path forward. I can set that
up and we can identify patches that need to be cherry-picked to be
able to produce a release
On Mon, Jul 8, 2019 at 11:32 AM Wes McKinney wrote:
>
> hi folks,
27 matches
Mail list logo
