+1 (I'm assuming, as Neal described, I can just reassign the issue to
myself and it won't confuse the assignment bot)
On Fri, Jul 8, 2022 at 8:29 AM Jacob Wujciak wrote:
>
> I support this idea and a 90 days threshold seems good to me!
>
> On Fri, Jul 8, 2022 at 8:02 PM Neal Richardson
> wrote:
+ 1 (non-binding)
Verified on Mac M1.
Thanks, Andrew!
On Sat, 9 Jul 2022 at 02:55, Andrew Lamb wrote:
> Hi,
>
> I would like to propose a release of Apache Arrow Rust Implementation,
> version 18.0.0.
>
> This release candidate is based on commit:
> 330505c98c9db4d103b4965e8bd55065961dada7 [1]
Hi,
I would like to propose a release of Apache Arrow Rust Implementation,
version 18.0.0.
This release candidate is based on commit:
330505c98c9db4d103b4965e8bd55065961dada7 [1]
The proposed release tarball and signatures are hosted at [2].
The changelog is located at [3].
Please download, ve
I support this idea and a 90 days threshold seems good to me!
On Fri, Jul 8, 2022 at 8:02 PM Neal Richardson
wrote:
> Sounds like a good idea to me, thanks for taking the initiative on this.
>
> To Benson's idea about varying the timeout based on priority, IMO we could
> just start with the simp
Sounds like a good idea to me, thanks for taking the initiative on this.
To Benson's idea about varying the timeout based on priority, IMO we could
just start with the simple approach and see how that goes. Maybe that would
be helpful but maybe it's not necessary. If you're truly watching an issue
Thank you all for the comments and discussion; Given there appears to be
consensus from the community to accept this donation, I have written up a
plan [1] and will begin to execute it over the coming weeks.
Any and all feedback is more than welcome.
Thanks again
Andrew
[1] https://github.com/ap
On 7/8/22 18:49, Todd Farmer wrote:
Hello,
The backlog of ARROW issues currently stands at 2585 open issues [1]. The
size of the backlog presents challenges to users and developers alike, and
I believe the project would benefit from establishing guidance around issue
handling. I'll be submitting
Hello,
The backlog of ARROW issues currently stands at 2585 open issues [1]. The
size of the backlog presents challenges to users and developers alike, and
I believe the project would benefit from establishing guidance around issue
handling. I'll be submitting a series of proposals for discussion,
hi all,
Just catching up on this e-mail thread from last month. Since I've
been neck deep refactoring the kernels code the last few weeks I have
a few thoughts about this:
* How we implement and use RLE in the C++ library and Acero is
separate from how RLE will be represented in the Arrow IPC for
