[incubator-openwhisk-release] branch master updated: Describing the signature for the release and the Apache repos (#24)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

daisyguo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-openwhisk-release.git


The following commit(s) were added to refs/heads/master by this push:
     new bd70d6a  Describing the signature for the release and the Apache repos (#24)
bd70d6a is described below

commit bd70d6a24b9da01e4117e1a3261b973ac74aadef
Author: Vincent <sh...@us.ibm.com>
AuthorDate: Wed Feb 7 20:41:40 2018 -0500

    Describing the signature for the release and the Apache repos (#24)
    
    Reviewed and merged.
---
 docs/work_items.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/work_items.md b/docs/work_items.md
index d9cb41e..c3a8b64 100644
--- a/docs/work_items.md
+++ b/docs/work_items.md
@@ -83,14 +83,19 @@ we need to figure out how to package the artifacts differently for different lan
 consistent build environment. OpenWhisk core is based on Scala, CLI is based on Go, wskdeploy is based on Go, api gateway
 is based on lua, runtime project may be based on its native runtime language, etc. 
 
+Another important item in this step is to sign the artifacts cryptographically for the release. We need to figure out
+how to do it, either in Travis CI, Jenkins pipeline, or any other building tools.
+
 **Work bulletins**:
 - Investigate how to package the artifacts with existing tools, like Gradle, Maven, any other building plugins, etc.
 - Investigate how the tools works on the source code differently, according to different languages
 - Implement the script to package the artifacts
+- Sign the artifacts cryptographically for the staging and release
 
 ## 7. Upload the artifacts into staging repository for release vote ([open issue](https://github.com/apache/incubator-openwhisk-release/issues/21))
 
 Upload the artifacts including source code, compiled packages, etc into the staging repository for vote.
+This is the [staging directory of Apache projects](https://dist.apache.org/repos/dist/dev/incubator/openwhisk/) for OpenWhisk.
 
 **Work bulletins**:
 - Investigate how to upload the artifacts to a staging repository with existing tools, like Gradle, Maven, any other
@@ -101,7 +106,7 @@ building plugins, etc
 ## 8. Release the artifacts ([open issue](https://github.com/apache/incubator-openwhisk-release/issues/22))
 
 When we reach an agreement on the candidate located in the staging repository, the artifacts need to be move to the Apache\
-directory for release.
+directory for release. This is the [release directory of Apache](https://dist.apache.org/repos/dist/release/incubator/openwhisk/) for OpenWhisk.
 
 **Work bulletins**:
 - Migrate artifacts from the staging repository to Apache directory

-- 
To stop receiving notification emails like this one, please contact
daisyguo@apache.org.