Hi all, I would like to start a discussion regarding a possible release of Apache OpenServerless.
The release would include various OpenServerless components: Apache OpenServerless Cli, Apache OpenServerless Tasks, Apache OpenServerless Operator, Apache OpenServerless DevContainer, Apache OpenServerless Runtimes, Apache OpenServerless Streamer and Apache OpenServerless Admin Api. Before preparing the release candidate, I’d like to gather feedback from the community about these two facts: 1) We should designate a release manager, as stated in the guidelines ( https://infra.apache.org/release-publishing.html). 2) We should find a way to comply with the release rules ( https://infra.apache.org/release-publishing.html), given that currently, the OpenServerless installation requires the CLI to download tasks, which in turn starts the operator, and various docker images are installed inside a kubernetes cluster from GH registry. This seems to be contrary to the following ASF policies: - A release must be self-contained and reproducible. - A release must not download binaries from non-ASF infrastructure during the build. - GitHub (including GHCR: ghcr.io/apache/...) is not ASF release infrastructure. Many other release-related topics will probably derives from these. Please share your thoughts on this topic. Thanks, Bruno -- The life is short.. live at your best!
