openwhisk-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [incubator-openwhisk-release] branch master updated: Add the description of this repository into README (#4)
Date Tue, 23 Jan 2018 22:23:21 GMT
This is an automated email from the ASF dual-hosted git repository.

mrutkowski pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new cbfead7  Add the description of this repository into README (#4)
cbfead7 is described below

commit cbfead7bde960ae12ed655a8cad348beb7850617
Author: Vincent <>
AuthorDate: Tue Jan 23 17:23:19 2018 -0500

    Add the description of this repository into README (#4)
 .travis.yml              |  5 -----                | 43 ++++++++++++++++++++++++++++++++++++++++++-
 tools/travis/config.json |  2 +-
 3 files changed, 43 insertions(+), 7 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 2cd1331..4147f1a 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -2,11 +2,6 @@ sudo: required
 group: deprecated-2017Q3
-language: scala
-   - 2.11.8
   - docker
diff --git a/ b/
index 47c3c02..51c2a00 100644
--- a/
+++ b/
@@ -1 +1,42 @@
-# incubator-openwhisk-release
+# OpenWhisk Graduate and Release Management
+[![Build Status](](
+This project is responsible for the Release Management of OpenWhisk projects, by automating
the processes of verifying
+the source code, building & deploying OpenWhisk, packaging the source code and binaries,
publishing the artifacts to
+the specified online directories, etc. OpenWhisk is a serverless event-based programming
service and currently an Apache
+Incubator project. The ultimate goal of this project is to guarantee the compliance with
the Apache release requirements
+for OpenWhisk projects.
+We use Travis CI as the automated integration build tool to streamline the release process
of 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 cache in Travis, as different jobs run on different virtual machines.
+# How to release an Apache project
+## Release Approval
+Apache requires a minimum of three positive votes and more positive than negative votes MUST
be cast, in order to release.
+Release manager of OpenWhisk sends a release note to the OpenWhisk mailing for votes, and
opens the mail for 72 hours.
+We can create JIRA issue for this release and close it when the requirement is met and ready
for release. This step can
+be done manually by the release manager, beyond the scope of this project.
+An example of the release note can be found at the following link: [example of release note](
+## Artifacts
+We need to package the source code and the complied binaries separately. Each of them should
be signed cryptographically.
+The package of source code needs to provide the installation script for users to deploy a
full OpenWhisk environment.
+We target to implement this step in Travis build.
+## Licensing
+All the source code has to be compliant with Apache Licensing Policy, by adding the LICENSE
file, NOTICE file to each
+repository and the release package, and adding Licensing headers to each source code file.
+## Release distribution
+We need to upload all artifacts to project’s subdirectory in Apache channel. This step
needs to be implemented in Travis build.
+# Reference
+[Apache release policy](
+# Important Note
+There can be some missing steps in the release process described above for Apache projects,
which will be implemented in
+future. We welcome any comments and contributions.
diff --git a/tools/travis/config.json b/tools/travis/config.json
index 5226aa9..e4077f0 100644
--- a/tools/travis/config.json
+++ b/tools/travis/config.json
@@ -7,7 +7,7 @@
   "incubator_openwhisk": {
-    "hash": "fc98e9a"
+    "hash": "a891e06"
   "incubator_openwhisk_catalog": {
     "hash": "ad24d4c"

To stop receiving notification emails like this one, please contact

View raw message