[jira] [Created] (ARROW-8337) [Release] Verify release candidate wheels without using conda

Neal Richardson created ARROW-8337: -- Summary: [Release] Verify release candidate wheels without using conda Key: ARROW-8337 URL: https://issues.apache.org/jira/browse/ARROW-8337 Project: Apache

[jira] [Created] (ARROW-5816) [Release] Parallel curl does not work reliably in verify-release-candidate-sh

Wes McKinney created ARROW-5816: --- Summary: [Release] Parallel curl does not work reliably in verify-release-candidate-sh Key: ARROW-5816 URL: https://issues.apache.org/jira/browse/ARROW-5816 Project

[jira] [Created] (ARROW-2960) [Packaging] Fix verify-release-candidate for binary packages and fix release cutting script for lib64 cmake issue

Phillip Cloud created ARROW-2960: Summary: [Packaging] Fix verify-release-candidate for binary packages and fix release cutting script for lib64 cmake issue Key: ARROW-2960 URL: https://issues.apache.org/jira

[jira] [Created] (ARROW-2959) Dockerize verify-release-candidate.{sh,bat}

Phillip Cloud created ARROW-2959: Summary: Dockerize verify-release-candidate.{sh,bat} Key: ARROW-2959 URL: https://issues.apache.org/jira/browse/ARROW-2959 Project: Apache Arrow Issue Type

Re: Working towards 0.10.0 release candidate

ROW-2937 > https://github.com/apache/arrow/pull/2340 that would be helpful. I > think this is the last code-related patch outstanding > > Thank you, > Wes > > On Mon, Jul 30, 2018 at 9:38 AM, Phillip Cloud wrote: > > Wanted to update everyone here regarding the ability to c

Re: Working towards 0.10.0 release candidate

here regarding the ability to cut a release > candidate for 0.10.0. > > The last remaining set of tasks is to be able to use the new packaging tool > (crossbow.py) to build binary artifacts from a source archive. What this > means is that we'll have to move the release scripts in

Re: Working towards 0.10.0 release candidate

Wanted to update everyone here regarding the ability to cut a release candidate for 0.10.0. The last remaining set of tasks is to be able to use the new packaging tool (crossbow.py) to build binary artifacts from a source archive. What this means is that we'll have to move the release sc

Re: Working towards 0.10.0 release candidate

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 > t

Re: Working towards 0.10.0 release candidate

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: > T

Re: Working towards 0.10.0 release candidate

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

Re: Working towards 0.10.0 release candidate

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 this

Re: Working towards 0.10.0 release candidate

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

Re: Working towards 0.10.0 release candidate

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

Re: Working towards 0.10.0 release candidate

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 resolved

Re: Working towards 0.10.0 release candidate

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

Re: Working towards 0.10.0 release candidate

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: >

Re: Working towards 0.10.0 release candidate

@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!

Re: Working towards 0.10.0 release candidate

? > > >> >> >> > > >> >> >> Cheers, > > >> >> >> Craig > > >> >> >> > > >> >> >> On Mon, Jul 23, 2018 at 5:47 PM Li Jin > > >> wrote: > > >> >> >> > > &

Re: Working towards 0.10.0 release candidate

; >> > On Mon, Jul 23, 2018 at 1:40 PM, Wes McKinney < > wesmck...@gmail.com > >> > > >> >> >> wrote: > >> >> >> > > >> >> >> > > hi Li -- thanks. We are working on these issues; I will report >

Re: Working towards 0.10.0 release candidate

t; > >> >> >> wrote: >> >> >> > >> >> >> > > hi Li -- thanks. We are working on these issues; I will report >> in on >> >> >> > > the status at the end of the week. If anything is C++/Python or >> >> >> >

Re: Working towards 0.10.0 release candidate

t; >> >> > > Website-related, please don't move anything out of the milestone > >> >> > > without checking with me. > >> >> > > > >> >> > > The most at risk JIRA for the 0.10 release AFAICT is ARROW-2704: > >> >

Re: Working towards 0.10.0 release candidate

e status at the end of the week. If anything is C++/Python or >> >> > > Website-related, please don't move anything out of the milestone >> >> > > without checking with me. >> >> > > >> >> > > The most at risk J

Re: Working towards 0.10.0 release candidate

t;> > > https://github.com/apache/arrow/pull/2139. I have been following > the > >> > > code review; there seems to be a good deal of cross talk and > >> > > disagreement. > >> > > > >> > > - Wes > >> > > > >>

Re: Working towards 0.10.0 release candidate

; > > > > > > > The most at risk JIRA for the 0.10 release AFAICT is ARROW-2704: > > > > https://github.com/apache/arrow/pull/2139. I have been following the > > > > code review; there seems to be a good deal of cross talk and > > >

Re: Working towards 0.10.0 release candidate

