[docs] Update release promotion wait time

website/community/how-to-release/creating-a-fluss-release.mdx

@@ -839,23 +839,25 @@ 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))
 - Milestone marked as released in GitHub
 
 ## Promote the release
 
+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
 
 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.
@@ -882,6 +884,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/