Yes, that is correct. We don't want to create confusion between releases
made by the Apache project and unofficial development releases
On Wed, Apr 4, 2018, 10:17 PM Andy Grove wrote:
> Wes,
>
> We talked about nightlies and downstream dependencies and I just want to be
>
Wes,
We talked about nightlies and downstream dependencies and I just want to be
clear I'm understanding what you are suggesting. Apologies if I'm being a
bit slow.
I think we are in agreement that nightlies make sense for now because
things are moving fast and this Rust library is very new.
I
Wes,
Thanks for the feedback.
A nightly release sounds appealing in these early days. Technically, I
assume this is just a case of configuring travis to update the minor
version number and run a "cargo publish" on master once per day (if there
are changes)?
>From a process point of view, what
hi Andy,
> My argument for doing this is that although other Rust developers can set up
> a github dependency in their Cargo,toml, this just isn't a natural way to
> work in Rust so we are making it hard for people to experiment with Arrow.
Being penalized by the language for not using a
Hi,
I've been creating some frustrations for myself this week because I'm not
sure how to work efficiently now that the Rust version of Apache Arrow is
in the official Apache repo.
It seems I have two conflicting requirements:
1. I want Apache Arrow [Rust] to be a community-driven high quality