AFAICT is ARROW-2704: >> > > https://github.com/apache/arrow/pull/2139. I have been following the >> > > code review; there seems to be a good deal of cross talk and >> > > disagreement. >> > > >> > > - Wes >> > > >&

Re: Working towards 0.10.0 release candidate

sk JIRA for the 0.10 release AFAICT is ARROW-2704: > > > https://github.com/apache/arrow/pull/2139. I have been following the > > > code review; there seems to be a good deal of cross talk and > > > disagreement. > > > > > > - Wes > > > > >

Re: Working towards 0.10.0 release candidate

CT is ARROW-2704: > > https://github.com/apache/arrow/pull/2139. I have been following the > > code review; there seems to be a good deal of cross talk and > > disagreement. > > > > - Wes > > > > On Mon, Jul 23, 2018 at 1:25 PM, Li Jin wrote: > > > Hi

Re: Working towards 0.10.0 release candidate

> On Mon, Jul 23, 2018 at 1:25 PM, Li Jin wrote: > > Hi All, > > > > As we get close to cut 0.10.0 release candidate, I want to clean up the > > remaining 16 open issues. Here is the board: > > > > https://issues.apache.org/jira/projects/ARROW/versions/12342562

Re: Working towards 0.10.0 release candidate

https://github.com/apache/arrow/pull/2139. I have been following the code review; there seems to be a good deal of cross talk and disagreement. - Wes On Mon, Jul 23, 2018 at 1:25 PM, Li Jin wrote: > Hi All, > > As we get close to cut 0.10.0 release candidate, I want to clean up the >

Working towards 0.10.0 release candidate

Hi All, As we get close to cut 0.10.0 release candidate, I want to clean up the remaining 16 open issues. Here is the board: https://issues.apache.org/jira/projects/ARROW/versions/12342562 For the two with PR open, I'd assume we can include them in the release once review is finished. Fo

Re: Working towards getting 0.9.0 release candidate up next week

; release verification script passes on a snapshot of master) > > On Thu, Mar 15, 2018 at 2:06 AM, Kouhei Sutou wrote: > > https://github.com/apache/arrow/pull/1752 will solve this. > > > > -- > > kou > > > > In <20180315.135146.1891617944364686374

Re: Working towards getting 0.9.0 release candidate up next week

row/pull/1752 will solve this. > > -- > kou > > In <20180315.135146.1891617944364686374@clear-code.com> > "Re: Working towards getting 0.9.0 release candidate up next week" on Thu, > 15 Mar 2018 13:51:46 +0900 (JST), > Kouhei Sutou wrote: > >>

Re: Working towards getting 0.9.0 release candidate up next week

https://github.com/apache/arrow/pull/1752 will solve this. -- kou In <20180315.135146.1891617944364686374@clear-code.com> "Re: Working towards getting 0.9.0 release candidate up next week" on Thu, 15 Mar 2018 13:51:46 +0900 (JST), Kouhei Sutou wrote: > Sure. Plea

Re: Working towards getting 0.9.0 release candidate up next week

Sure. Please wait for a while. -- kou In "Re: Working towards getting 0.9.0 release candidate up next week" on Thu, 15 Mar 2018 00:49:02 -0400, Wes McKinney wrote: > I ran into another problem: > > https://issues.apache.org/jira/browse/ARROW-2313 > > @Kou, coul

Re: Working towards getting 0.9.0 release candidate up next week

;> >>>>>>>>>> Thanks >>>>>>>>>> Wes >>>>>>>>>> >>>>>>>>>> On Mon, Mar 12, 2018 at 12:03 AM, Wes McKinney >>>>>>>>>> wrote: >>>>>>>>>>&g

Re: Working towards getting 0.9.0 release candidate up next week

>>>>>> I've done a pass over the remaining JIRAs -- I think we're going to >>>>>>>>>> need at least another full day to get things buttoned up, so I would >>>>>>>>>> say we're looking at an RC on Tuesday. >>>>&

Re: Working towards getting 0.9.0 release candidate up next week

ull day to get things buttoned up, so I would >>>>>>>>> say we're looking at an RC on Tuesday. >>>>>>>>> >>>>>>>>> In progress: >>>>>>>>> - ARROW-1425: Patch up, needs some editing, may be moved to 0.10.0 >>

Re: Working towards getting 0.9.0 release candidate up next week

;> >>>> In progress: >>>> >>>> - ARROW-1425: Patch up, needs some editing, may be moved to 0.10.0 >>>> >>>> - ARROW-2282: Patch up, needs some test cases >>>> >>>> - ARROW-1974: Patch in review in apache

[jira] [Created] (ARROW-2312) [JS] verify-release-candidate-sh must be updated to include JS in integration tests

