You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Andy Grove <ag...@apache.org> on 2021/04/10 13:48:20 UTC
[Rust] [Ballista] PR reviews / merges
Now that Ballista is merged into the Arrow repo, there is some follow-up
work around CI and updating documentation.
Given that Apache Arrow follows a Commit-then-review policy, I am planning
on merging some of these early trivial PRs (that do not involve code
changes) without requesting or waiting on reviews (but of course reviews
are welcome!) so that I can get the project back to a state where others
can start contributing.
Please let me know if there are any objections and I will be happy to
change the approach.
Re: [Rust] [Ballista] PR reviews / merges
Posted by Andy Grove <an...@gmail.com>.
Thanks, Andrew. I think I'm done now with the changes I needed to make to
docs and CI.
On Sun, Apr 11, 2021 at 4:13 AM Andrew Lamb <al...@influxdata.com> wrote:
> Sounds good --- just let us know if you need any help!
>
> Andrew
>
> On Sat, Apr 10, 2021 at 9:48 AM Andy Grove <ag...@apache.org> wrote:
>
> > Now that Ballista is merged into the Arrow repo, there is some follow-up
> > work around CI and updating documentation.
> >
> > Given that Apache Arrow follows a Commit-then-review policy, I am
> planning
> > on merging some of these early trivial PRs (that do not involve code
> > changes) without requesting or waiting on reviews (but of course reviews
> > are welcome!) so that I can get the project back to a state where others
> > can start contributing.
> >
> > Please let me know if there are any objections and I will be happy to
> > change the approach.
> >
>
Re: [Rust] [Ballista] PR reviews / merges
Posted by Andrew Lamb <al...@influxdata.com>.
Sounds good --- just let us know if you need any help!
Andrew
On Sat, Apr 10, 2021 at 9:48 AM Andy Grove <ag...@apache.org> wrote:
> Now that Ballista is merged into the Arrow repo, there is some follow-up
> work around CI and updating documentation.
>
> Given that Apache Arrow follows a Commit-then-review policy, I am planning
> on merging some of these early trivial PRs (that do not involve code
> changes) without requesting or waiting on reviews (but of course reviews
> are welcome!) so that I can get the project back to a state where others
> can start contributing.
>
> Please let me know if there are any objections and I will be happy to
> change the approach.
>