An update: we have had success filtering out git history (using
git-filter-repo) in the arrow-rs and arrow-datafusion repos, and have made
most of the required changes to start accepting PRs in the new repo.

Stay tuned.

On Tue, Apr 20, 2021 at 2:30 AM Jorge Cardoso Leitão <
jorgecarlei...@gmail.com> wrote:

> Perfect, thanks Krisztian.
>
> There is no hurry in any of this; I am just covering high risk tasks to
> evaluate and mitigate these risks ahead of time.
>
> There is now a PR that adds integration tests on the rust side:
> https://github.com/apache/arrow-rs/pull/10 . All green.
>
> Best,
> Jorge
>
>
>
>
> On Mon, Apr 19, 2021 at 6:49 PM Krisztián Szűcs <szucs.kriszt...@gmail.com
> >
> wrote:
>
> > On Mon, Apr 19, 2021 at 7:32 AM Jorge Cardoso Leitão
> > <jorgecarlei...@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > I created ARROW-12444 <
> https://issues.apache.org/jira/browse/ARROW-12444
> > >
> > > to handle the changes on the apache/arrow side and fielded
> > > https://github.com/apache/arrow/pull/10096 to address it. It:
> > >
> > > * removes rust/
> > > * updates CI
> > > * runs integration tests via git clone
> > > * removes rust from archery lint, RAT, etc.
> > >
> > > It passes =D
> > >
> > > Please do not merge until the release and post-release tasks are
> > completed
> > > (i.e. Krisztián gives a green light), as that has priority and imo
> > > conflicts should be handled on this PR.
> > If everything goes well the VOTE shouldn't take more than 3 days and
> > the post-release tasks should take at most a single day.
> >
> > Thanks, Krisztian
> > >
> > > It does not handle the release process and tooling. We have until the
> > next
> > > release to solve that. I created ARROW-12445
> > > <https://issues.apache.org/jira/browse/ARROW-12445> to track that.
> > >
> > > Best,
> > > Jorge
> > >
> > >
> > > On Mon, Apr 19, 2021 at 4:10 AM Andy Grove <andygrov...@gmail.com>
> > wrote:
> > >
> > > > CI is now working for arrow-datafusion so we are at a state where
> > people
> > > > can fork and open PRs.
> > > >
> > > > There is plenty of follow-up work to do (tracked in the google doc
> > shared
> > > > earlier) and this work will continue over the next few days.
> > > >
> > > > Thanks to everyone who has been involved in making this happen.
> > > >
> > > >
> > > >
> > > >
> > > > On Sun, Apr 18, 2021 at 2:01 PM Andy Grove <andygrov...@gmail.com>
> > wrote:
> > > >
> > > > > We were making good progress, and working through getting CI
> working
> > for
> > > > > arrow-datafusion, but now crates.io seems to be having an outage
> so
> > I am
> > > > > blocked now. I will be out for a few hours but will see if I can
> get
> > this
> > > > > resolved when I am back.
> > > > >
> > > > > On Sun, Apr 18, 2021 at 12:10 PM Andy Grove <andygrov...@gmail.com
> >
> > > > wrote:
> > > > >
> > > > >> I found out how to enable GitHub issues and control other GitHub
> > > > features
> > > > >> by editing .asf.yaml
> > > > >>
> > > > >> Pretty cool actually.
> > > > >>
> > > > >>
> > > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
> > > > >>
> > > > >> On Sun, Apr 18, 2021 at 11:52 AM Krisztián Szűcs <
> > > > >> szucs.kriszt...@gmail.com> wrote:
> > > > >>
> > > > >>> On Sun, Apr 18, 2021 at 7:03 PM Antoine Pitrou <
> anto...@python.org
> > >
> > > > >>> wrote:
> > > > >>> >
> > > > >>> > On Sun, 18 Apr 2021 18:27:27 +0200
> > > > >>> > Jorge Cardoso Leitão <jorgecarlei...@gmail.com> wrote:
> > > > >>> >
> > > > >>> > > Yes, we are not touching apache/arrow.
> > > > >>> > >
> > > > >>> > > Does anyone know how to request permissions on github repos?
> We
> > > > >>> can't even
> > > > >>> > > see "Settings" atm (we can push to master). A JIRA on INFRA?
> > > > >>> >
> > > > >>> > "Settings" are only available by INFRA AFAIU :-(
> > > > >>> > You'll have to make JIRA tickets everytime you want to
> customize
> > a
> > > > repo
> > > > >>> > setting, I'm afraid.
> > > > >>> Yes, sadly this is the case.
> > > > >>> >
> > > > >>> > Regards
> > > > >>> >
> > > > >>> > Antoine.
> > > > >>> >
> > > > >>> >
> > > > >>>
> > > > >>
> > > >
> >
>

Reply via email to