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/07/28 23:46:02 UTC
(datafusion-comet) branch asf-site updated: Publish built docs triggered by 1db954d08580c725c7e3b2906a0ae1c887f52f9a
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-comet.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 35b6d4797b Publish built docs triggered by 1db954d08580c725c7e3b2906a0ae1c887f52f9a
35b6d4797b is described below
commit 35b6d4797b96d9d4dd9c95806bc6adb838a55ccc
Author: github-actions[bot] <gi...@users.noreply.github.com>
AuthorDate: Tue Jul 28 23:45:58 2026 +0000
Publish built docs triggered by 1db954d08580c725c7e3b2906a0ae1c887f52f9a
---
_sources/contributor-guide/release_process.md.txt | 25 +++++++++++++++++++----
contributor-guide/release_process.html | 23 +++++++++++++++++----
searchindex.js | 2 +-
3 files changed, 41 insertions(+), 9 deletions(-)
diff --git a/_sources/contributor-guide/release_process.md.txt b/_sources/contributor-guide/release_process.md.txt
index 8de85a6b63..58738be086 100644
--- a/_sources/contributor-guide/release_process.md.txt
+++ b/_sources/contributor-guide/release_process.md.txt
@@ -142,18 +142,35 @@ targeting the release branch.
### Update Maven Version
-Open a PR targeting the release branch that changes the Maven version from `0.13.0-SNAPSHOT` to `0.13.0` in
-the `pom.xml` files and in the diff files under `dev/diffs`.
+Open a PR targeting the release branch that changes the Maven version from `0.13.0-SNAPSHOT` to `0.13.0` in:
+
+- the `pom.xml` files: `pom.xml`, `common/pom.xml`, `spark/pom.xml`, and `spark-integration/pom.xml`
+- the `<comet.version>` property in the Spark test diffs under `dev/diffs`
+- the `comet` version in the Iceberg test diffs under `dev/diffs/iceberg`, which use a Gradle version
+ catalog entry (`comet = "0.13.0"`) rather than a Maven property
There is no need to update the Rust crate versions because they will already be `0.13.0`.
+Once the version is bumped, verify that no references to the old version remain:
+
+```shell
+git grep -n '0.13.0-SNAPSHOT' -- . ':!docs/source/changelog'
+```
+
+Any hit outside the change log is a place that will break on the release branch. Note that dropping the
+`-SNAPSHOT` qualifier changes the built artifact file names, so anything that locates the jar by glob must
+match a bare version too. Prefer patterns such as `comet-spark-spark3.5_2.12-*.jar` over
+`comet-spark-spark3.5_2.12-*-SNAPSHOT.jar`, and prefer resolving the jar by glob over hardcoding a version.
+The release branch runs the same CI workflows as `main`, including the PyArrow UDF tests, so a
+`-SNAPSHOT`-only glob in a test harness or script fails only after the release branch is cut.
+
### Update Version in main
Create a PR against the main branch to prepare for developing the next release:
- Update the Rust crate version to `0.14.0`.
-- Update the Maven version to `0.14.0-SNAPSHOT` (both in the `pom.xml` files and also in the diff files
- under `dev/diffs`).
+- Update the Maven version to `0.14.0-SNAPSHOT` in the same set of files listed above (the `pom.xml` files,
+ the Spark test diffs under `dev/diffs`, and the Iceberg test diffs under `dev/diffs/iceberg`).
### Generate the Change Log
diff --git a/contributor-guide/release_process.html b/contributor-guide/release_process.html
index f995454ab1..8e344d64f4 100644
--- a/contributor-guide/release_process.html
+++ b/contributor-guide/release_process.html
@@ -663,17 +663,32 @@ targeting the release branch.</p>
</section>
<section id="update-maven-version">
<h3>Update Maven Version<a class="headerlink" href="#update-maven-version" title="Link to this heading">#</a></h3>
-<p>Open a PR targeting the release branch that changes the Maven version from <code class="docutils literal notranslate"><span class="pre">0.13.0-SNAPSHOT</span></code> to <code class="docutils literal notranslate"><span class="pre">0.13.0</span></code> in
-the <code class="docutils literal notranslate"><span class="pre">pom.xml</span></code> files and in the diff files under <code class="docutils literal notranslate"><span class="pre">dev/diffs</span></code>.</p>
+<p>Open a PR targeting the release branch that changes the Maven version from <code class="docutils literal notranslate"><span class="pre">0.13.0-SNAPSHOT</span></code> to <code class="docutils literal notranslate"><span class="pre">0.13.0</span></code> in:</p>
+<ul class="simple">
+<li><p>the <code class="docutils literal notranslate"><span class="pre">pom.xml</span></code> files: <code class="docutils literal notranslate"><span class="pre">pom.xml</span></code>, <code class="docutils literal notranslate"><span class="pre">common/pom.xml</span></code>, <code class="docutils literal notranslate"><span class="pre">spark/pom.xml</span></code>, and <code class="docutils literal notranslate"><span class="pre">spark-integration/pom.xml</span></code></p></li>
+<li><p>the <code class="docutils literal notranslate"><span class="pre"><comet.version></span></code> property in the Spark test diffs under <code class="docutils literal notranslate"><span class="pre">dev/diffs</span></code></p></li>
+<li><p>the <code class="docutils literal notranslate"><span class="pre">comet</span></code> version in the Iceberg test diffs under <code class="docutils literal notranslate"><span class="pre">dev/diffs/iceberg</span></code>, which use a Gradle version
+catalog entry (<code class="docutils literal notranslate"><span class="pre">comet</span> <span class="pre">=</span> <span class="pre">"0.13.0"</span></code>) rather than a Maven property</p></li>
+</ul>
<p>There is no need to update the Rust crate versions because they will already be <code class="docutils literal notranslate"><span class="pre">0.13.0</span></code>.</p>
+<p>Once the version is bumped, verify that no references to the old version remain:</p>
+<div class="highlight-shell notranslate"><div class="highlight"><pre><span></span>git<span class="w"> </span>grep<span class="w"> </span>-n<span class="w"> </span><span class="s1">'0.13.0-SNAPSHOT'</span><span class="w"> </span>--<span class="w"> </span>.<span class="w"> </span><span class="s1">':!docs/source/changelog'</span>
+</pre></div>
+</div>
+<p>Any hit outside the change log is a place that will break on the release branch. Note that dropping the
+<code class="docutils literal notranslate"><span class="pre">-SNAPSHOT</span></code> qualifier changes the built artifact file names, so anything that locates the jar by glob must
+match a bare version too. Prefer patterns such as <code class="docutils literal notranslate"><span class="pre">comet-spark-spark3.5_2.12-*.jar</span></code> over
+<code class="docutils literal notranslate"><span class="pre">comet-spark-spark3.5_2.12-*-SNAPSHOT.jar</span></code>, and prefer resolving the jar by glob over hardcoding a version.
+The release branch runs the same CI workflows as <code class="docutils literal notranslate"><span class="pre">main</span></code>, including the PyArrow UDF tests, so a
+<code class="docutils literal notranslate"><span class="pre">-SNAPSHOT</span></code>-only glob in a test harness or script fails only after the release branch is cut.</p>
</section>
<section id="update-version-in-main">
<h3>Update Version in main<a class="headerlink" href="#update-version-in-main" title="Link to this heading">#</a></h3>
<p>Create a PR against the main branch to prepare for developing the next release:</p>
<ul class="simple">
<li><p>Update the Rust crate version to <code class="docutils literal notranslate"><span class="pre">0.14.0</span></code>.</p></li>
-<li><p>Update the Maven version to <code class="docutils literal notranslate"><span class="pre">0.14.0-SNAPSHOT</span></code> (both in the <code class="docutils literal notranslate"><span class="pre">pom.xml</span></code> files and also in the diff files
-under <code class="docutils literal notranslate"><span class="pre">dev/diffs</span></code>).</p></li>
+<li><p>Update the Maven version to <code class="docutils literal notranslate"><span class="pre">0.14.0-SNAPSHOT</span></code> in the same set of files listed above (the <code class="docutils literal notranslate"><span class="pre">pom.xml</span></code> files,
+the Spark test diffs under <code class="docutils literal notranslate"><span class="pre">dev/diffs</span></code>, and the Iceberg test diffs under <code class="docutils literal notranslate"><span class="pre">dev/diffs/iceberg</span></code>).</p></li>
</ul>
</section>
<section id="generate-the-change-log">
diff --git a/searchindex.js b/searchindex.js
index 1349b37c3c..0f761297c0 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles": {"!": [[54, "id1"]], "%": [[52, "id1"]], "&": [[42, "id1"]], "*": [[52, "id2"]], "+": [[52, "id3"]], "-": [[52, "id4"]], "/": [[52, "id5"]], "1. Format Your Code": [[39, "format-your-code"]], "1. Install Comet": [[60, "install-comet"], [70, "install-comet"]], "1. Native Operators (nativeExecs map)": [[27, "native-operators-nativeexecs-map"]], "2. Build and Verify": [[39, "build-and-verify"]], "2. Clone Iceberg and Apply Diff": [[60, "clone-iceberg-and-apply- [...]
\ No newline at end of file
+Search.setIndex({"alltitles": {"!": [[54, "id1"]], "%": [[52, "id1"]], "&": [[42, "id1"]], "*": [[52, "id2"]], "+": [[52, "id3"]], "-": [[52, "id4"]], "/": [[52, "id5"]], "1. Format Your Code": [[39, "format-your-code"]], "1. Install Comet": [[60, "install-comet"], [70, "install-comet"]], "1. Native Operators (nativeExecs map)": [[27, "native-operators-nativeexecs-map"]], "2. Build and Verify": [[39, "build-and-verify"]], "2. Clone Iceberg and Apply Diff": [[60, "clone-iceberg-and-apply- [...]
\ 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