This is a document for creating releases in OpenWhisk. It documents the proposed release process and will be updated as we move forward.
Release planning
OpenWhisk releases are created weekly.
Prerequisites for release managers
to do...
Release management tasks
- Make sure that an appropriate version for the release is entered in Jira and that all the related issues have been resolved.
- Create a new version in JIRA for the next release.
- Copy the generated RELEASE-NOTES.txt and paste in the release repo.
Build and deploy the release artifacts with bash script. See below for the exact steps.
- Send an announcement email to openwhisk dev mailing list
Steps to build the release artifacts
Individual component release
All components should be tagged with semantic versioning. Release command is run in each repo.
make release
The script will:
- run automated tests of released component; if failed, stop releasing here
- if passed, automatically increment minor tag version (e.g. 0.0.1 to 0.0.2) and ask release person to confirm or change it
- build and tag the docker image with this version
- push docker image to Docker Hub
- create release tag in GitHub
System release
This release does not produce any functional artifact, it only deploys the latest versions of each components.
- Update the version file to have the latest component versions.
- Release command is run in the release repo.
make release
The script will:
- automatically increment minor tag version (e.g. 0.0.1 to 0.0.2) and ask release person to confirm or change it
- deploy a local openwhisk environment with docker-compose
- (system test) run create / invoke / delete hello-world action on the newly deployed cluster
- create release tag in GitHub