Wes McKinney created ARROW-2312: --- Summary: [JS] verify-release-candidate-sh must be updated to include JS in integration tests Key: ARROW-2312 URL: https://issues.apache.org/jira/browse/ARROW-2312

Re: Working towards getting 0.9.0 release candidate up next week

h up, needs some test cases >>> >>>> - ARROW-1974: Patch in review in apache/parquet-cpp -- may want to >>> >>>> move this JIRA to the Parquet project >>> >>>> - ARROW-2122: Patch to be reviewed >>> >>>> - ARROW-2135: Pa

Re: Working towards getting 0.9.0 release candidate up next week

project >> >>>> - ARROW-2122: Patch to be reviewed >> >>>> - ARROW-2135: Patch to be merged >> >>>> >> >>>> TODO >> >>>> - ARROW-2082: Parquet segfault <- to be investigated, may be moved to >> >>

Re: Working towards getting 0.9.0 release candidate up next week

merged > >>>> > >>>> TODO > >>>> - ARROW-2082: Parquet segfault <- to be investigated, may be moved to > >>>> 0.10.0 > >>>> - ARROW-2118: Fix rough edge with reading length-0 files > >>>> - ARROW-2227: Bug with creating chunk

Re: Working towards getting 0.9.0 release candidate up next week

creating chunked arrays in Table.from_pandas >>>> - ARROW-2292: Deprecation / renaming a Python method >>>> >>>> Out of the two items in TODO, ARROW-2118 and ARROW-2292 are small >>>> matters, so I will take care of them. ARROW-2227 may not be fixable >>>> wi

Re: Working towards getting 0.9.0 release candidate up next week

atters, so I will take care of them. ARROW-2227 may not be fixable >>> within ~1 day but it would be useful to have a diagnosis in case the >>> fix is easy -- multiple users hit this bug. >>> >>> Thanks, >>> Wes >>> >>> On Thu, Mar 8,

Re: Working towards getting 0.9.0 release candidate up next week

>> matters, so I will take care of them. ARROW-2227 may not be fixable >> within ~1 day but it would be useful to have a diagnosis in case the >> fix is easy -- multiple users hit this bug. >> >> Thanks, >> Wes >> >> On Thu, Mar 8, 2018 at 8:47 PM, Kou

Re: Working towards getting 0.9.0 release candidate up next week

> matters, so I will take care of them. ARROW-2227 may not be fixable > within ~1 day but it would be useful to have a diagnosis in case the > fix is easy -- multiple users hit this bug. > > Thanks, > Wes > > On Thu, Mar 8, 2018 at 8:47 PM, Kouhei Sutou wrote: >> Tha

Re: Working towards getting 0.9.0 release candidate up next week

1 day but it would be useful to have a diagnosis in case the fix is easy -- multiple users hit this bug. Thanks, Wes On Thu, Mar 8, 2018 at 8:47 PM, Kouhei Sutou wrote: > Thanks! > > -- > kou > > In > "Re: Working towards getting 0.9.0 release candidate up nex

Re: Working towards getting 0.9.0 release candidate up next week

Thanks! -- kou In "Re: Working towards getting 0.9.0 release candidate up next week" on Thu, 8 Mar 2018 20:44:14 -0500, Wes McKinney wrote: > hi Kou -- yes, I think this is a good idea. It will require a little > bit of work to be able to produce a viable standalon

Re: Working towards getting 0.9.0 release candidate up next week

I, I can install PyArrow with > Arrow C++ installed by .deb or .rpm by "pip --no-binary > pyarrow". > > Red Arrow can also use Arrow C++ installed by .deb or .rpm. > > > Thanks, > -- > kou > > In > "Re: Working towards getting 0.9.0 relea

Re: Working towards getting 0.9.0 release candidate up next week

by "pip --no-binary pyarrow". Red Arrow can also use Arrow C++ installed by .deb or .rpm. Thanks, -- kou In "Re: Working towards getting 0.9.0 release candidate up next week" on Thu, 8 Mar 2018 11:25:32 -0800, Siddharth Teotia wrote: > All, > > I plan t

Re: Working towards getting 0.9.0 release candidate up next week

.com> > >> wrote: > >> > Sounds good. > >> > > >> > Thanks > >> > Sidd > >> > > >> > On Feb 24, 2018 6:24 PM, "Wes McKinney" wrote: > >> > > >> > Hi Sidd, > >> > > >> > I th

Re: Working towards getting 0.9.0 release candidate up next week

> >> > Hi Sidd, >> > >> > I think we have too many bugs to make an RC this coming week. I suggest >> we >> > defer to the following week. >> > >> > Thanks >> > Wes >> > >> > On Feb 24, 2018 7:09 PM, "Siddha

Re: Working towards getting 0.9.0 release candidate up next week

