|author||David Grove <firstname.lastname@example.org>||Thu Sep 21 20:29:00 2023 -0400|
|committer||GitHub <email@example.com>||Thu Sep 21 20:29:00 2023 -0400|
config for runtime-php 1.19.0 (#424) * config for runtime-php 1.19.0 * configs for runtime-java-1.19 and runtime-nodejs-1.22
This project provides the Apache OpenWhisk project‘s Release Managers with the instructions and automation needed to ensure that project releases comply with both the Apache Software Foundation’s (ASF) Release Creation Process and Release Policy.
Specifically, this project documents the steps a Release Manager must take to make a release of an OpenWhisk software component and provides scripts and tool support to reduce the number of manual steps and potential for human error during the release process. Script support is provided for:
All release artifacts must be built and signed by a project Release Manager on their own machine to ensure proper security of signing keys and the integrity of the release artifacts.
Any OpenWhisk committer may take on the role of a Release Manager. The first time you serve as a Release Manager, you will need to prepare your machine by following the Release Manager Setup Instructions.
Please follow the process described in the Detailed Instructions for Release Managers.
Release candidates of Apache OpenWhisk components are published to the release candidate staging area during the voting process. These release candidates are not Apache Releases and are not intended for end users.
The following table can be used by Release Managers to check the status of all project repositories that produced releasable software components: