Re: [question] arrow-c-glib examples and references

[Ivan Ogasawara]

Hi @kou,


> How about using Apache Arrow C++ directly instead of using
> Apache Arrow C GLib? You're using C++ to implement your
> language, right? (I think that you need to use C++ to use
> LLVM IR.)
>

As I am not a llvm expert, I asked a friend and he recommended me to use
the C api.
I will try with the Apache Arrow c++ instead! Thank you so much for your
recommendation!


> Apache Arrow C GLib is a wrapper of Apache Arrow C++. So
> there are some overheads. If you can use Apache Arrow C++,
> you should use Apache Arrow C++ directly.
>
> For Apache Arrow data types, see the followings:
>
>   * https://arrow.apache.org/docs/cpp/datatypes.html
>   * https://arrow.apache.org/docs/cpp/api/datatype.html#factory-functions


got it. thank you so much for these references, I will check that out!

> thanks, it looks very helpful. if anyone could guide me, maybe I could
> help
> > with the apache arrow c glib cookbook. that would be a very nice way to
> > learn more about that.
>
> Thanks! But I think that you don't need to use Apache Arrow
> C GLib...
>

that sounds great! hope to have some updates soon about that :)

Again, thank you so much for your attention and all the recommendations.

Ivan (@xmnlab)

cpp: Debugging 'plan destruction before finishing'

[Ivan Chau]

Hi all,

I've been encountering a "plan destruction before finishing" output
occurring with the AsOfJoin node, particularly when joining large tables.

My execution context is configured with the default memory pool and a
nullptr for the executor. I am calling StartAndCollect

to execute the plan.

After some quick debugging, I found that the asof node's StopProducing (a
conditioning necessary to finish the plan) is called shortly after the
error output.

What cases would cause the plan to destruct before its nodes finish?

Re: cpp: Debugging 'plan destruction before finishing'

[Weston Pace]

> After some quick debugging, I found that the asof node's StopProducing (a
conditioning necessary to finish the plan) is called shortly after the
error output.

StopProducing should probably more accurately be named "Abort" or
"StopRightNow".  If you run the plan to completion normally I do not
believe you should see this getting called.

> What cases would cause the plan to destruct before its nodes finish?

This may be a chicken/egg problem but destroying a plan before it has
finished will cause this (the destructor panics and, in a probably
futile attempt, calls StopProducing in hopes it can stop the ongoing
plan before a segmentation fault since any ongoing task is going to
assume the plan is still alive and valid).

StartAndCollect returns a future.  Are you sure you are keeping the
exec plan alive / in scope until that future completes?  Can you share
the code that is calling StartAndCollect?

An error that is unhandled and reaches a sink (since there are no
nodes that "handle errors" today this means any error) will also
trigger a call to StopProducing.  So if the AsofJoinNode is calling
ErrorReceived on its output then that would be a potential cause.  You
can probably check for this condition with a debugger.

On Thu, Jul 14, 2022 at 9:07 AM Ivan Chau  wrote:
>
> Hi all,
>
> I've been encountering a "plan destruction before finishing" output
> occurring with the AsOfJoin node, particularly when joining large tables.
>
> My execution context is configured with the default memory pool and a
> nullptr for the executor. I am calling StartAndCollect
> 
> to execute the plan.
>
> After some quick debugging, I found that the asof node's StopProducing (a
> conditioning necessary to finish the plan) is called shortly after the
> error output.
>
> What cases would cause the plan to destruct before its nodes finish?

Re: [Go][Release][Discussion] Patch release for Go libraries to address CVE-2022-28948

[Sutou Kouhei]

Hi,

It seems that there are no objections for this release plan.

I've prepared 6.0.2, 7.0.1 and 8.0.1. I'll start votes for
them.

Thanks,
-- 
kou

In <20220708.110101.1989678110062934069@clear-code.com>
  "Re: [Go][Release][Discussion] Patch release for Go libraries to address 
