(datafusion-comet) branch branch-0.17 updated: chore: [branch-0.17] update release_process.md

[mb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mbutrovich pushed a commit to branch branch-0.17
in repository https://gitbox.apache.org/repos/asf/datafusion-comet.git


The following commit(s) were added to refs/heads/branch-0.17 by this push:
     new 45f55a867a chore: [branch-0.17] update release_process.md
45f55a867a is described below

commit 45f55a867a52b91c8caf9e44f5ed99c94f5b9990
Author: Matt Butrovich <mb...@users.noreply.github.com>
AuthorDate: Tue Jun 16 10:29:54 2026 -0400

    chore: [branch-0.17] update release_process.md
---
 docs/source/contributor-guide/release_process.md | 33 ++++++++++++++++++++----
 1 file changed, 28 insertions(+), 5 deletions(-)

diff --git a/docs/source/contributor-guide/release_process.md b/docs/source/contributor-guide/release_process.md
index 0daf4416b6..210dd33c1c 100644
--- a/docs/source/contributor-guide/release_process.md
+++ b/docs/source/contributor-guide/release_process.md
@@ -30,6 +30,7 @@ instructions on each step.
 
 - [ ] Release preparation: review expression support status and user guide
 - [ ] Create release branch
+- [ ] Protect the release branch in `.asf.yaml`
 - [ ] Generate release documentation
 - [ ] Update Maven version in release branch
 - [ ] Update version in main for next development cycle
@@ -103,23 +104,45 @@ git checkout -b branch-0.13
 git push apache branch-0.13
 ```
 
+Creating the branch is the only direct push to it. After protecting the branch (next step), all later changes
+to the release branch (documentation, version bump, changelog) go through pull requests targeting it.
+
+### Protect the Release Branch
+
+Add the new branch to `protected_branches` in `.asf.yaml` so it requires a pull request and review, the same as
+`main`. ASF applies `.asf.yaml` from the default branch, so this is a PR against `main`:
+
+```yaml
+protected_branches:
+  main:
+    required_pull_request_reviews:
+      required_approving_review_count: 1
+  branch-0.13:
+    required_pull_request_reviews:
+      required_approving_review_count: 1
+```
+
+All release branches stay protected, including older ones, so released code cannot be pushed to directly.
+
 ### Generate Release Documentation
 
-Generate the documentation content for this release. The docs on `main` contain only template markers,
-so we need to generate the actual content (config tables, compatibility matrices) for the release branch:
+The docs on `main` contain only template markers; CI fills them at publish time. A release branch instead
+commits the generated content so the archived docs for the release render real tables. Run the script to
+generate the config reference and the per-Spark-version compatibility pages and freeze them onto the branch:
 
 ```shell
 ./dev/generate-release-docs.sh
 git add docs/source/user-guide/latest/
 git commit -m "Generate docs for 0.13.0 release"
-git push apache branch-0.13
 ```
 
-This freezes the documentation to reflect the configs and expressions available in this release.
+The script runs one Maven build per supported Spark version, so it takes a while. Open a PR with this commit
+targeting the release branch.
 
 ### Update Maven Version
 
-Update the `pom.xml` files in the release branch to update the Maven version from `0.13.0-SNAPSHOT` to `0.13.0`.
+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`.
 
 There is no need to update the Rust crate versions because they will already be `0.13.0`.
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datafusion.apache.org
For additional commands, e-mail: commits-help@datafusion.apache.org