[Bug]: download page problems

[sebbASF]

What happened?

Download pages for releases must use closer.lua for artifacts, and must use downloads.apache.org for the corresponding hashes and sigs.

The archive server is only allowed for older non-supported releases.

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[liferoad]

Please check https://beam.apache.org/contribute/

[github-actions]

This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

[sebbASF]

Is anyone going to review this? The download page at
https://beam.apache.org/get-started/downloads
has lots of problems.

It must not use the archive server for current releases and must use closer.lua for current artifacts.

[liferoad]

To be clear, do you mean we should update all URLs to something like https://www.apache.org/dyn/closer.lua/beam/2.67.0/apache-beam-2.67.0-source-release.zip?

[sebbASF]

For current artifacts, yes.
Hashes, sigs and KEYS for current artifacts must point directly to the files under
https://downloads.apache.org/beam/

Older artifacts (and their sigs, hashes and KEYS) that are no longer maintained can be linked to the archive server.

See https://infra.apache.org/release-download-pages.html

[liferoad]

ok. Is #36174 good? If so, I will update our release guide later.