Pindikura Ravindra created ARROW-3469:
-
Summary: add travis entry for gandiva on OSX
Key: ARROW-3469
URL: https://issues.apache.org/jira/browse/ARROW-3469
Project: Apache Arrow
Issue Type
Kouhei Sutou created ARROW-3468:
---
Summary: [Packaging] Add wheels for Python 3.7
Key: ARROW-3468
URL: https://issues.apache.org/jira/browse/ARROW-3468
Project: Apache Arrow
Issue Type: Improvem
Dmitry Kalinkin created ARROW-3467:
--
Summary: Building against external double conversion is broken
Key: ARROW-3467
URL: https://issues.apache.org/jira/browse/ARROW-3467
Project: Apache Arrow
Antoine Pitrou created ARROW-3466:
-
Summary: [CI] Python coverage crash on Travis-CI
Key: ARROW-3466
URL: https://issues.apache.org/jira/browse/ARROW-3466
Project: Apache Arrow
Issue Type: Bu
Hi,
One problem for Java packages:
I clicked "Release" button at
https://repository.apache.org/#stagingRepositories but
https://search.maven.org/search?q=g:org.apache.arrow%20AND%20v:0.11.0
shows nothing.
Can you help this?
Here are remains tasks:
* Updating the Arrow website
https://c
OK! Tanks for confirming this!
In
"Re: [RESULT][VOTE] Release Apache Arrow 0.11.0 (RC1)" on Mon, 8 Oct 2018
10:16:55 -0400,
Wes McKinney wrote:
> That looks OK, using test.pypi.org is not strictly necessary. Thanks
> for uploading the wheels
> On Mon, Oct 8, 2018 at 10:16 AM Kouhei Sutou
That looks OK, using test.pypi.org is not strictly necessary. Thanks
for uploading the wheels
On Mon, Oct 8, 2018 at 10:16 AM Kouhei Sutou wrote:
>
> Hi Uwe,
>
> "Updating Python Artifacts"
> https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-pipPacka
Hi Uwe,
"Updating Python Artifacts"
https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-pipPackages
says we test at https://test.pypi.org/ . Is it required?
I don't have an account for https://test.pypi.org/ . Should
I create it?
Sorry but I've uplo
Krisztian Szucs created ARROW-3465:
--
Summary: [Documentation] Fix gen_apidocs' docker image
Key: ARROW-3465
URL: https://issues.apache.org/jira/browse/ARROW-3465
Project: Apache Arrow
Issue
Le 08/10/2018 à 15:31, Wes McKinney a écrit :
> I personally feel pretty strongly about having a linear commit history
> with no merge commits.
>
> Another option is that we add an option to the PR merge tool to merge
> into a branch other than master during release votes. So we can
> continue t
Krisztian Szucs created ARROW-3464:
--
Summary: [Packaging] Build shared libraries for gandiva fat JAR
via crossbow
Key: ARROW-3464
URL: https://issues.apache.org/jira/browse/ARROW-3464
Project: Apache
I personally feel pretty strongly about having a linear commit history
with no merge commits.
Another option is that we add an option to the PR merge tool to merge
into a branch other than master during release votes. So we can
continue to merge PRs and then rebase those onto master later. There's
Le 08/10/2018 à 15:21, Wes McKinney a écrit :
> Here's the last time we discussed this in 2017:
>
> https://lists.apache.org/thread.html/2dc068da8c5074bd7a2717475fa82abe51b323a2a8fd59529971242c@%3Cdev.arrow.apache.org%3E
>
> We have 3 choices:
>
> 1. Lock master during release votes
> 2. Rebas
Here's the last time we discussed this in 2017:
https://lists.apache.org/thread.html/2dc068da8c5074bd7a2717475fa82abe51b323a2a8fd59529971242c@%3Cdev.arrow.apache.org%3E
We have 3 choices:
1. Lock master during release votes
2. Rebase master after a release closes
3. Release from a branch, and th
Kouhei Sutou created ARROW-3463:
---
Summary: [Website] Update for 0.11.0
Key: ARROW-3463
URL: https://issues.apache.org/jira/browse/ARROW-3463
Project: Apache Arrow
Issue Type: Improvement
Kouhei Sutou created ARROW-3462:
---
Summary: [Packaging] Update CHANGELOG for 0.11.0
Key: ARROW-3462
URL: https://issues.apache.org/jira/browse/ARROW-3462
Project: Apache Arrow
Issue Type: Improv
Our policy has been to rebase master after releases. We can discuss how we
handle the release branch again if the community would like. In the
meantime contributors should git reset --hard apache/master
On Mon, Oct 8, 2018, 1:55 PM Antoine Pitrou wrote:
>
> Hi,
>
> Could we avoid rebasing the ma
Hi,
Could we avoid rebasing the master branch? I don't think it's very nice
to force rewriting the histories of all development clones out there.
"git pull" gave me a local merge commit, which I don't know what to do
with...
Regards
Antoine.
Le 08/10/2018 à 13:28, Kouhei Sutou a écrit :
>
Kouhei Sutou created ARROW-3461:
---
Summary: [Packaging] Add a script to upload RC artifacts as the
official release
Key: ARROW-3461
URL: https://issues.apache.org/jira/browse/ARROW-3461
Project: Apache A
Kouhei Sutou created ARROW-3460:
---
Summary: [Packaging] Add a script to rebase master on local
release branch
Key: ARROW-3460
URL: https://issues.apache.org/jira/browse/ARROW-3460
Project: Apache Arrow
Thanks!
I've done the rebase. I'll add this task to the our Wiki.
In
"Re: [RESULT][VOTE] Release Apache Arrow 0.11.0 (RC1)" on Mon, 8 Oct 2018
13:06:54 +0200,
Wes McKinney wrote:
> Yes, rebase the current master branch (after pulling latest) on the release
> branch and force push. Thanks
Yes, rebase the current master branch (after pulling latest) on the release
branch and force push. Thanks Kou!
On Mon, Oct 8, 2018, 1:05 PM Kouhei Sutou wrote:
> Hi Wes,
>
> I have one question that isn't documented at "Post-release
> tasks".
>
> https://cwiki.apache.org/confluence/display/ARROW
Hi Wes,
I have one question that isn't documented at "Post-release
tasks".
https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-Post-releasetasks
Should I rebase master on "release-0_1_0_rc0"
("release-0_11_0_rc1" for this case) local branch?
% g
With 3 binding +1 votes, 1 non-binding +1 and no other
votes, the vote passes. Thanks all!
I'll start "Post-release tasks".
https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-Post-releasetasks
Wes will write a blog post.
Krisztián will create the
I'll create the conda-forge PRs.
On Oct 8 2018, at 10:31 am, Wes McKinney wrote:
>
> Also: I will write a blog post about the 0.11 release and have that
> ready later today. Any volunteers to update the Python conda and pip
> packages?
> On Mon, Oct 8, 2018 at 4:30 AM Wes McKinney wrote:
> >
> >
Pindikura Ravindra created ARROW-3459:
-
Summary: Add support for variable length output vectors
Key: ARROW-3459
URL: https://issues.apache.org/jira/browse/ARROW-3459
Project: Apache Arrow
Also: I will write a blog post about the 0.11 release and have that
ready later today. Any volunteers to update the Python conda and pip
packages?
On Mon, Oct 8, 2018 at 4:30 AM Wes McKinney wrote:
>
> Do you have some ideas about how we can improve our process to find
> more of these small issues
Do you have some ideas about how we can improve our process to find
more of these small issues? Perhaps as part of some nightly builds to
test on different / newer flavors of OSX and base Linux images.
On Mon, Oct 8, 2018 at 3:53 AM Uwe L. Korn wrote:
>
> +1 (binding)
>
> I'm quite uncomfortable w
+1 (binding)
I'm quite uncomfortable with the number of breakages but I think that at this
size of the project it will be unevitable that we will have still some minor
problems in the release.
On Mon, Oct 8, 2018, at 6:39 AM, Bryan Cutler wrote:
> +1 (non-binding)
>
> I ran tests for C++, Pyth
Pindikura Ravindra created ARROW-3458:
-
Summary: Add a string based expression parser
Key: ARROW-3458
URL: https://issues.apache.org/jira/browse/ARROW-3458
Project: Apache Arrow
Issue Typ
30 matches
Mail list logo
