I'm cutting RC1 right now, right in the middle of uploading binaries to
SVN...
On Fri, Aug 3, 2018 at 9:00 AM Marco Neumann
wrote:
> +1
> Tested against a wide range of applications and no obvious problems found
> so far.
>
> For our regular test against master: WIP, ETA around end of September
+1
Tested against a wide range of applications and no obvious problems found so
far.
For our regular test against master: WIP, ETA around end of September
(hopefully faster).
Thanks,
Marco
On August 2, 2018 9:50:49 PM GMT+02:00, Wes McKinney
wrote:
>I think it's OK to proceed with the next
I think it's OK to proceed with the next RC (RC1) if the code
described in https://issues.apache.org/jira/browse/ARROW-2963 works
properly after the fix. Please let us know tomorrow if you run into
any more issues. Thank you!
On Thu, Aug 2, 2018 at 3:38 PM, Marco Neumann
wrote:
> I'll test the
I'll test the PR tomorrow (Friday, until 15:00 UTC). Thanks for the quick fix!
@Wes Might be doable, I'll check how we can improve there. Sorry for catching
this problem that late.
I'm totally fine with the "no veto" policy. It's a bug for which no test
existed beforehand, and a behavior /
Marco, what would be even better is if you would test your application
against Antoine's PR before it gets merged.
On Thu, Aug 2, 2018 at 2:37 PM Phillip Cloud wrote:
> I'll cut another one. Can someone review Antoine's PR, like ASAP, so that
> I can cut another RC?
>
> On Thu, Aug 2, 2018 at
I'll cut another one. Can someone review Antoine's PR, like ASAP, so that I
can cut another RC?
On Thu, Aug 2, 2018 at 2:32 PM Wes McKinney wrote:
> -1
>
> It's up to Phillip whether he wants to cancel the RC, but note that
> releases cannot be vetoed.
>
> @Marco, thanks for reporting -- is
-1
It's up to Phillip whether he wants to cancel the RC, but note that
releases cannot be vetoed.
@Marco, thanks for reporting -- is there a process which could have
surfaced this issue sooner (e.g. testing your application regularly
against master)?
Thanks,
Wes
On Thu, Aug 2, 2018 at 2:29 PM,
Le 02/08/2018 à 20:15, Li Jin a écrit :
> Antoine,
>
> Do you think we should fail this RC because of Arrow-2963?
It's a regression, so ideally it should be fixed.
Furthermore, the issue can be reproduced quite easily in Python with the
(popular) multiprocessing package.
Regards
Antoine.
Antoine,
Do you think we should fail this RC because of Arrow-2963?
On Thu, Aug 2, 2018 at 2:00 PM Antoine Pitrou wrote:
> On Thu, 2 Aug 2018 17:57:20 +0200
> Antoine Pitrou wrote:
> > I'm on ARROW-2963 and will submit a fix soon.
>
> Fix is at https://github.com/apache/arrow/pull/2363
>
On Thu, 2 Aug 2018 17:57:20 +0200
Antoine Pitrou wrote:
> I'm on ARROW-2963 and will submit a fix soon.
Fix is at https://github.com/apache/arrow/pull/2363
Regards
Antoine.
I'm on ARROW-2963 and will submit a fix soon.
Regards
Antoine.
Le 02/08/2018 à 17:26, Marco Neumann a écrit :
> +0
> Because of https://issues.apache.org/jira/browse/ARROW-2963
> (not sure if this counts as a blocker)
>
> Marco
>
> On August 1, 2018 7:35:50 PM GMT+02:00, Phillip Cloud
+0
Because of https://issues.apache.org/jira/browse/ARROW-2963
(not sure if this counts as a blocker)
Marco
On August 1, 2018 7:35:50 PM GMT+02:00, Phillip Cloud wrote:
>Hello all,
>
>I'd like to propose the 1st release candidate (rc0) of Apache Arrow
>version
>0.10.0. This is a major release
+1 (binding)
ran dev/release/verify-release-candidate.sh on MacOS
I had the same problem with Glib in GISCAN as mentioned in
https://github.com/apache/arrow/pull/2303#issuecomment-406934428
I replaced the make call with `LD_LIBRARY_PATH=$ARROW_HOME/lib make` but did
not seem to fix my
+1
ran dev/release/verify-release-candidate.sh on MacOS
* clang-902.0.39.2
* jdk8
On Wed, Aug 1, 2018 at 8:01 PM, Wes McKinney wrote:
> I won't be able to verify the release for a day or two, but honestly
> huge props / congratulations to Krisztian, Kou, and Phillip for making
> the binary
I won't be able to verify the release for a day or two, but honestly
huge props / congratulations to Krisztian, Kou, and Phillip for making
the binary release packaging project happen. It was a 4 month project
with dozens of tedious patches and hundreds of build iterations, but
this work will pay
+1 (binding)
ran dev/release/verify-release-candidate.sh on Arch Linux
* clang 6
* jdk8
* ruby 2.5.1p57
* nodejs v10.5.0
-Phillip
On Wed, Aug 1, 2018 at 1:35 PM Phillip Cloud wrote:
> Hello all,
>
> I'd like to propose the 1st release candidate (rc0) of Apache Arrow version
> 0.10.0. This is
Hello all,
I'd like to propose the 1st release candidate (rc0) of Apache Arrow version
0.10.0. This is a major release consisting of 454 resolved JIRAs [1].
This release candidate is distinct from previous releases in that it
includes binary artifacts such as python wheels, conda packages, and
17 matches
Mail list logo
