From a321bf8f391cec49ce108c95c54b51a17b133aa7 Mon Sep 17 00:00:00 2001 From: Jark Wu Date: Mon, 21 Sep 2026 19:03:32 +0800 Subject: [PATCH 1/5] [docs] Update release promotion wait time Align the release guide with the current ASF policy by replacing the outdated 24-hour wait with the one-hour post-upload requirement for download page updates and announcement emails. Co-Authored-By: Codex AI-Model: gpt-5 AI-Contributed/Feature: 4/4 AI-Contributed/UT: 0/0 --- website/community/how-to-release/creating-a-fluss-release.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/community/how-to-release/creating-a-fluss-release.mdx b/website/community/how-to-release/creating-a-fluss-release.mdx index 640496ae80..4a577141aa 100644 --- a/website/community/how-to-release/creating-a-fluss-release.mdx +++ b/website/community/how-to-release/creating-a-fluss-release.mdx @@ -848,14 +848,14 @@ In [GitHub Milestones](https://github.com/apache/fluss/milestones), mark the cur ## Promote the release +Once the release has been finalized, wait at least one hour after uploading the new release before updating the project download page or sending the announcement emails, in accordance with the [ASF release policy](https://www.apache.org/legal/release-policy.html#how-should-releases-be-announced). + ### Merge website pull request Merge the website pull requests for the release blog and download page that were created in the [Prepare for the release](#9-pull-requests-for-release-blog-and-downloads) step. ### Apache mailing lists -Once the release has been finalized, the last step of the process is to promote the release within the project and beyond. Please wait for 24h after finalizing the release in accordance with the [ASF release policy](https://www.apache.org/legal/release-policy.html#release-announcements). - Announce on the dev@ mailing list that the release has been finished. Announce on the release on the user@ mailing list, listing major improvements and contributions. From 235997974fa37f97dceed7c11335bbb70453e38d Mon Sep 17 00:00:00 2001 From: Jark Wu Date: Mon, 21 Sep 2026 19:10:11 +0800 Subject: [PATCH 2/5] [docs] Verify public release artifacts before promotion Require release managers to confirm that the Apache downloads, Maven, PyPI, and crates.io artifacts are publicly available before merging website updates or sending announcements. Co-Authored-By: Codex AI-Model: gpt-5 AI-Contributed/Feature: 9/9 AI-Contributed/UT: 0/0 --- .../how-to-release/creating-a-fluss-release.mdx | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/website/community/how-to-release/creating-a-fluss-release.mdx b/website/community/how-to-release/creating-a-fluss-release.mdx index 4a577141aa..8ffca88400 100644 --- a/website/community/how-to-release/creating-a-fluss-release.mdx +++ b/website/community/how-to-release/creating-a-fluss-release.mdx @@ -839,8 +839,10 @@ In [GitHub Milestones](https://github.com/apache/fluss/milestones), mark the cur **Checklist to proceed to the next step** - Maven artifacts released and indexed in the Maven Central Repository (usually takes about a day to show up) -- Source & binary distributions available in the release repository of https://dist.apache.org/repos/dist/release/fluss/ +- Source & binary distributions available on `https://downloads.apache.org/fluss/fluss-${RELEASE_VERSION}/` - Helm Chart package available in the release repository of https://dist.apache.org/repos/dist/release/fluss/helm-chart/ +- Python client artifacts available on [PyPI](https://pypi.org/project/pyfluss/) +- Rust client crate available on [crates.io](https://crates.io/crates/fluss-rs) - Dev repository https://dist.apache.org/repos/dist/dev/fluss/ is empty - Release tagged in the source code repository - Docker images for the release pushed to DockerHub ([apache/fluss](https://hub.docker.com/r/apache/fluss/tags), [apache/fluss-gateway](https://hub.docker.com/r/apache/fluss-gateway/tags), [apache/fluss-quickstart-flink](https://hub.docker.com/r/apache/fluss-quickstart-flink/tags)) @@ -848,7 +850,10 @@ In [GitHub Milestones](https://github.com/apache/fluss/milestones), mark the cur ## Promote the release -Once the release has been finalized, wait at least one hour after uploading the new release before updating the project download page or sending the announcement emails, in accordance with the [ASF release policy](https://www.apache.org/legal/release-policy.html#how-should-releases-be-announced). +Before merging the website pull requests or sending the announcement emails, make sure both of the following conditions are met: + +- At least one hour has passed since uploading the new release, in accordance with the [ASF release policy](https://www.apache.org/legal/release-policy.html#how-should-releases-be-announced). +- The corresponding release artifacts are publicly available from [downloads.apache.org](https://downloads.apache.org/fluss/), [Maven Central](https://search.maven.org/search?q=g:org.apache.fluss), [PyPI](https://pypi.org/project/pyfluss/), and [crates.io](https://crates.io/crates/fluss-rs). ### Merge website pull request From f8ea91f899bfd4b9616472720a6d0c62b1321644 Mon Sep 17 00:00:00 2001 From: Jark Wu Date: Mon, 21 Sep 2026 20:12:56 +0800 Subject: [PATCH 3/5] [docs] Include Docker images in promotion checks Require the final Fluss, Gateway, and Quickstart images to be publicly available on Docker Hub before website updates or release announcements. Co-Authored-By: Codex AI-Model: gpt-5 AI-Contributed/Feature: 2/2 AI-Contributed/UT: 0/0 --- website/community/how-to-release/creating-a-fluss-release.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/community/how-to-release/creating-a-fluss-release.mdx b/website/community/how-to-release/creating-a-fluss-release.mdx index 8ffca88400..3013b60aee 100644 --- a/website/community/how-to-release/creating-a-fluss-release.mdx +++ b/website/community/how-to-release/creating-a-fluss-release.mdx @@ -853,7 +853,7 @@ In [GitHub Milestones](https://github.com/apache/fluss/milestones), mark the cur Before merging the website pull requests or sending the announcement emails, make sure both of the following conditions are met: - At least one hour has passed since uploading the new release, in accordance with the [ASF release policy](https://www.apache.org/legal/release-policy.html#how-should-releases-be-announced). -- The corresponding release artifacts are publicly available from [downloads.apache.org](https://downloads.apache.org/fluss/), [Maven Central](https://search.maven.org/search?q=g:org.apache.fluss), [PyPI](https://pypi.org/project/pyfluss/), and [crates.io](https://crates.io/crates/fluss-rs). +- The corresponding release artifacts and Docker images are publicly available from [downloads.apache.org](https://downloads.apache.org/fluss/), [Maven Central](https://search.maven.org/search?q=g:org.apache.fluss), [PyPI](https://pypi.org/project/pyfluss/), [crates.io](https://crates.io/crates/fluss-rs), and Docker Hub ([apache/fluss](https://hub.docker.com/r/apache/fluss/tags), [apache/fluss-gateway](https://hub.docker.com/r/apache/fluss-gateway/tags), [apache/fluss-quickstart-flink](https://hub.docker.com/r/apache/fluss-quickstart-flink/tags)). ### Merge website pull request From 085228e084e0fab3f44e8ecd640edfaa19f6ba56 Mon Sep 17 00:00:00 2001 From: Jark Wu Date: Mon, 21 Sep 2026 20:21:46 +0800 Subject: [PATCH 4/5] [docs] Add artifact links to release announcement Include the final Fluss and Gateway Docker image pages together with the PyPI and crates.io release pages in the announcement email template. Co-Authored-By: Codex AI-Model: gpt-5 AI-Contributed/Feature: 10/10 AI-Contributed/UT: 0/0 --- .../how-to-release/creating-a-fluss-release.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/website/community/how-to-release/creating-a-fluss-release.mdx b/website/community/how-to-release/creating-a-fluss-release.mdx index 3013b60aee..e652d22fc1 100644 --- a/website/community/how-to-release/creating-a-fluss-release.mdx +++ b/website/community/how-to-release/creating-a-fluss-release.mdx @@ -887,6 +887,16 @@ Maven artifacts for Fluss can be found at: https://search.maven.org/search?q=g:org.apache.fluss%20AND%20v:1.0.0 +Docker images for Fluss can be found at: +https://hub.docker.com/r/apache/fluss/tags?name=1.0.0 +https://hub.docker.com/r/apache/fluss-gateway/tags?name=1.0.0 + +Python client artifacts can be found at: +https://pypi.org/project/pyfluss/1.0.0/ + +The Rust client crate can be found at: +https://crates.io/crates/fluss-rs/1.0.0 + Please check out the release blog post for an overview of this release: https://fluss.apache.org/blog/releases/1.0/ From 20fbe243deb8f728fce2b84a5afee5a5e139bc33 Mon Sep 17 00:00:00 2001 From: Jark Wu Date: Mon, 21 Sep 2026 20:51:52 +0800 Subject: [PATCH 5/5] [docs] Consolidate release promotion requirements Combine the artifact availability and one-hour waiting requirements into a single sentence, keeping the waiting period at the end. Co-Authored-By: Codex AI-Model: gpt-5 AI-Contributed/Feature: 5/5 AI-Contributed/UT: 0/0 --- .../community/how-to-release/creating-a-fluss-release.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/website/community/how-to-release/creating-a-fluss-release.mdx b/website/community/how-to-release/creating-a-fluss-release.mdx index e652d22fc1..a1116b3f30 100644 --- a/website/community/how-to-release/creating-a-fluss-release.mdx +++ b/website/community/how-to-release/creating-a-fluss-release.mdx @@ -850,10 +850,7 @@ In [GitHub Milestones](https://github.com/apache/fluss/milestones), mark the cur ## Promote the release -Before merging the website pull requests or sending the announcement emails, make sure both of the following conditions are met: - -- At least one hour has passed since uploading the new release, in accordance with the [ASF release policy](https://www.apache.org/legal/release-policy.html#how-should-releases-be-announced). -- The corresponding release artifacts and Docker images are publicly available from [downloads.apache.org](https://downloads.apache.org/fluss/), [Maven Central](https://search.maven.org/search?q=g:org.apache.fluss), [PyPI](https://pypi.org/project/pyfluss/), [crates.io](https://crates.io/crates/fluss-rs), and Docker Hub ([apache/fluss](https://hub.docker.com/r/apache/fluss/tags), [apache/fluss-gateway](https://hub.docker.com/r/apache/fluss-gateway/tags), [apache/fluss-quickstart-flink](https://hub.docker.com/r/apache/fluss-quickstart-flink/tags)). +Before merging the website pull requests or sending the announcement emails, verify that the corresponding release artifacts and Docker images are publicly available from [downloads.apache.org](https://downloads.apache.org/fluss/), [Maven Central](https://search.maven.org/search?q=g:org.apache.fluss), [PyPI](https://pypi.org/project/pyfluss/), [crates.io](https://crates.io/crates/fluss-rs), and Docker Hub ([apache/fluss](https://hub.docker.com/r/apache/fluss/tags), [apache/fluss-gateway](https://hub.docker.com/r/apache/fluss-gateway/tags), [apache/fluss-quickstart-flink](https://hub.docker.com/r/apache/fluss-quickstart-flink/tags)), and ensure that at least one hour has passed since uploading the new release, in accordance with the [ASF release policy](https://www.apache.org/legal/release-policy.html#how-should-releases-be-announced). ### Merge website pull request