[docs] Update release promotion wait time - #4459
Merged
Merged
Conversation
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 <noreply@openai.com> AI-Model: gpt-5 AI-Contributed/Feature: 4/4 AI-Contributed/UT: 0/0
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 <noreply@openai.com> AI-Model: gpt-5 AI-Contributed/Feature: 9/9 AI-Contributed/UT: 0/0
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 <noreply@openai.com> AI-Model: gpt-5 AI-Contributed/Feature: 2/2 AI-Contributed/UT: 0/0
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 <noreply@openai.com> AI-Model: gpt-5 AI-Contributed/Feature: 10/10 AI-Contributed/UT: 0/0
Combine the artifact availability and one-hour waiting requirements into a single sentence, keeping the waiting period at the end. Co-Authored-By: Codex <noreply@openai.com> AI-Model: gpt-5 AI-Contributed/Feature: 5/5 AI-Contributed/UT: 0/0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
The release guide still asks release managers to wait 24 hours after finalizing a release before announcing it. The current ASF release policy instead requires waiting at least one hour after uploading a new release before updating the project download page or sending announcement emails. Promotion should also wait until the release artifacts are publicly available from all supported distribution channels.
Brief change log
Tests
git diff --checknpm run build -- --no-minify; the final link check remains blocked by pre-existing broken links in the Fluss 0.7 and 0.8 release blog posts.API and Format
No API or storage format changes.
Documentation
Updates the release management guide to match the current ASF release policy.
Generative AI disclosure