CVE-2022-28948" on Fri, 08 Jul 2022 11:01:01 +0900 (JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> It seems that there are no objections for these patch releases.
> 
> I'll initiate these patch releases. Here is my plan. If
> there are any objections/concerns, please share them.
> 
>   * We'll release 6.0.2, 7.0.1 and 8.0.1
>   * These releases only include
> https://github.com/apache/arrow/pull/13322
>   * We'll create apache-arrow-6.0.2.tar.gz,
> apache-arrow-7.0.1.tar.gz and
> apache-arrow-8.0.1.tar.gz as usual
>   * These tar.gz include not only go/ but also all languages
> in apache/arrow to reuse the current release script
>   * We'll not create binary artifacts for 6.0.2, 7.0.1 and
> 8.0.1 because we don't have binary artifacts relate to Go
>   * We'll start votes for releasing 6.0.2, 7.0.1 and 8.0.1
> 
> 
> Thanks,
> -- 
> kou
> 
> In 
>   "Re: [Go][Release][Discussion] Patch release for Go libraries to address 
> CVE-2022-28948" on Mon, 13 Jun 2022 19:24:16 -0400,
>   Matt Topol  wrote:
> 
>>>  I'm also not an expert but I think that we need to "release"
>>> (vote) a patch version. (I think that just doing "git tag"
>>> isn't suitable.)
>> 
>> I was figuring there would need to be a vote, and as I'm not part of the
>> PMC I didn't know whether it was my place to attempt to call such a vote.
>> :) Would we need three separate votes? (One for v6.0.2, v.7.0.1, and one
>> for v8.0.1)
>> 
>>> We can't mark 8.0.1 as official unless we "release" 8.0.1.
>> 
>> Can we *just* "release" the Go patch releases (like the arrow-rs rust
>> library seems to be doing)? Or do we need to fully release all the
>> languages for consistency (which is what I assume is the case)?
>> 
>>> Again, I'm also not an expert. I hope that others comment on
>>> this too.
>> 
>> Same. This isn't exactly something I can pretend to be very familiar with
>> particularly as a policy decision. Hopefully others will comment and
>> respond to this.
>> 
>> --Matt
>> 
>> On Sun, Jun 12, 2022 at 10:06 PM Sutou Kouhei  wrote:
>> 
>>> Hi,
>>>
>>> I'm also not an expert but I think that we need to "release"
>>> (vote) a patch version. (I think that just doing "git tag"
>>> isn't suitable.)
>>>
>>> Because we need to "release" to announce users to use
>>> "go/v8.0.1" rather than "go/v8.0.0":
>>>
>>> https://www.apache.org/legal/release-policy.html#publication
>>>
>>> > Projects SHALL publish official releases and SHALL NOT
>>> > publish unreleased materials outside the development
>>> > community.
>>>
>>> We can't mark 8.0.1 as official unless we "release" 8.0.1.
>>>
>>> (I understand that Go doesn't need released materials. Go
>>> just needs a Git tag. I understand that the ASF's release
>>> policy isn't suitable for recent languages such as Go and
>>> Julia. Micah started a discussion it in another place. The
>>> ASF's release policy may be updated in future.)
>>>
>>>
>>> But we don't need to release binary artifacts because we
>>> don't have any binary artifacts for Go. We can just release
>>> a source archive for patch releases of this.
>>>
>>>
>>> Again, I'm also not an expert. I hope that others comment on
>>> this too.
>>>
>>>
>>> Thanks,
>>> --
>>> kou
>>>
>>> In 
>>>   "Re: [Go][Release][Discussion] Patch release for Go libraries to address
>>> CVE-2022-28948" on Fri, 10 Jun 2022 11:43:26 -0400,
>>>   Neal Richardson  wrote:
>>>
>>> > Personally, I don't have a problem with doing `git tag` just for Go. I
>>> > don't think this needs a full patch release process since we aren't
>>> > producing new artifacts that need signing, we're only adding a tag that
>>> > points to a SHA in git. But I am not an expert in this area of policy and
>>> > will defer to others who know better.
>>> >
>>> > Neal
>>> >
>>> >
>>> > On Fri, Jun 10, 2022 at 11:07 AM Matt Topol 
>>> wrote:
>>> >
>>> >> I've merged the PR to master and want to propose cherry-picking it to
>>> >> create patch releases. Technically, for Go, all we need to do is create
>>> the
>>> >> appropriate tags named like "go/v6.0.2", and so on. Since this
>>> >> vulnerability only affects Go we don't necessarily need to release
>>> patches
>>> >> for the other language libraries other than for consistency.
>>> >>
>>> >> So I guess I'd like others to chime in on opinions as to whether we
>>> should
>>> >> just cherry-pick and create the tags just for patch releases for Go or
>>> do
>>> >> full patch releases of everything for consistency.
>>> >>
>>> >> --Matt
>>> >>
>>> >> On Thu, Jun 9, 2022 at 5:21 PM Dominic Barnes
>>> >> >> >
>>> >> wrote:
>>> >>
>>> >> > Howdy!
>>> >> >
>>> >> > I'm a first-time contributor, and I just opened a PR to update a
>>> dev/test
>>> >> > dependency (github.com/stretchr

[VOTE] Release Apache Arrow 6.0.2 - RC0

[Sutou Kouhei]

Hi,

I would like to propose the following release candidate
(RC0) of Apache Arrow version 6.0.2. This is a release
consisting of 1 resolved JIRA issues[1].

This is one of releases[2] that focus on a Go related
security vulnerability[3]. We don't publish binary artifacts
of this release because we don't have Go related binaries.

This release candidate is based on commit:
3ea5af64865f9910d3c98162c7949af8d63ec68e [4]

The source release rc0 is hosted at [5].
The changelog is located at [6].

Please download, verify checksums and signatures, run the
unit tests, and vote on the release. See [7] for how to
validate a release candidate. But you need to verify only Go
related tests because this release candidate only includes a
change for Go. So we can use the following command line:

TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 6.0.2 0

The vote will be open for at least 72 hours.

[ ] +1 Release this as Apache Arrow 6.0.2
[ ] +0
[ ] -1 Do not release this as Apache Arrow 6.0.2 because...

[1]: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%206.0.2
[2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
[3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
[4]: 
https://github.com/apache/arrow/tree/3ea5af64865f9910d3c98162c7949af8d63ec68e
[5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-6.0.2-rc0
[6]: 
https://github.com/apache/arrow/blob/3ea5af64865f9910d3c98162c7949af8d63ec68e/CHANGELOG.md
[7]: 
https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

[VOTE] Release Apache Arrow 8.0.1 - RC0

[Sutou Kouhei]

Hi,

I would like to propose the following release candidate
(RC0) of Apache Arrow version 8.0.1. This is a release
consisting of 1 resolved JIRA issues[1].

This is one of releases[2] that focus on a Go related
security vulnerability[3]. We don't publish binary artifacts
of this release because we don't have Go related binaries.

This release candidate is based on commit:
9966c39583f1e203bac9200753e9db32478d43a6 [4]

The source release rc0 is hosted at [5].
The changelog is located at [6].

Please download, verify checksums and signatures, run the
unit tests, and vote on the release. See [7] for how to
validate a release candidate. But you need to verify only Go
related tests because this release candidate only includes a
change for Go. So we can use the following command line:

TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 8.0.1 0

The vote will be open for at least 72 hours.

[ ] +1 Release this as Apache Arrow 8.0.1
[ ] +0
[ ] -1 Do not release this as Apache Arrow 8.0.1 because...

[1]: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%208.0.1
[2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
[3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
[4]: 
https://github.com/apache/arrow/tree/9966c39583f1e203bac9200753e9db32478d43a6
[5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-8.0.1-rc0
[6]: 
https://github.com/apache/arrow/blob/9966c39583f1e203bac9200753e9db32478d43a6/CHANGELOG.md
[7]: 
https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

[VOTE] Release Apache Arrow 7.0.1 - RC0

[Sutou Kouhei]

Hi,

I would like to propose the following release candidate
(RC0) of Apache Arrow version 7.0.1. This is a release
consisting of 1 resolved JIRA issues[1].

This is one of releases[2] that focus on a Go related
security vulnerability[3]. We don't publish binary artifacts
of this release because we don't have Go related binaries.

This release candidate is based on commit:
072ae55dc8172bb1a898fda5d5a83ec063b05a6d [4]

The source release rc0 is hosted at [5].
The changelog is located at [6].

Please download, verify checksums and signatures, run the
unit tests, and vote on the release. See [7] for how to
validate a release candidate. But you need to verify only Go
related tests because this release candidate only includes a
change for Go. So we can use the following command line:

TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 7.0.1 0

The vote will be open for at least 72 hours.

[ ] +1 Release this as Apache Arrow 7.0.1
[ ] +0
[ ] -1 Do not release this as Apache Arrow 7.0.1 because...

[1]: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%207.0.1
[2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
[3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
[4]: 
https://github.com/apache/arrow/tree/072ae55dc8172bb1a898fda5d5a83ec063b05a6d
[5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-7.0.1-rc0
[6]: 
https://github.com/apache/arrow/blob/072ae55dc8172bb1a898fda5d5a83ec063b05a6d/CHANGELOG.md
[7]: 
https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Re: [VOTE] Release Apache Arrow 6.0.2 - RC0

[Sutou Kouhei]

FYI: Here are verification results on GitHub Actions:
https://github.com/apache/arrow/pull/13603#issuecomment-1183912949

In <20220715.061031.728260673372395082@clear-code.com>
  "[VOTE] Release Apache Arrow 6.0.2 - RC0" on Fri, 15 Jul 2022 06:10:31 +0900 
(JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> I would like to propose the following release candidate
> (RC0) of Apache Arrow version 6.0.2. This is a release
> consisting of 1 resolved JIRA issues[1].
> 
> This is one of releases[2] that focus on a Go related
> security vulnerability[3]. We don't publish binary artifacts
> of this release because we don't have Go related binaries.
> 
> This release candidate is based on commit:
> 3ea5af64865f9910d3c98162c7949af8d63ec68e [4]
> 
> The source release rc0 is hosted at [5].
> The changelog is located at [6].
> 
> Please download, verify checksums and signatures, run the
> unit tests, and vote on the release. See [7] for how to
> validate a release candidate. But you need to verify only Go
> related tests because this release candidate only includes a
> change for Go. So we can use the following command line:
> 
> TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 6.0.2 0
> 
> The vote will be open for at least 72 hours.
> 
> [ ] +1 Release this as Apache Arrow 6.0.2
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow 6.0.2 because...
> 
> [1]: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%206.0.2
> [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> [4]: 
> https://github.com/apache/arrow/tree/3ea5af64865f9910d3c98162c7949af8d63ec68e
> [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-6.0.2-rc0
> [6]: 
> https://github.com/apache/arrow/blob/3ea5af64865f9910d3c98162c7949af8d63ec68e/CHANGELOG.md
> [7]: 
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Re: [VOTE] Release Apache Arrow 7.0.1 - RC0

[Sutou Kouhei]

FYI: Here are verification results on GitHub Actions:
https://github.com/apache/arrow/pull/13607#issuecomment-1184118112

In <20220715.061039.1868304737470784647@clear-code.com>
  "[VOTE] Release Apache Arrow 7.0.1 - RC0" on Fri, 15 Jul 2022 06:10:39 +0900 
(JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> I would like to propose the following release candidate
> (RC0) of Apache Arrow version 7.0.1. This is a release
> consisting of 1 resolved JIRA issues[1].
> 
> This is one of releases[2] that focus on a Go related
> security vulnerability[3]. We don't publish binary artifacts
> of this release because we don't have Go related binaries.
> 
> This release candidate is based on commit:
> 072ae55dc8172bb1a898fda5d5a83ec063b05a6d [4]
> 
> The source release rc0 is hosted at [5].
> The changelog is located at [6].
> 
> Please download, verify checksums and signatures, run the
> unit tests, and vote on the release. See [7] for how to
> validate a release candidate. But you need to verify only Go
> related tests because this release candidate only includes a
> change for Go. So we can use the following command line:
> 
> TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 7.0.1 0
> 
> The vote will be open for at least 72 hours.
> 
> [ ] +1 Release this as Apache Arrow 7.0.1
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow 7.0.1 because...
> 
> [1]: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%207.0.1
> [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> [4]: 
> https://github.com/apache/arrow/tree/072ae55dc8172bb1a898fda5d5a83ec063b05a6d
> [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-7.0.1-rc0
> [6]: 
> https://github.com/apache/arrow/blob/072ae55dc8172bb1a898fda5d5a83ec063b05a6d/CHANGELOG.md
> [7]: 
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Re: [VOTE] Release Apache Arrow 8.0.1 - RC0

[Sutou Kouhei]

FYI: Here are verification results on GitHub Actions:
https://github.com/apache/arrow/pull/13604#issuecomment-1183937088

In <20220715.061057.1116573445635493266@clear-code.com>
  "[VOTE] Release Apache Arrow 8.0.1 - RC0" on Fri, 15 Jul 2022 06:10:57 +0900 
(JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> I would like to propose the following release candidate
> (RC0) of Apache Arrow version 8.0.1. This is a release
> consisting of 1 resolved JIRA issues[1].
> 
> This is one of releases[2] that focus on a Go related
> security vulnerability[3]. We don't publish binary artifacts
> of this release because we don't have Go related binaries.
> 
> This release candidate is based on commit:
> 9966c39583f1e203bac9200753e9db32478d43a6 [4]
> 
> The source release rc0 is hosted at [5].
> The changelog is located at [6].
> 
> Please download, verify checksums and signatures, run the
> unit tests, and vote on the release. See [7] for how to
> validate a release candidate. But you need to verify only Go
> related tests because this release candidate only includes a
> change for Go. So we can use the following command line:
> 
> TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 8.0.1 0
> 
> The vote will be open for at least 72 hours.
> 
> [ ] +1 Release this as Apache Arrow 8.0.1
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow 8.0.1 because...
> 
> [1]: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%208.0.1
> [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> [4]: 
> https://github.com/apache/arrow/tree/9966c39583f1e203bac9200753e9db32478d43a6
> [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-8.0.1-rc0
> [6]: 
> https://github.com/apache/arrow/blob/9966c39583f1e203bac9200753e9db32478d43a6/CHANGELOG.md
> [7]: 
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Re: [VOTE] Release Apache Arrow 6.0.2 - RC0

[Sutou Kouhei]

+1

I ran the followings on Debian GNU/Linux sid:

  * TEST_DEFAULT=0 \
  TEST_GO=1 \
  dev/release/verify-release-candidate.sh 6.0.2 0

with:

  * go version go1.18.3 linux/amd64


Thanks,
-- 
kou

In <20220715.061031.728260673372395082@clear-code.com>
  "[VOTE] Release Apache Arrow 6.0.2 - RC0" on Fri, 15 Jul 2022 06:10:31 +0900 
(JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> I would like to propose the following release candidate
> (RC0) of Apache Arrow version 6.0.2. This is a release
> consisting of 1 resolved JIRA issues[1].
> 
> This is one of releases[2] that focus on a Go related
> security vulnerability[3]. We don't publish binary artifacts
> of this release because we don't have Go related binaries.
> 
> This release candidate is based on commit:
> 3ea5af64865f9910d3c98162c7949af8d63ec68e [4]
> 
> The source release rc0 is hosted at [5].
> The changelog is located at [6].
> 
> Please download, verify checksums and signatures, run the
> unit tests, and vote on the release. See [7] for how to
> validate a release candidate. But you need to verify only Go
> related tests because this release candidate only includes a
> change for Go. So we can use the following command line:
> 
> TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 6.0.2 0
> 
> The vote will be open for at least 72 hours.
> 
> [ ] +1 Release this as Apache Arrow 6.0.2
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow 6.0.2 because...
> 
> [1]: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%206.0.2
> [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> [4]: 
> https://github.com/apache/arrow/tree/3ea5af64865f9910d3c98162c7949af8d63ec68e
> [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-6.0.2-rc0
> [6]: 
> https://github.com/apache/arrow/blob/3ea5af64865f9910d3c98162c7949af8d63ec68e/CHANGELOG.md
> [7]: 
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Re: [VOTE] Release Apache Arrow 7.0.1 - RC0

[Sutou Kouhei]

+1

I ran the followings on Debian GNU/Linux sid:

  * TEST_DEFAULT=0 \
  TEST_GO=1 \
  dev/release/verify-release-candidate.sh 7.0.1 0

with:

  * go version go1.17.11 linux/amd64


Thanks,
-- 
kou

In <20220715.061039.1868304737470784647@clear-code.com>
  "[VOTE] Release Apache Arrow 7.0.1 - RC0" on Fri, 15 Jul 2022 06:10:39 +0900 
(JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> I would like to propose the following release candidate
> (RC0) of Apache Arrow version 7.0.1. This is a release
> consisting of 1 resolved JIRA issues[1].
> 
> This is one of releases[2] that focus on a Go related
> security vulnerability[3]. We don't publish binary artifacts
> of this release because we don't have Go related binaries.
> 
> This release candidate is based on commit:
> 072ae55dc8172bb1a898fda5d5a83ec063b05a6d [4]
> 
> The source release rc0 is hosted at [5].
> The changelog is located at [6].
> 
> Please download, verify checksums and signatures, run the
> unit tests, and vote on the release. See [7] for how to
> validate a release candidate. But you need to verify only Go
> related tests because this release candidate only includes a
> change for Go. So we can use the following command line:
> 
> TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 7.0.1 0
> 
> The vote will be open for at least 72 hours.
> 
> [ ] +1 Release this as Apache Arrow 7.0.1
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow 7.0.1 because...
> 
> [1]: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%207.0.1
> [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> [4]: 
> https://github.com/apache/arrow/tree/072ae55dc8172bb1a898fda5d5a83ec063b05a6d
> [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-7.0.1-rc0
> [6]: 
> https://github.com/apache/arrow/blob/072ae55dc8172bb1a898fda5d5a83ec063b05a6d/CHANGELOG.md
> [7]: 
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Re: [VOTE] Release Apache Arrow 8.0.1 - RC0

[Sutou Kouhei]

+1

I ran the followings on Debian GNU/Linux sid:

  * TEST_DEFAULT=0 \
  TEST_GO=1 \
  dev/release/verify-release-candidate.sh 8.0.1 0

with:

  * go version go1.18.3 linux/amd64


Thanks,
-- 
kou

In <20220715.061057.1116573445635493266@clear-code.com>
  "[VOTE] Release Apache Arrow 8.0.1 - RC0" on Fri, 15 Jul 2022 06:10:57 +0900 
(JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> I would like to propose the following release candidate
> (RC0) of Apache Arrow version 8.0.1. This is a release
> consisting of 1 resolved JIRA issues[1].
> 
> This is one of releases[2] that focus on a Go related
> security vulnerability[3]. We don't publish binary artifacts
> of this release because we don't have Go related binaries.
> 
> This release candidate is based on commit:
> 9966c39583f1e203bac9200753e9db32478d43a6 [4]
> 
> The source release rc0 is hosted at [5].
> The changelog is located at [6].
> 
> Please download, verify checksums and signatures, run the
> unit tests, and vote on the release. See [7] for how to
> validate a release candidate. But you need to verify only Go
> related tests because this release candidate only includes a
> change for Go. So we can use the following command line:
> 
> TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 8.0.1 0
> 
> The vote will be open for at least 72 hours.
> 
> [ ] +1 Release this as Apache Arrow 8.0.1
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow 8.0.1 because...
> 
> [1]: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%208.0.1
> [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> [4]: 
> https://github.com/apache/arrow/tree/9966c39583f1e203bac9200753e9db32478d43a6
> [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-8.0.1-rc0
> [6]: 
> https://github.com/apache/arrow/blob/9966c39583f1e203bac9200753e9db32478d43a6/CHANGELOG.md
> [7]: 
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Re: [VOTE] Release Apache Arrow 6.0.2 - RC0

[Neal Richardson]

+1. Thank you for doing this, Kou.

Neal

On Thu, Jul 14, 2022 at 5:15 PM Sutou Kouhei  wrote:

> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
>   * TEST_DEFAULT=0 \
>   TEST_GO=1 \
>   dev/release/verify-release-candidate.sh 6.0.2 0
>
> with:
>
>   * go version go1.18.3 linux/amd64
>
>
> Thanks,
> --
> kou
>
> In <20220715.061031.728260673372395082@clear-code.com>
>   "[VOTE] Release Apache Arrow 6.0.2 - RC0" on Fri, 15 Jul 2022 06:10:31
> +0900 (JST),
>   Sutou Kouhei  wrote:
>
> > Hi,
> >
> > I would like to propose the following release candidate
> > (RC0) of Apache Arrow version 6.0.2. This is a release
> > consisting of 1 resolved JIRA issues[1].
> >
> > This is one of releases[2] that focus on a Go related
> > security vulnerability[3]. We don't publish binary artifacts
> > of this release because we don't have Go related binaries.
> >
> > This release candidate is based on commit:
> > 3ea5af64865f9910d3c98162c7949af8d63ec68e [4]
> >
> > The source release rc0 is hosted at [5].
> > The changelog is located at [6].
> >
> > Please download, verify checksums and signatures, run the
> > unit tests, and vote on the release. See [7] for how to
> > validate a release candidate. But you need to verify only Go
> > related tests because this release candidate only includes a
> > change for Go. So we can use the following command line:
> >
> > TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh
> 6.0.2 0
> >
> > The vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this as Apache Arrow 6.0.2
> > [ ] +0
> > [ ] -1 Do not release this as Apache Arrow 6.0.2 because...
> >
> > [1]:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%206.0.2
> > [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> > [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> > [4]:
> https://github.com/apache/arrow/tree/3ea5af64865f9910d3c98162c7949af8d63ec68e
> > [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-6.0.2-rc0
> > [6]:
> https://github.com/apache/arrow/blob/3ea5af64865f9910d3c98162c7949af8d63ec68e/CHANGELOG.md
> > [7]:
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
>

Re: [VOTE] Release Apache Arrow 7.0.1 - RC0

[Neal Richardson]

+1

Neal

On Thu, Jul 14, 2022 at 5:16 PM Sutou Kouhei  wrote:

> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
>   * TEST_DEFAULT=0 \
>   TEST_GO=1 \
>   dev/release/verify-release-candidate.sh 7.0.1 0
>
> with:
>
>   * go version go1.17.11 linux/amd64
>
>
> Thanks,
> --
> kou
>
> In <20220715.061039.1868304737470784647@clear-code.com>
>   "[VOTE] Release Apache Arrow 7.0.1 - RC0" on Fri, 15 Jul 2022 06:10:39
> +0900 (JST),
>   Sutou Kouhei  wrote:
>
> > Hi,
> >
> > I would like to propose the following release candidate
> > (RC0) of Apache Arrow version 7.0.1. This is a release
> > consisting of 1 resolved JIRA issues[1].
> >
> > This is one of releases[2] that focus on a Go related
> > security vulnerability[3]. We don't publish binary artifacts
> > of this release because we don't have Go related binaries.
> >
> > This release candidate is based on commit:
> > 072ae55dc8172bb1a898fda5d5a83ec063b05a6d [4]
> >
> > The source release rc0 is hosted at [5].
> > The changelog is located at [6].
> >
> > Please download, verify checksums and signatures, run the
> > unit tests, and vote on the release. See [7] for how to
> > validate a release candidate. But you need to verify only Go
> > related tests because this release candidate only includes a
> > change for Go. So we can use the following command line:
> >
> > TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh
> 7.0.1 0
> >
> > The vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this as Apache Arrow 7.0.1
> > [ ] +0
> > [ ] -1 Do not release this as Apache Arrow 7.0.1 because...
> >
> > [1]:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%207.0.1
> > [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> > [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> > [4]:
> https://github.com/apache/arrow/tree/072ae55dc8172bb1a898fda5d5a83ec063b05a6d
> > [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-7.0.1-rc0
> > [6]:
> https://github.com/apache/arrow/blob/072ae55dc8172bb1a898fda5d5a83ec063b05a6d/CHANGELOG.md
> > [7]:
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
>

Re: [VOTE] Release Apache Arrow 8.0.1 - RC0

[Neal Richardson]

+1

Neal

On Thu, Jul 14, 2022 at 5:17 PM Sutou Kouhei  wrote:

> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
>   * TEST_DEFAULT=0 \
>   TEST_GO=1 \
>   dev/release/verify-release-candidate.sh 8.0.1 0
>
> with:
>
>   * go version go1.18.3 linux/amd64
>
>
> Thanks,
> --
> kou
>
> In <20220715.061057.1116573445635493266@clear-code.com>
>   "[VOTE] Release Apache Arrow 8.0.1 - RC0" on Fri, 15 Jul 2022 06:10:57
> +0900 (JST),
>   Sutou Kouhei  wrote:
>
> > Hi,
> >
> > I would like to propose the following release candidate
> > (RC0) of Apache Arrow version 8.0.1. This is a release
> > consisting of 1 resolved JIRA issues[1].
> >
> > This is one of releases[2] that focus on a Go related
> > security vulnerability[3]. We don't publish binary artifacts
> > of this release because we don't have Go related binaries.
> >
> > This release candidate is based on commit:
> > 9966c39583f1e203bac9200753e9db32478d43a6 [4]
> >
> > The source release rc0 is hosted at [5].
> > The changelog is located at [6].
> >
> > Please download, verify checksums and signatures, run the
> > unit tests, and vote on the release. See [7] for how to
> > validate a release candidate. But you need to verify only Go
> > related tests because this release candidate only includes a
> > change for Go. So we can use the following command line:
> >
> > TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh
> 8.0.1 0
> >
> > The vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this as Apache Arrow 8.0.1
> > [ ] +0
> > [ ] -1 Do not release this as Apache Arrow 8.0.1 because...
> >
> > [1]:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%208.0.1
> > [2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
> > [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
> > [4]:
> https://github.com/apache/arrow/tree/9966c39583f1e203bac9200753e9db32478d43a6
> > [5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-8.0.1-rc0
> > [6]:
> https://github.com/apache/arrow/blob/9966c39583f1e203bac9200753e9db32478d43a6/CHANGELOG.md
> > [7]:
> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
>

RE: [VOTE] Release Apache Arrow 8.0.1 - RC0

[Yibo Cai]

+1, verified on arm64

-Original Message-
From: Sutou Kouhei 
Sent: Friday, July 15, 2022 5:11 AM
To: dev@arrow.apache.org
Subject: [VOTE] Release Apache Arrow 8.0.1 - RC0

Hi,

I would like to propose the following release candidate
(RC0) of Apache Arrow version 8.0.1. This is a release consisting of 1 resolved 
JIRA issues[1].

This is one of releases[2] that focus on a Go related security 
vulnerability[3]. We don't publish binary artifacts of this release because we 
don't have Go related binaries.

This release candidate is based on commit:
9966c39583f1e203bac9200753e9db32478d43a6 [4]

The source release rc0 is hosted at [5].
The changelog is located at [6].

Please download, verify checksums and signatures, run the unit tests, and vote 
on the release. See [7] for how to validate a release candidate. But you need 
to verify only Go related tests because this release candidate only includes a 
change for Go. So we can use the following command line:

TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 8.0.1 0

The vote will be open for at least 72 hours.

[ ] +1 Release this as Apache Arrow 8.0.1 [ ] +0 [ ] -1 Do not release this as 
Apache Arrow 8.0.1 because...

[1]: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%208.0.1
[2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
[3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
[4]: 
https://github.com/apache/arrow/tree/9966c39583f1e203bac9200753e9db32478d43a6
[5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-8.0.1-rc0
[6]: 
https://github.com/apache/arrow/blob/9966c39583f1e203bac9200753e9db32478d43a6/CHANGELOG.md
[7]: 
https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

RE: [VOTE] Release Apache Arrow 7.0.1 - RC0

[Yibo Cai]

+1, verified on arm64

-Original Message-
From: Sutou Kouhei 
Sent: Friday, July 15, 2022 5:11 AM
To: dev@arrow.apache.org
Subject: [VOTE] Release Apache Arrow 7.0.1 - RC0

Hi,

I would like to propose the following release candidate
(RC0) of Apache Arrow version 7.0.1. This is a release consisting of 1 resolved 
JIRA issues[1].

This is one of releases[2] that focus on a Go related security 
vulnerability[3]. We don't publish binary artifacts of this release because we 
don't have Go related binaries.

This release candidate is based on commit:
072ae55dc8172bb1a898fda5d5a83ec063b05a6d [4]

The source release rc0 is hosted at [5].
The changelog is located at [6].

Please download, verify checksums and signatures, run the unit tests, and vote 
on the release. See [7] for how to validate a release candidate. But you need 
to verify only Go related tests because this release candidate only includes a 
change for Go. So we can use the following command line:

TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 7.0.1 0

The vote will be open for at least 72 hours.

[ ] +1 Release this as Apache Arrow 7.0.1 [ ] +0 [ ] -1 Do not release this as 
Apache Arrow 7.0.1 because...

[1]: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%207.0.1
[2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
[3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
[4]: 
https://github.com/apache/arrow/tree/072ae55dc8172bb1a898fda5d5a83ec063b05a6d
[5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-7.0.1-rc0
[6]: 
https://github.com/apache/arrow/blob/072ae55dc8172bb1a898fda5d5a83ec063b05a6d/CHANGELOG.md
[7]: 
https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

RE: [VOTE] Release Apache Arrow 6.0.2 - RC0

[Yibo Cai]

+1, verified on arm64

-Original Message-
From: Sutou Kouhei 
Sent: Friday, July 15, 2022 5:11 AM
To: dev@arrow.apache.org
Subject: [VOTE] Release Apache Arrow 6.0.2 - RC0

Hi,

I would like to propose the following release candidate
(RC0) of Apache Arrow version 6.0.2. This is a release consisting of 1 resolved 
JIRA issues[1].

This is one of releases[2] that focus on a Go related security 
vulnerability[3]. We don't publish binary artifacts of this release because we 
don't have Go related binaries.

This release candidate is based on commit:
3ea5af64865f9910d3c98162c7949af8d63ec68e [4]

The source release rc0 is hosted at [5].
The changelog is located at [6].

Please download, verify checksums and signatures, run the unit tests, and vote 
on the release. See [7] for how to validate a release candidate. But you need 
to verify only Go related tests because this release candidate only includes a 
change for Go. So we can use the following command line:

TEST_DEFAULT=0 TEST_GO=1 dev/release/verify-release-candidate.sh 6.0.2 0

The vote will be open for at least 72 hours.

[ ] +1 Release this as Apache Arrow 6.0.2 [ ] +0 [ ] -1 Do not release this as 
Apache Arrow 6.0.2 because...

[1]: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%206.0.2
[2] https://lists.apache.org/thread/qkkzpvmxc0coqhdkc1qoygwy6h4v5sgn
[3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948
[4]: 
https://github.com/apache/arrow/tree/3ea5af64865f9910d3c98162c7949af8d63ec68e
[5]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-6.0.2-rc0
[6]: 
https://github.com/apache/arrow/blob/3ea5af64865f9910d3c98162c7949af8d63ec68e/CHANGELOG.md
[7]: 
https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

Re: [VOTE][RUST][DataFusion] Release Apache Arrow DataFusion 10.0.0 RC1

[Neville Dipale]

+1 (binding)

There are 3 test failures because the hardcoded strings expect
"ARROW_TEST_DATA" but we get "privateARROW_TEST_DATA"
when verifying the RC.

An example can be seen on this diff https://www.diffchecker.com/B8i8w4GC.

My conclusion from looking at it is that it's likely a quirk that we can
fix, but shouldn't affect the release.

On Wed, 13 Jul 2022 at 23:48, QP Hou  wrote:

> +1 (binding)
>
> On Wed, Jul 13, 2022 at 1:24 PM Andrew Lamb  wrote:
> >
> > +1 (binding)
> >
> > Thanks Andy! I know releases are a significant amount of work.
> >
> > Andrew
> >
> > On Tue, Jul 12, 2022 at 11:45 AM Andy Grove 
> wrote:
> >
> > > Hi,
> > >
> > > I would like to propose a release of Apache Arrow DataFusion
> > > Implementation,
> > > version 10.0.0.
> > >
> > > This release candidate is based on commit:
> > > d25e822c1ef85ee7c0297b4b38d05a51b0d2e46f [1]
> > > The proposed release tarball and signatures are hosted at [2].
> > > The changelog is located at [3].
> > >
> > > Please download, verify checksums and signatures, run the unit tests,
> and
> > > vote
> > > on the release. The vote will be open for at least 72 hours.
> > >
> > > Only votes from PMC members are binding, but all members of the
> community
> > > are
> > > encouraged to test the release and vote with "(non-binding)".
> > >
> > > The standard verification procedure is documented at
> > >
> > >
> https://github.com/apache/arrow-datafusion/blob/master/dev/release/README.md#verifying-release-candidates
> > > .
> > >
> > > [ ] +1 Release this as Apache Arrow DataFusion 10.0.0
> > > [ ] +0
> > > [ ] -1 Do not release this as Apache Arrow DataFusion 10.0.0 because...
> > >
> > > Here is my vote:
> > >
> > > +1
> > >
> > > [1]:
> > >
> > >
> https://github.com/apache/arrow-datafusion/tree/d25e822c1ef85ee7c0297b4b38d05a51b0d2e46f
> > > [2]:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-datafusion-10.0.0-rc1
> > > [3]:
> > >
> > >
> https://github.com/apache/arrow-datafusion/blob/d25e822c1ef85ee7c0297b4b38d05a51b0d2e46f/CHANGELOG.md
> > >
>

Re: [VOTE][RUST][DataFusion] Release Apache Arrow DataFusion 10.0.0 RC1

[Neville Dipale]

I've logged https://github.com/apache/arrow-datafusion/issues/2916

On Fri, 15 Jul 2022 at 08:34, Neville Dipale  wrote:

> +1 (binding)
>
> There are 3 test failures because the hardcoded strings expect
> "ARROW_TEST_DATA" but we get "privateARROW_TEST_DATA"
> when verifying the RC.
>
> An example can be seen on this diff https://www.diffchecker.com/B8i8w4GC.
>
> My conclusion from looking at it is that it's likely a quirk that we can
> fix, but shouldn't affect the release.
>
> On Wed, 13 Jul 2022 at 23:48, QP Hou  wrote:
>
>> +1 (binding)
>>
>> On Wed, Jul 13, 2022 at 1:24 PM Andrew Lamb  wrote:
>> >
>> > +1 (binding)
>> >
>> > Thanks Andy! I know releases are a significant amount of work.
>> >
>> > Andrew
>> >
>> > On Tue, Jul 12, 2022 at 11:45 AM Andy Grove 
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > I would like to propose a release of Apache Arrow DataFusion
>> > > Implementation,
>> > > version 10.0.0.
>> > >
>> > > This release candidate is based on commit:
>> > > d25e822c1ef85ee7c0297b4b38d05a51b0d2e46f [1]
>> > > The proposed release tarball and signatures are hosted at [2].
>> > > The changelog is located at [3].
>> > >
>> > > Please download, verify checksums and signatures, run the unit tests,
>> and
>> > > vote
>> > > on the release. The vote will be open for at least 72 hours.
>> > >
>> > > Only votes from PMC members are binding, but all members of the
>> community
>> > > are
>> > > encouraged to test the release and vote with "(non-binding)".
>> > >
>> > > The standard verification procedure is documented at
>> > >
>> > >
>> https://github.com/apache/arrow-datafusion/blob/master/dev/release/README.md#verifying-release-candidates
>> > > .
>> > >
>> > > [ ] +1 Release this as Apache Arrow DataFusion 10.0.0
>> > > [ ] +0
>> > > [ ] -1 Do not release this as Apache Arrow DataFusion 10.0.0
>> because...
>> > >
>> > > Here is my vote:
>> > >
>> > > +1
>> > >
>> > > [1]:
>> > >
>> > >
>> https://github.com/apache/arrow-datafusion/tree/d25e822c1ef85ee7c0297b4b38d05a51b0d2e46f
>> > > [2]:
>> > >
>> > >
>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-datafusion-10.0.0-rc1
>> > > [3]:
>> > >
>> > >
>> https://github.com/apache/arrow-datafusion/blob/d25e822c1ef85ee7c0297b4b38d05a51b0d2e46f/CHANGELOG.md
>> > >
>>
>