From 40ea3b6b8682eb143c635e7d03e36b9bef69318f Mon Sep 17 00:00:00 2001 From: Andrew Lamb Date: Mon, 8 Jun 2026 06:47:32 -0400 Subject: [PATCH 1/2] Link to Release tracking issue to docs --- docs/source/contributor-guide/release_management.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/source/contributor-guide/release_management.md b/docs/source/contributor-guide/release_management.md index 0515204a5ecbc..31a5d3bd43e96 100644 --- a/docs/source/contributor-guide/release_management.md +++ b/docs/source/contributor-guide/release_management.md @@ -44,10 +44,12 @@ 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 the coordination for each specific +release is done on a dedicated issues (for example, the [release issue for +50.3.0]). If you think a fix should be included in a patch release, please +discuss it on the relevant tracking issue, optionally opening a backport PR as +well. To prepare for a new release series, maintainers: @@ -117,6 +119,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 From 00e898b83550c5097d2ce0972a22d563dbe4202a Mon Sep 17 00:00:00 2001 From: Andrew Lamb Date: Mon, 8 Jun 2026 06:49:18 -0400 Subject: [PATCH 2/2] docs: tighten release tracking wording --- docs/source/contributor-guide/release_management.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/source/contributor-guide/release_management.md b/docs/source/contributor-guide/release_management.md index 31a5d3bd43e96..e01e58a3695b1 100644 --- a/docs/source/contributor-guide/release_management.md +++ b/docs/source/contributor-guide/release_management.md @@ -45,11 +45,10 @@ Changes reach a release branch in one of two ways: - Fix the issue on the release branch and then forward-port the change to `main` Releases are coordinated using GitHub issues. Each planned release is listed in -the [DataFusion Releases tracking issue], and the coordination for each specific -release is done on a dedicated issues (for example, the [release issue for -50.3.0]). If you think a fix should be included in a patch release, please -discuss it on the relevant tracking issue, optionally opening a backport PR as -well. +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: