mrutkows closed pull request #43: Add the documentation to describe automated 
mode of release

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/docs/ b/docs/
index 70c692b..0f1ac98 100644
--- a/docs/
+++ b/docs/
@@ -19,3 +19,25 @@ the artifacts in the staging directory and the Apache 
release directory.
   9. If the vote fails - configure the file config.json and resume from step 3
   10. [Publish the release artifacts to Apache release 
   11. Announce the release
+## Automated mode of Release Process
+The release manager can take full advantage of Travis CI to implement the 
release process. The only manual step is to
+configure the release information, by editing the configuration file 
_config.json_. Please refer to [edit configuration 
+for the information able to be configured.
+* **PR-based Travis build**: the Travis build triggered by a pull request. 
Each time the file config.json is ready, release
+manager can submit a pull request to the master branch of OpenWhisk release 
repository. Based on the result of the Travis build,
+we know whether the configurations in config.json can be used as a candidate 
to release. This type of Travis build will
+download the source code, generate the artifacts, sign the artifacts, install 
the OpenWhisk services and run the test cases.
+* **Push-based Travis build**: the Travis build triggered by a push into 
master branch. When a PR with new configurations
+is accepted, the release manager can merge it to kick off this type of Travis 
build. On top of the tasks done by PR-based
+Travis build, it will upload the artifacts into the staging directory.
+* **Tag-based Travis build**: the Travis build triggered by git tag. After the 
vote succeeds in the community, we decide to
+move the artifacts from the staging directory to the Apache release directory. 
This type of Travis build is responsible
+for this task.
+In summary, the release process of OpenWhisk is the process of developing the 
configuration file _config.json_ for a
+certain release.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to