Hi everyone,

While finalizing the Flink Agents 0.4.0 release, I noticed that both the Flink 
release guide [1] and the Flink Agents release guide [2] ask release managers 
to wait 24 hours before promoting a release, citing ASF release policy.

The current Infra guidance [3] recommends checking that the artifacts are 
available on downloads.apache.org, then waiting one hour for caches to refresh 
before announcing the release. Apache switched from download mirrors to a CDN 
in 2021 [4], so the 24-hour wording may have been carried over from the 
previous mirror infrastructure.

Is there a Flink-specific reason to retain the 24-hour waiting period? If not, 
would it make sense to update both guides to follow the current Infra guidance, 
while still verifying that the public download links work and that Maven 
Central and PyPI artifacts are available where applicable?

For the current Flink Agents release, I will follow the existing 24-hour 
guidance.

[1] https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
[2] https://github.com/apache/flink-agents/discussions/294
[3] 
https://infra.apache.org/release-publishing.html#release-distribution-availability-schedule
[4] https://www.apache.org/history/mirror-history.html

Best,
Wenjin

Reply via email to