Before generating any release artifacts, it is recommended to verify the source code by checking the license headers and the existence of LICENSE and NOTICE files under each repository. This step can be done by running the following script under the directory tools:
$ ./verify_source_code.sh
This script will generate a RAT report called rat.txt under the directory <local_release_dir>/openwhisk_release/openwhisk_sources/target. You can find the status of license header in this RAT report. In addition, you can check the existence of LICENSE and NOTICE from the terminal, after running this script.
The artifacts to be made in this step consists of the source code packages, binary packages and docker image packages. As the deliverable of the first phase, we currently only build the source code packages. Binary and docker image are on our future agenda.
After downloading the source code, we can run the following script under tools to generate the artifacts for each OpenWhisk project:
$ ./package_source_code.sh
This script will create a source code package file of source code suffixed with tar.gz for each project, under <local_release_dir>/openwhisk_sources/openwhisk/apache-openwhisk-<version>. The key version is defined in config.json.
We can run the following script under tools to add or update the documents for the current release:
$ ./package_doc.sh
This script will copy all the files under releases/ into the designated directory, <local_release_dir>/openwhisk_sources/openwhisk/apache-openwhisk-<version>/doc/.