Sounds good. I will start cranking on this later today and provide an
update tomorrow morning about any progress or issues that arise.
On Mon, Jul 30, 2018 at 11:05 AM Wes McKinney wrote:
> hey Phillip,
>
> I think this is getting too complicated and it's going to hold up the
> release more than
hey Phillip,
I think this is getting too complicated and it's going to hold up the
release more than it already has. How about we cut 0.10.0 binaries
based on the git tag and we try for using a signed tarball for 0.11?
I'm concerned we're going to miss our window this week to get an RC
cut and vot
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 scripts into
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
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
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
this
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 resolved
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.
That sounds great to me. I'll make sure I'm able to build and sign
artifacts this week and surface any issues I find along the way. Looking
forward to a smooth release!
On Tue, Jul 24, 2018 at 11:24 AM Wes McKinney wrote:
> hi folks,
>
> Tuesday's update: it looks like we're going to be able to
hi folks,
Tuesday's update: it looks like we're going to be able to close out
the C++ and Python dev work without any issues before the end of the
week. I'm going to make some tweaks to the website per the JIRAs that
are available but that won't take long.
The two items where there's some uncerta
Wes and Li,
Thanks for your patience, and sorry for the noise! I did have an apache
jira account, but it's been captured by a previous employer. I have
created a new account and I can see the jira page now. Thanks!
Cheers,
Craig
On Mon, Jul 23, 2018 at 10:18 PM Wes McKinney wrote:
> hi Crai
hi Craig -- do you have a JIRA account? I think that page should be
visible to all logged in JIRA users. Let me know if not.
- Wes
On Mon, Jul 23, 2018 at 10:48 PM, Craig Ching wrote:
> Thanks for this, Wes, I appreciate it!
>
> On Mon, Jul 23, 2018 at 8:16 PM Wes McKinney wrote:
>
>> You can a
Thanks for this, Wes, I appreciate it!
On Mon, Jul 23, 2018 at 8:16 PM Wes McKinney wrote:
> You can also have a look at
>
> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.10.0+Release
>
> On Mon, Jul 23, 2018 at 8:40 PM, Li Jin wrote:
> > Craig,
> >
> > If you click the link
> > htt
HI Li,
Sorry, I should have said this originally, but that link leads me to a page
that says "Sorry, you can't view this page"
Cheers,
Craig
On Mon, Jul 23, 2018 at 7:40 PM Li Jin wrote:
> Craig,
>
> If you click the link
> https://issues.apache.org/jira/projects/ARROW/versions/12342562 you ca
You can also have a look at
https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.10.0+Release
On Mon, Jul 23, 2018 at 8:40 PM, Li Jin wrote:
> Craig,
>
> If you click the link
> https://issues.apache.org/jira/projects/ARROW/versions/12342562 you can
> view issues under "issues in progress"
Craig,
If you click the link
https://issues.apache.org/jira/projects/ARROW/versions/12342562 you can
view issues under "issues in progress" and "issues to do"
On Mon, Jul 23, 2018 at 8:30 PM, Craig Ching wrote:
> Hi Li,
>
> Is there a better link to see the 16 issues required for 0.10 to be
> r
Hi Li,
Is there a better link to see the 16 issues required for 0.10 to be
released?
Cheers,
Craig
On Mon, Jul 23, 2018 at 5:47 PM Li Jin wrote:
> Sounds good. I will stand by now.
>
> On Mon, Jul 23, 2018 at 1:40 PM, Wes McKinney wrote:
>
> > hi Li -- thanks. We are working on these issues;
Sounds good. I will stand by now.
On Mon, Jul 23, 2018 at 1:40 PM, Wes McKinney 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
> Website-related, please don't move anything out of the milestone
> wit
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
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:
https://g
25 matches
Mail list logo
