Skip to content

arrow 13.0.0#1124

Merged
h-vetinari merged 6 commits intoconda-forge:mainfrom
h-vetinari:13
Aug 24, 2023
Merged

arrow 13.0.0#1124
h-vetinari merged 6 commits intoconda-forge:mainfrom
h-vetinari:13

Conversation

@h-vetinari
Copy link
Copy Markdown
Member

@h-vetinari h-vetinari commented Jul 24, 2023

Let's see what building off of the latest tag brings. This helps prepare for when the bot comes around, but also to button up apache/arrow#35637

For arrow 13 I'm also planning to remove the old naming of the outputs arrow-cpp & arrow-cpp-proc.

Closes #1139

@conda-forge-webservices
Copy link
Copy Markdown

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@h-vetinari
Copy link
Copy Markdown
Member Author

@conda-forge/arrow-cpp, are people OK with dropping the old arrow-cpp compatibility outputs?

We've now reached the point where the last 4 releases (10-13) all have libarrow, so I think we could/should drop it. I can add a rule to the linter to warn any remaining users of arrow-cpp to move to `libarrow.

@xhochy
Copy link
Copy Markdown
Member

xhochy commented Aug 24, 2023

Result of an offline discussion on arrow-cpp between @h-vetinari is that we will keep the output for version 13 and will drop them with 14. Currently, a package that builds against Arrow C++ must use arrow-cpp as we don't have the output yet for version 9.

I had considered switching patterns for 10.x and 11.x already;
it was a mistake not to do it, so do it now. Better do the right
thing long-term; it'll only take a little while until the old
pattern falls off the radar.
@h-vetinari
Copy link
Copy Markdown
Member Author

Currently, a package that builds against Arrow C++ [for all currently supported versions] must use arrow-cpp as we don't have the output yet for version 9.

... which is solved once we drop off arrow v9 after the v13 migration. 🙃

@h-vetinari h-vetinari added the automerge Merge the PR when CI passes label Aug 24, 2023
@h-vetinari
Copy link
Copy Markdown
Member Author

Actually, since this passed already before, in it goes... :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Merge the PR when CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants