Re: [ANNOUNCE] Copying Rust components to new repositories

The new repositories are now ready to start accepting PRs and we will start merging new code shortly. Over the next few days, we plan to send out additional information to this mailing list on the use of Github issues instead of JIRA as well as porting over existing Rust/DataFusion content from JI

Re: [ANNOUNCE] Copying Rust components to new repositories

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.c

Re: [ANNOUNCE] Copying Rust components to new repositories

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

Re: [ANNOUNCE] Copying Rust components to new repositories

On Mon, Apr 19, 2021 at 7:32 AM Jorge Cardoso Leitão wrote: > > Hi, > > I created 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/ > * upd

Re: [ANNOUNCE] Copying Rust components to new repositories

Hi, I created 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 li

Re: [ANNOUNCE] Copying Rust components to new repositories

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.

Re: [ANNOUNCE] Copying Rust components to new repositories

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 wrote:

Re: [ANNOUNCE] Copying Rust components to new repositories

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 wrote: > On Sun, Apr 18, 2021 at 7:03 PM Antoine Pitr

Re: [ANNOUNCE] Copying Rust components to new repositories

On Sun, Apr 18, 2021 at 7:03 PM Antoine Pitrou wrote: > > On Sun, 18 Apr 2021 18:27:27 +0200 > Jorge Cardoso Leitão 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)

Re: [ANNOUNCE] Copying Rust components to new repositories

We aren’t allowed to access the Settings tab on the repos, if you need to configure anything, file an Infrastructure Jira and they’ll take care of it for you. On Sun, Apr 18, 2021 at 11:27 AM Jorge Cardoso Leitão < jorgecarlei...@gmail.com> wrote: > Yes, we are not touching apache/arrow. > > Does

Re: [ANNOUNCE] Copying Rust components to new repositories

On Sun, 18 Apr 2021 18:27:27 +0200 Jorge Cardoso Leitão 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 :-(

Re: [ANNOUNCE] Copying Rust components to new repositories

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? Thanks, Jorge On Sun, Apr 18, 2021 at 5:54 PM Krisztián Szűcs wrote: > On Sun, Apr 18, 2021 at 5:47 PM Antoine Pitro

Re: [ANNOUNCE] Copying Rust components to new repositories

On Sun, Apr 18, 2021 at 5:47 PM Antoine Pitrou wrote: > > > Le 18/04/2021 à 17:43, Krisztián Szűcs a écrit : > > I wouldn't overwrite the git history since there can be explicit > > commit references in other projects. > > > > Either way, please don't overwrite any of the branches until I'm > > wo

Re: [ANNOUNCE] Copying Rust components to new repositories

Le 18/04/2021 à 17:43, Krisztián Szűcs a écrit : I wouldn't overwrite the git history since there can be explicit commit references in other projects. Either way, please don't overwrite any of the branches until I'm working on the release. Ah, I think we're only talking about the arrow-rs re

Re: [ANNOUNCE] Copying Rust components to new repositories

I wouldn't overwrite the git history since there can be explicit commit references in other projects. Either way, please don't overwrite any of the branches until I'm working on the release. On Sun, Apr 18, 2021 at 5:09 PM Antoine Pitrou wrote: > > > Le 18/04/2021 à 16:36, Andy Grove a écrit : >

Re: [ANNOUNCE] Copying Rust components to new repositories

Thanks all for the info, we are going to run git filter branch next. On Sun, Apr 18, 2021 at 9:28 AM Jed Brown wrote: > Andy Grove writes: > > > We started looking at the documentation for git filter-branch and it > > recommends not to use it. It states that "git-filter-branch is riddled > with

Re: [ANNOUNCE] Copying Rust components to new repositories

Andy Grove writes: > We started looking at the documentation for git filter-branch and it > recommends not to use it. It states that "git-filter-branch is riddled with > gotchas resulting in various ways to easily corrupt repos or end up with a > mess worse than what you started with:". I've use

Re: [ANNOUNCE] Copying Rust components to new repositories

Le 18/04/2021 à 16:36, Andy Grove a écrit : Hi Wes, We started looking at the documentation for git filter-branch and it recommends not to use it. It states that "git-filter-branch is riddled with gotchas resulting in various ways to easily corrupt repos or end up with a mess worse than what y

Re: [ANNOUNCE] Copying Rust components to new repositories

Hi Wes, We started looking at the documentation for git filter-branch and it recommends not to use it. It states that "git-filter-branch is riddled with gotchas resulting in various ways to easily corrupt repos or end up with a mess worse than what you started with:". I guess we can decide to run

Re: [ANNOUNCE] Copying Rust components to new repositories

Hi Andy — are you planning to use git filter-branch to remove non-Rust-related commits from the git history? This would seem helpful to trim the repository sizes. It changes commit hashes but I suppose this is a fair trade off. On Sun, Apr 18, 2021 at 9:11 AM Andy Grove wrote: > We are now start

[ANNOUNCE] Copying Rust components to new repositories

We are now starting the process of copying the Rust components to the new repositories. There is a tracking document that we are working from [1]. We will send an update once the code is in the new repositories. We do not plan on removing code from the monorepo until after the 4.0.0 release. [1]