Update release schedule on README#9881
Merged
Merged
Conversation
alamb
commented
May 2, 2026
| | May 2026 | [`59.0.0`] | Major, potentially breaking API changes | | ||
| | Approximate Date | Version | Notes | | ||
| | ---------------- |-------------|-----------------------------------------| | ||
| | May 2026 | [`58.3.0`] | Minor, NO breaking API changes | |
Contributor
Author
There was a problem hiding this comment.
BTW @etseidl there are a few items I would like to get released soon (like make a release next week). If we can avoid making any breaking changes on main until then I will just make the PR off main.
etseidl
approved these changes
May 2, 2026
Contributor
Author
|
THanks @etseidl |
Rich-T-kid
pushed a commit
to Rich-T-kid/arrow-rs
that referenced
this pull request
Jun 2, 2026
# Which issue does this PR close? - relate to apache#7392 # Rationale for this change I need to keep this stuff written down somewhere otherwise I lose track of it # What changes are included in this PR? Update the release schedule of the README to reflect - apache#7392 # Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? If this PR claims a performance improvement, please include evidence such as benchmark results. --> # Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. If there are any breaking changes to public APIs, please call them out. -->
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
I need to keep this stuff written down somewhere otherwise I lose track of it
What changes are included in this PR?
Update the release schedule of the README to reflect
Are these changes tested?
Are there any user-facing changes?