You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@datafusion.apache.org by gi...@apache.org on 2026/06/09 23:59:09 UTC
(datafusion) branch asf-site updated: Publish built docs triggered by bf71ea67734087408afc3a5a26df5547f53cf777
This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 63d7b59c6f Publish built docs triggered by bf71ea67734087408afc3a5a26df5547f53cf777
63d7b59c6f is described below
commit 63d7b59c6f231e944c618c72c0f5e8cc3bbab307
Author: github-actions[bot] <gi...@users.noreply.github.com>
AuthorDate: Tue Jun 9 23:59:05 2026 +0000
Publish built docs triggered by bf71ea67734087408afc3a5a26df5547f53cf777
---
_sources/contributor-guide/release_management.md.txt | 10 ++++++----
contributor-guide/release_management.html | 9 +++++----
searchindex.js | 2 +-
3 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/_sources/contributor-guide/release_management.md.txt b/_sources/contributor-guide/release_management.md.txt
index 0515204a5e..e01e58a369 100644
--- a/_sources/contributor-guide/release_management.md.txt
+++ b/_sources/contributor-guide/release_management.md.txt
@@ -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:
@@ -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
diff --git a/contributor-guide/release_management.html b/contributor-guide/release_management.html
index 2dbe6d48f0..7600db0039 100644
--- a/contributor-guide/release_management.html
+++ b/contributor-guide/release_management.html
@@ -465,10 +465,11 @@ series.</p>
<li><p>(Most common) Fix the issue on <code class="docutils literal notranslate"><span class="pre">main</span></code> and then backport the merged change to the release branch</p></li>
<li><p>Fix the issue on the release branch and then forward-port the change to <code class="docutils literal notranslate"><span class="pre">main</span></code></p></li>
</ul>
-<p>Releases are coordinated in a GitHub issue, such as the
-<a class="reference external" href="https://github.com/apache/datafusion/issues/18072">release issue for 50.3.0</a>. 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.</p>
+<p>Releases are coordinated using GitHub issues. Each planned release is listed in
+the <a class="reference external" href="https://github.com/apache/datafusion/issues/19783">DataFusion Releases tracking issue</a>, and each release is coordinated in a
+dedicated issue, such as the <a class="reference external" href="https://github.com/apache/datafusion/issues/18072">release issue for 50.3.0</a>. 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.</p>
<p>To prepare for a new release series, maintainers:</p>
<ul class="simple">
<li><p>Create a new branch from <code class="docutils literal notranslate"><span class="pre">main</span></code>, such as <code class="docutils literal notranslate"><span class="pre">branch-50</span></code>, in the Apache repository</p></li>
diff --git a/searchindex.js b/searchindex.js
index e2d37722ec..8caad4d1a2 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles":{"!=":[[74,"op-neq"]],"!~":[[74,"op-re-not-match"]],"!~*":[[74,"op-re-not-match-i"]],"!~~":[[74,"id19"]],"!~~*":[[74,"id20"]],"#":[[74,"op-bit-xor"]],"%":[[74,"op-modulo"]],"&":[[74,"op-bit-and"]],"(relation, name) tuples in logical fields and logical columns are unique":[[15,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[74,"op-multiply"]],"+":[[74,"op-plus"]],"-":[[74,"op-minus"]],"/":[[74,"op-divide"]],"1. Array Literal Con [...]
\ No newline at end of file
+Search.setIndex({"alltitles":{"!=":[[74,"op-neq"]],"!~":[[74,"op-re-not-match"]],"!~*":[[74,"op-re-not-match-i"]],"!~~":[[74,"id19"]],"!~~*":[[74,"id20"]],"#":[[74,"op-bit-xor"]],"%":[[74,"op-modulo"]],"&":[[74,"op-bit-and"]],"(relation, name) tuples in logical fields and logical columns are unique":[[15,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[74,"op-multiply"]],"+":[[74,"op-plus"]],"-":[[74,"op-minus"]],"/":[[74,"op-divide"]],"1. Array Literal Con [...]
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datafusion.apache.org
For additional commands, e-mail: commits-help@datafusion.apache.org