Google Git
Sign in
apache / openwhisk-release / refs/tags/1.12.0-incubating-runtimes
tagb02ae243834c80a1817947a97d60467098fe2bd8
taggerVincent Hou <shou@us.ibm.com>Tue Sep 25 15:05:25 2018 -0400
object90fd82fb8d4ee038fe4b505849e39e91e5eaec64 
Release 6 runtimes of 1.12.0 under apache.
commit90fd82fb8d4ee038fe4b505849e39e91e5eaec64[log] [tgz]
authorVincent <shou@us.ibm.com>Mon Sep 10 15:12:46 2018 -0400
committerPriti Desai <pdesai@us.ibm.com>Mon Sep 10 12:12:46 2018 -0700
tree15789f049db12c67510d00efd6cbca56b52f7ed1
parent60a8b952f462891027d1e8aa7840e14aa92e1366 [diff]
Add document update based on the parameter UPDATE_DOC for release (#237)
1 file changed
tree: 15789f049db12c67510d00efd6cbca56b52f7ed1
  1. archive/
  2. docs/
  3. releases/
  4. tools/
  5. .travis.yml
  6. LICENSE.txt
  7. NOTICE.txt
  8. README.md
README.md

Apache OpenWhisk Project Release Management

License Build Status

The primary goal of this project is to provide the Apache OpenWhisk project‘s Release Managers the instructions and automation needed to guarantee a release complies with both the Apache Software Foundation’s (ASF) Release Creation Process and Release Policy.

Specifically, this repository provides Release Management of all designated Apache OpenWhisk project repositories, by automating:

  • Verification of the source code LICENSE and NOTICE files
  • Building & deploying the OpenWhisk platform
  • Running Build Verification Tests (BVT)
  • Generating CHANGELOGs for each project repository (since last release)
  • Packaging and signing source code (compressed archives) and binaries
  • publishing the artifacts to the approved Apache directories

all in accordance with Apache guidelines.

Release Process

Methodology

This project uses Travis CI as the automated integration build tool to streamline the release process of Apache OpenWhisk. Stages can be applied to build different jobs, which are able to run either in sequential or parallel. Artifacts can be shared across different jobs by using the cache feature in Travis, as different jobs run on different virtual machines.

Instructions

Please follow the Instructions for Release Managers.

Publishing

Staged candidate releases of Apache OpenWhisk artifacts are published to the approved staging repository path under Apache with all required PGP singatures:

Once candidates are approved, in accordance with required release processes and policies, their artifacts can be moved from the staging path to the approved release path:

Project status

The following table can be used by Release Managers to get quickly check the status of all project repositories that are currently included the current release plan:

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.
  • The Slack badge is hyperlinked to the corresponding repository's public Slack channel (if one exists).
  • LICENSE and NOTICE file process and compliance tracking can be found here: license_compliance.md

References

Disclaimer

This project is still “in development” with many steps still in the process of being automated and brought into compliance. We welcome any reviews, comments or contributions to help us complete and improve any part of the process.