Apache OpenWhisk Project Release Management

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:

• Packaging and signing source code (compressed archives)
• Verification of LICENSE and NOTICE files, source code license headers, and other formal aspects of a release candidate
• Publishing release artifacts to the proper staging and release Apache distribution servers
• Generation of a VOTE email for a release candidate

Release Process

Methodology

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.

Being a Release Manager

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.

Details of Making a Release

Please follow the process described in the Detailed Instructions for Release Managers.

Publishing Release Candidates and Releases

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.

If a release candidate is formally approved for release, it will be removed from the staging area, distributed from the release distribution server, and listed on the Apache OpenWhisk Downloads page.

Apache OpenWhisk Git Repository Status

The following table can be used by Release Managers to check the status of all project repositories that produced releasable software components:

Repository	Travis (Master)	ASF LICENSE	ASF NOTICE	ScanCode
openwhisk			NOTICE	scan.sh
openwhisk-apigateway			NOTICE	build.sh
openwhisk-catalog			NOTICE	build.sh
openwhisk-cli			NOTICE	test_openwhisk.sh
openwhisk-client-go			NOTICE	build.sh
openwhisk-client-js			NOTICE	scancode.sh
openwhisk-composer			NOTICE	scancode.sh
openwhisk-deploy-kube			NOTICE	scancode.sh
openwhisk-package-alarms			NOTICE	build.sh
openwhisk-package-cloudant			NOTICE	build.sh
openwhisk-package-kafka			NOTICE	build.sh
openwhisk-runtime-docker			NOTICE	build.sh
openwhisk-runtime-dotnet			NOTICE	build.sh
openwhisk-runtime-go			NOTICE	build.sh
openwhisk-runtime-java			NOTICE	build.sh
openwhisk-runtime-nodejs			NOTICE	build.sh
openwhisk-runtime-php			NOTICE	build.sh
openwhisk-runtime-python			NOTICE	build.sh
openwhisk-runtime-ruby			NOTICE	build.sh
openwhisk-runtime-rust			NOTICE	build.sh
openwhisk-runtime-swift			NOTICE	build.sh
openwhisk-wskdebug			NOTICE	scancode.sh
openwhisk-vscode-extension			NOTICE	scancode.sh
openwhisk-intellij-plugin			NOTICE	scancode.sh

Status notes:

• The Travis build status badge is hyperlinked to the corresponding repository's Travis CI dashboard's "branches" page.
• The ASF License badge is hyperlinked to the corresponding repository's LICENSE file.
• The ASF NOTICE column text links to the corresponding repository's NOTICE file.
• The ScanCode column text is hyperlinked to the corresponding repository's build file that executes the scancode utility.
  • The ASF scan configuration for all repos. can be found here: ASF-Release.cfg.

References

• Apache Release Creation Process
• Apache Release Policy
• Apache OpenWhisk Project License Header Policy