Apache openwhisk release

Clone this repo:
  1. 5f921bb openwhisk-client-js v3.21.2 (#335) by rodric rabbah · 4 weeks ago master
  2. 56445f1 document apigw 1.0.0 rc1 (#334) by David Grove · 8 weeks ago
  3. ddcbaa1 Updates repository status table to include wskdebug (#333) by Morgan Langlais · 8 weeks ago
  4. 3dbf2cf document wskdebug 1.2.0 (#332) by David Grove · 3 months ago
  5. 35e6ae7 exclude wskdebug.js from executable check to support new openwhisk-wskdebug repo (#330) by Alexander Klimetschek · 3 months ago

Apache OpenWhisk Project Release Management

License Build Status

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 where possible provides scripts and tool support to reduce the number of manual steps and potential for human error during the 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:

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