week. > > > > Thanks > > Wes > > > > On Feb 24, 2018 7:09 PM, "Siddharth Teotia" > wrote: > > > > Hi All, > > > > We currently have 10 issues in progress and PRs are available for 8 of > > them. In interest of getting a release can

Re: Working towards getting 0.9.0 release candidate up next week

ek. > > Thanks > Wes > > On Feb 24, 2018 7:09 PM, "Siddharth Teotia" wrote: > > Hi All, > > We currently have 10 issues in progress and PRs are available for 8 of > them. In interest of getting a release candidate next week, I would request > people to r

Re: Working towards getting 0.9.0 release candidate up next week

ly have 10 issues in progress and PRs are available for 8 of them. In interest of getting a release candidate next week, I would request people to review PRs as soon as they can to help make progress and close out as many JIRAs as we can. There are 32 issues in TODO list and 25 of them are not yet ass

Re: Working towards getting 0.9.0 release candidate up next week

Hi Sidd, I think we have too many bugs to make an RC this coming week. I suggest we defer to the following week. Thanks Wes On Feb 24, 2018 7:09 PM, "Siddharth Teotia" wrote: Hi All, We currently have 10 issues in progress and PRs are available for 8 of them. In interest of getting

Working towards getting 0.9.0 release candidate up next week

Hi All, We currently have 10 issues in progress and PRs are available for 8 of them. In interest of getting a release candidate next week, I would request people to review PRs as soon as they can to help make progress and close out as many JIRAs as we can. There are 32 issues in TODO list and 25

Cutting 0.4.1 Apache Arrow release candidate later today

Since there were a few moderately serious bugs fixed (regressions from 0.3.0) in the last couple weeks, we are going to cut a bugfix release candidate 0.4.1 based on the master branch later today unless we hear objections otherwise. See JIRAs resolved https://issues.apache.org/jira/issues

Re: release candidate

Good news is I reproduced Jacek's errors. Uwe (in Germany) had the same failures. This was related to a timezone issue. There's some code using the default Timezone. Julian's errors are still a mystery. On Fri, Sep 23, 2016 at 10:49 AM, Julien Le Dem wrote: > Thanks Jacek and Julian, > I'm still

Re: release candidate

Thanks Jacek and Julian, I'm still puzzled by those errors. You also have different errors each. The tests don't fail for me nor travis so we need to figure out what's different in your case. On Thu, Sep 22, 2016 at 12:54 PM, Julian Hyde wrote: > Here’s my zipped vector/target directory: http://

Re: release candidate

Here’s my zipped vector/target directory: http://www.hydromatic.net/vector-target.tar.bz2 > On Sep 20, 2016, at 1:37 PM, Julian Hyde wrote: > > Keys look good now. > > I’m using a different OS X machine today and I can’t reproduce the problem. > The java test suite passes on OS X under JDK

Re: release candidate

ring Apache Spark 2.0 http://bit.ly/mastering-apache-spark Follow me at https://twitter.com/jaceklaskowski On Tue, Sep 20, 2016 at 12:09 AM, Julien Le Dem wrote: > Hi all, > I have published a release candidate for arrow-0.1.0 RC0 > > I don't think it is ready for a vote yet but

Re: release candidate

Keys look good now. I’m using a different OS X machine today and I can’t reproduce the problem. The java test suite passes on OS X under JDK 1.7 and 1.8, and on Ubuntu under JDK 1.8. I’ll send you a tar of java/vector/target when I get back to that particular machine, but I think we can chalk

Re: release candidate

Actually I had updated my fingerprint in ip.apache.org, it just takes time to publish on https://people.apache.org/keys/committer/julien.asc which is now up to date. I have also added my key there: https://dist.apache.org/repos/dist/release/arrow/KEYS For the test failures, possibly it's related t

Re: release candidate

See inline. > On Sep 19, 2016, at 4:25 PM, Julien Le Dem wrote: > > Thanks Julian! > > https://people.apache.org/keys/committer/julien.asc > is my old key. > I forgot how to update this location. Do you know? This, I think: https://www.ap

Re: release candidate

es. Please set BOOST_ROOT to the root > directory containing Boost or BOOST_INCLUDEDIR to the directory > containing > Boost's headers. > > I didn’t try the python build. > > Julian > > > > On Sep 19, 2016, at 3:09 PM, Julien Le Dem wrote: > > &

Re: release candidate

to the root directory containing Boost or BOOST_INCLUDEDIR to the directory containing Boost's headers. I didn’t try the python build. Julian > On Sep 19, 2016, at 3:09 PM, Julien Le Dem wrote: > > Hi all, > I have published a release candidate for arrow-0.1.0 RC0 >

release candidate

Hi all, I have published a release candidate for arrow-0.1.0 RC0 I don't think it is ready for a vote yet but I wanted to test the publication process: The RC0 is here: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.1.0-rc0/ I also have staged maven artifacts (password prot