docs: link to 2026 Q3-Q4 roadmap discussion#22884
Merged
Merged
Conversation
Add a link to the current roadmap discussion (apache#22882) in the README and the contributor-guide roadmap page, and list it at the top of the quarterly roadmap discussions. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
the
documentation
2010YOUY01
approved these changes
Jun 11, 2026
Contributor
Author
|
Thanks @2010YOUY01 -- I'll merge this one in and we can make any changes that others would suggest as follow on PRs |
AdamGS
pushed a commit
to AdamGS/arrow-datafusion
that referenced
this pull request
Jun 11, 2026
## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes apache#123` indicates that this PR will close issue apache#123. --> - Related to apache#22882. ## Rationale for this change I opened a new roadmap discussion, [DataFusion 2026 Q3-Q4 Roadmap Discussion](apache#22882), and it would be nice if public-facing docs pointed readers at it so the community can find and join the current discussion. ## What changes are included in this PR? - Add a roadmap pointer to the `README.md` "Contributing to DataFusion" section linking to the roadmap docs and the current discussion (apache#22882). - Update the contributor-guide roadmap page (`docs/source/contributor-guide/roadmap.md`) to call out apache#22882 as the current discussion and list it at the top of the quarterly roadmap discussions. ## Are these changes tested? No tests; documentation-only change. ## Are there any user-facing changes? Documentation only — adds links to the current roadmap discussion. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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 opened a new roadmap discussion, DataFusion 2026 Q3-Q4 Roadmap Discussion, and it would be nice if public-facing docs pointed readers at it so the community can find and join the current discussion.
What changes are included in this PR?
README.md"Contributing to DataFusion" section linking to the roadmap docs and the current discussion ([DISCUSSION] 2026 Q3-Q4 Roadmap Discussion #22882).docs/source/contributor-guide/roadmap.md) to call out [DISCUSSION] 2026 Q3-Q4 Roadmap Discussion #22882 as the current discussion and list it at the top of the quarterly roadmap discussions.Are these changes tested?
No tests; documentation-only change.
Are there any user-facing changes?
Documentation only — adds links to the current roadmap discussion.