Thanks for starting this thread and thanks a lot for verifying the download page for a lot of podlings!
For previewing a staging website, with .asf.yaml config, there is a way [1] to do so self-served by any (P)PMC. And I agree that we should spread such practices to every project. [1] https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#staging-a-web-site-preview-domain For example, to recommend every project's verifying release docs (like [2]) have a check item to verify the (staged) download page. And instruct the RM to build such a staged page. [2] https://opendal.apache.org/community/committers/verify Best, tison. sebb <seb...@gmail.com> 于2024年4月23日周二 19:52写道： > The primary mission of the ASF is to produce open SOURCE, so it seems > to me that an essential part of a release is a download page with > properly constituted links to the source bundle and the associated > download verification files. > > However, no attention seems to be given to this aspect of a release, > vital though it is. > > Obviously, the current download page cannot be updated with the > details of an upcoming release, but there are ways of providing access > to a staging website which shows how the page will look. > > Sebb > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
