Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should we document at what rate deprecated APIs are removed? #6851

Closed
alamb opened this issue Dec 6, 2024 · 2 comments · Fixed by #6852
Closed

Should we document at what rate deprecated APIs are removed? #6851

alamb opened this issue Dec 6, 2024 · 2 comments · Fixed by #6852
Assignees
@alamb
Labels
arrow Changes to the arrow crate documentation Improvements or additions to documentation parquet Changes to the parquet crate

Comments

@alamb
Copy link
Contributor

alamb commented Dec 6, 2024 

          Should we document at what rate deprecated APIs will be removed? 4 major releases does seem sufficient to me, but perhaps others downstream have a different view. 🤷

Originally posted by @etseidl in #6838 (comment)
@alamb alamb mentioned this issue Dec 6, 2024
Merged
@alamb
Copy link
Contributor Author

alamb commented Dec 6, 2024

Proposal here: #6852

@alamb alamb added documentation Improvements or additions to documentation parquet Changes to the parquet crate arrow Changes to the arrow crate labels Dec 6, 2024
@alamb
Copy link
Contributor Author

alamb commented Dec 6, 2024

I think we should!

@alamb alamb self-assigned this Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alamb alamb

Labels
arrow Changes to the arrow crate documentation Improvements or additions to documentation parquet Changes to the parquet crate
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add deprecation / API removal policy alamb/arrow-rs
1 participant
@alamb