Phillip Cloud created ARROW-2924:
Summary: [Java] mvn release fails with an older maven javadoc
plugin is installed
Key: ARROW-2924
URL: https://issues.apache.org/jira/browse/ARROW-2924
Project:
Sure, added to dev/README
On Fri, Jul 27, 2018 at 1:16 PM, Wes McKinney wrote:
> OK, can you add instructions to the README, or we can also use the
> developer wiki as a lighter-weight option (not requiring PRs)? We need
> to be more consistently organized about developer documentation since
>
Bryan Cutler created ARROW-2923:
---
Summary: [Doc] Add instructions for running Spark integration tests
Key: ARROW-2923
URL: https://issues.apache.org/jira/browse/ARROW-2923
Project: Apache Arrow
OK, can you add instructions to the README, or we can also use the
developer wiki as a lighter-weight option (not requiring PRs)? We need
to be more consistently organized about developer documentation since
the project is expanding rapidly
On Fri, Jul 27, 2018 at 3:25 PM, Bryan Cutler wrote:
>
The commands to run are in the Dockerfile for right now, however, you do
need to use the patched version of Spark from my branch I linked in
ARROW-2914 because there have been Java API changes.
On Fri, Jul 27, 2018 at 12:18 PM, Wes McKinney wrote:
> I dealt with some of the remaining unassigned
I dealt with some of the remaining unassigned issues. There are
several left where the PR author does not have a JIRA account or I
wasn't able to find their ID to add them to the "contributor" role.
@Li, I think you can run (Bryan, is this right?)
dev/run_docker_compose.sh spark_integration
Like, I ran the Spark integration after ARROW-2914 but I'll run again later
today since there might be some changes.
On Fri, Jul 27, 2018, 7:11 AM Li Jin wrote:
> @Bryan I noticed there are integration tests setup with Spark. We should
> probably run those before cutting the RC but I don't know
I tried to clean this up as much as I could, there are still one Jira with
out component (I cannot change the component for some reason) and 20 Jira
without Assignee.
The ones without Assignees are either no PR available or the I cannot find
the PR author in ASF Jira.
Wes, is there anything else
I can help clean this up.
On Fri, Jul 27, 2018 at 2:45 PM, Wes McKinney wrote:
> I have been adding JIRA summary tables to the wiki -- we have some
> untidiness it would be good to clean up, have a look:
>
> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.10.0+Release
>
> * 45
I have been adding JIRA summary tables to the wiki -- we have some
untidiness it would be good to clean up, have a look:
https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.10.0+Release
* 45 resolved issues with no Component
* 42 issues with no Assignee
If anyone has some time please help
Hi Li -- from my perspective we are blocked on the packaging work / release
procedure and nothing else. I am working on ARROW-2814 today but it is not
a blocker. I will review ARROW-2704 and merge that later today if there are
no further issues.
Wes
On Fri, Jul 27, 2018, 7:11 AM Li Jin wrote:
@Bryan I noticed there are integration tests setup with Spark. We should
probably run those before cutting the RC but I don't know how those are run.
If you can help running those or show me how to run those it would be great!
Hello,
Looks like we still have a few PR and open issues. Maybe we should delay
for a few days?
Building and signing on artifacts are worked on by Phillip Cloud (Huge
thanks!), I will sync with Phillip today.
Li
On Tue, Jul 24, 2018 at 6:16 PM, Phillip Cloud wrote:
> That sounds great to me.
Kouhei Sutou created ARROW-2922:
---
Summary: [Release] Make python command name customizable
Key: ARROW-2922
URL: https://issues.apache.org/jira/browse/ARROW-2922
Project: Apache Arrow
Issue
Kouhei Sutou created ARROW-2921:
---
Summary: [Release] Update .deb/.rpm changelos in preparation
Key: ARROW-2921
URL: https://issues.apache.org/jira/browse/ARROW-2921
Project: Apache Arrow
Issue
15 matches
Mail list logo
