Skip to content

docs: link release tracking issue to release management page #22822

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

Open
alamb wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −4
Open

docs: link release tracking issue to release management page #22822

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
40ea3b6
Link to Release tracking issue to docs
alamb Jun 8, 2026
00e898b
docs: tighten release tracking wording
alamb Jun 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions docs/source/contributor-guide/release_management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,11 @@ Changes reach a release branch in one of two ways:
- (Most common) Fix the issue on `main` and then backport the merged change to the release branch
- Fix the issue on the release branch and then forward-port the change to `main`

Releases are coordinated in a GitHub issue, such as the
[release issue for 50.3.0]. If you think a fix should be included in a patch
release, discuss it on the relevant tracking issue first. You can also open the
backport PR first and then link it from the tracking issue.
Releases are coordinated using GitHub issues. Each planned release is listed in
the [DataFusion Releases tracking issue], and each release is coordinated in a
dedicated issue, such as the [release issue for 50.3.0]. If you think a fix
should be included in a patch release, discuss it on the relevant tracking issue
or open a backport PR and link it there.

To prepare for a new release series, maintainers:

Expand Down Expand Up @@ -117,6 +118,7 @@ This PR:
[`main` branch]: https://github.com/apache/datafusion/tree/main
[`branch-50`]: https://github.com/apache/datafusion/tree/branch-50
[the release process readme in `dev/release`]: https://github.com/apache/datafusion/blob/main/dev/release/README.md
[datafusion releases tracking issue]: https://github.com/apache/datafusion/issues/19783
[release issue for 50.3.0]: https://github.com/apache/datafusion/issues/18072
[example backport pr]: https://github.com/apache/datafusion/pull/18131
[additional backport pr example]: https://github.com/apache/datafusion/pull/20792
Expand Down
Loading