| commit | 42481eccf4a2e4317b33576f5fa8095b12bae468 | [log] [tgz] |
|---|---|---|
| author | Vincent <shou@us.ibm.com> | Tue Mar 27 04:50:34 2018 -0400 |
| committer | Ying Chun Guo <guoyingc@cn.ibm.com> | Tue Mar 27 16:50:34 2018 +0800 |
| tree | 72c790aa4369135f8fe55a17fcabf30b796042e3 | |
| parent | 915edf15cea20d287d3606b819256957837b015c [diff] |
Publish the binaries of openwhisk cli and wskdeploy (#69) This PR adds the support to push the binaries of openwhisk cli and wskdeploy into the staging url in Apache.
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.
As a release manger of OpenWhisk, please visit OpenWhisk Release tutorial.
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.
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.
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. Please visit License_Compliance for detailed information.
We need to upload all artifacts to project’s subdirectory in Apache channel. This step needs to be implemented in Travis build.
To find the specifications about how to implement the Apache Release process for OpenWhisk project set, please visit the following page.
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.