Call for Topics for Tech Interchange Call tomorrow Wednesday (June 11)

[Vincent S Hou]

Hi OpenWhiskers,

Please send me by emails or slack your topics, to be discussed on tomorrow's 
bi-weekly technical meeting.
Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [VOTE] Apache OpenWhisk graduation to Top Level Project

[Vincent S Hou]

Thank all the great efforts by OpenWhisk contributors. It is time for us to 
graduate.
All the official modules, like openwhisk core, catalog, cli, runtimes, etc, 
have successfully gone through one or multiple releases under Apache as 
incubator.
We have been familiar with all the legal processes of Apache. The modules have 
been mature enough to evolve as top level project.

I vote: +1 Apache OpenWhisk should graduate. 


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Rodric Rabbah  wrote: -
To: dev@openwhisk.apache.org
From: Rodric Rabbah 
Date: 06/04/2019 05:26PM
Subject: [EXTERNAL] [VOTE] Apache OpenWhisk graduation to Top Level Project

Hi all,

After a discussion among the Apache OpenWhisk community on the dev
mailing list [1], we have completed all Trademark transfers, and we
are now in the process of pruning the PMC roster, completing the
podling status page and completing the project maturity model [2].

Apache OpenWhisk entered the incubator on November 23 2016. Since
then, we have grown to be in the top 25 list of Apache projects by
GitHub Stars at 4041, have 229 unique contributors across all our
project repos, more than 2500 commits, and most importantly, our
community has grown and is diversified beyond the initial founding
contributors and organization.

The project has come a long way in embracing The Apache Way, in no
small part to our dedicated mentors and the community spirit that has
grown along this journey. We are operating well as an Apache project
and so we should take the next step.

As such, I am calling a vote for Apache OpenWhisk to graduate to a top
level project. If we agree that we should graduate to a top level
project, the next step will be to draft a Resolution [3] for the PPMC
and IPMC to vote upon.

Please take a minute to vote on whether or not Apache OpenWhisk should
graduate to a Top Level Project by responding with one of the
following:

 [ ] +1 Apache OpenWhisk should graduate.
 [ ] +0 No opinion
 [ ] -1 Apache OpenWhisk should not graduate (please provide the reason)

The VOTE is open for a minimum of 72 hours. Per Apache guidelines [4]
I will notify the incubator mailing list that a community vote is
under way.

Thank you.
-r
(on behalf of the Apache OpenWhisk PPMC)

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.apache.org_thread.html_8daa3a05148f54ca82458777e2b2b5e25ba99d39dcf8ce7dd85d0188-40-253Cdev.openwhisk.apache.org-253E=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=LFSSfkEdvRwfS3FkELMfDq_7zw2s2_TKfw_AXT9Dw2o=Gnn9hS-jCq6kxpUkV5YDjAvpeSZ2W9p1_XFdfvkjIa4=
 
[2] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_OPENWHISK_Project-2BMaturity-2BModel=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=LFSSfkEdvRwfS3FkELMfDq_7zw2s2_TKfw_AXT9Dw2o=qtLpjM8ULRYiBYtOmML-UfW6byo2BgbC0Qaz9HSJubc=
 
[3] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_pages_viewpage.action-3FpageId-3D115526932=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=LFSSfkEdvRwfS3FkELMfDq_7zw2s2_TKfw_AXT9Dw2o=YGyPOxDTHT-HjpQZb1_UMuX4dySHKqv0FH0AkPlJjpg=
 
[4] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__incubator.apache.org_guides_graduation.html-23community-5Fgraduation-5Fvote=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=LFSSfkEdvRwfS3FkELMfDq_7zw2s2_TKfw_AXT9Dw2o=oYAfkquuRCiMbdk0S-TF9_IG9jFe1OYc-qtxFDjBf2Q=
 

Re: Current status of Jenkins setup for OpenWhisk

[Vincent S Hou]

Hi OpenWhiskers,

I have already made the Jenkins pipeline working.
I resolved the issue about the constantly failing test case by enabling the 
memory limit of docker on each openwhisk VM.
Three VMs are able to run three instances of OpenWhisk deployment and test at 
the same time.

Normally the result will turn out passed for our code located in master branch 
of OpenWhisk. The pipeline is healthy now.
If the pipeline build fails, it could be due to the error of the PR. However, 
report the issues you find, if you believe it is caused by mistake of the 
pipeline.

Thank you.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 03/26/2019 11:26AM
Subject: Re: Current status of Jenkins setup for OpenWhisk

Hi folks,

I have improved the way how we utilize the three VMs for Jenkins pipeline.
Instead of using openwhisk1 as the edge service node, running all the services 
except invoker, we can also schedule openwhisk2 and openwhisk3 to run the edge 
service as well.

How to implement the distributed model to deploy openwhisk?

The deployment topology is orchestrated as below:
If openwhisk1 runs as the edge service, openwhisk2 runs invoker0 and openwhisk3 
runs invoker1.
If openwhisk2 runs as the edge service, openwhisk3 runs invoker0 and openwhisk1 
runs invoker1.
If openwhisk3 runs as the edge service, openwhisk1 runs invoker0 and openwhisk2 
runs invoker1.
 
Even three of these deployments are able to run at the same time, instead of 
one deployment at a time.
For safety reasons, I also added resource lock to each node in Jenkinsfile, so 
that even if the job is scheduled to a busy node, it will wait there till the 
previous job finishes.

I am now looking at the test to stop one of the invokers and run the designated 
tests. If you have any idea on how to do that, welcome to chime in.
Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 03/12/2019 10:59AM
Subject: Current status of Jenkins setup for OpenWhisk

Hi OpenWhiskers,

I have come back from my holiday last week, and officially start to work this 
week. During the past few days, I have made some progress in terms of getting 
the access to openwhisk VMs and Apache Jenkins.

Current state:
My apache ID has granted root access to the VMs:
openwhisk-vm1-he-de.apache.org
openwhisk-vm2-he-de.apache.org
openwhisk-vm3-he-de.apache.org

I am now able to use the command ssh openwhisk-vm1-he-de.apache.org -l  to access the VM via terminal.

My Apache ID has been added into the hudson-jobadmin group: 
https://whimsy.apache.org/roster/group/hudson-jobadmin, which means I have 
earned the admin access to Apache Jenkins environment at 
https://builds.apache.org/. I should be able to create build or pipeline.

I have granted the user "jenkins" root access within three of these VMs.

Work items to do:
Next, I will configured the ssh access among three of these VMs, since I plan 
to use one VM as the master, launching all the services except invoker, and the 
other two as designated nodes to launch invoker service.

Travis CI has already tested the case, when all the openwhisk services are 
installed on one server. I plan to use Jenkins to test openwhisk installed in a 
distributed way.

Welcome to chime in and add your comments, if you have any idea about how to 
use these three VMs for OpenWhisk.

Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: Current status of Jenkins setup for OpenWhisk

[Vincent S Hou]

Hi folks,

I have improved the way how we utilize the three VMs for Jenkins pipeline.
Instead of using openwhisk1 as the edge service node, running all the services 
except invoker, we can also schedule openwhisk2 and openwhisk3 to run the edge 
service as well.

How to implement the distributed model to deploy openwhisk?

The deployment topology is orchestrated as below:
If openwhisk1 runs as the edge service, openwhisk2 runs invoker0 and openwhisk3 
runs invoker1.
If openwhisk2 runs as the edge service, openwhisk3 runs invoker0 and openwhisk1 
runs invoker1.
If openwhisk3 runs as the edge service, openwhisk1 runs invoker0 and openwhisk2 
runs invoker1.
 
Even three of these deployments are able to run at the same time, instead of 
one deployment at a time.
For safety reasons, I also added resource lock to each node in Jenkinsfile, so 
that even if the job is scheduled to a busy node, it will wait there till the 
previous job finishes.

I am now looking at the test to stop one of the invokers and run the designated 
tests. If you have any idea on how to do that, welcome to chime in.
Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 03/12/2019 10:59AM
Subject: Current status of Jenkins setup for OpenWhisk

Hi OpenWhiskers,

I have come back from my holiday last week, and officially start to work this 
week. During the past few days, I have made some progress in terms of getting 
the access to openwhisk VMs and Apache Jenkins.

Current state:
My apache ID has granted root access to the VMs:
openwhisk-vm1-he-de.apache.org
openwhisk-vm2-he-de.apache.org
openwhisk-vm3-he-de.apache.org

I am now able to use the command ssh openwhisk-vm1-he-de.apache.org -l  to access the VM via terminal.

My Apache ID has been added into the hudson-jobadmin group: 
https://whimsy.apache.org/roster/group/hudson-jobadmin, which means I have 
earned the admin access to Apache Jenkins environment at 
https://builds.apache.org/. I should be able to create build or pipeline.

I have granted the user "jenkins" root access within three of these VMs.

Work items to do:
Next, I will configured the ssh access among three of these VMs, since I plan 
to use one VM as the master, launching all the services except invoker, and the 
other two as designated nodes to launch invoker service.

Travis CI has already tested the case, when all the openwhisk services are 
installed on one server. I plan to use Jenkins to test openwhisk installed in a 
distributed way.

Welcome to chime in and add your comments, if you have any idea about how to 
use these three VMs for OpenWhisk.

Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: LICENSE format?

[Vincent S Hou]

Hi James,

Please follow the format of 
https://github.com/apache/incubator-openwhisk-wskdeploy/blob/master/LICENSE.txt.
This is the correct approach, and we have verified with the Apache community.

First, whether to add appendix. yes.
Second, do we change the copyright to meet the requirement of our project? No, 
still keep Copyright [] [name of copyright owner].

Please raise an issue for devtool project to change the LICENSE format. Thank 
you.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-James Thomas  wrote: -
To: dev@openwhisk.apache.org
From: James Thomas 
Date: 03/25/2019 12:33PM
Subject: LICENSE format?

Should the LICENSE.txt files in the OpenWhisk project repos include the

 APPENDIX: How to apply the Apache License to your work.

section as-is from 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_licenses_LICENSE-2D2.0.txt=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=aQjldjIi7GndHy-lJxQCB2Q16BPW913XWPYrXxWvbfU=wAOyWfEFHUzS2ohx7TjosY-yiOHgUb4zQsHXQ2a6I-Y=
 OR is it
supposed to be applied following the instructions in those section, e.g.

 Copyright 2019 Some Name...

We have a variety of styles in different repos and it's not clear which we
should follow.

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Dwskdeploy_blob_master_LICENSE.txt=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=aQjldjIi7GndHy-lJxQCB2Q16BPW913XWPYrXxWvbfU=Yfz_nznzX0sWLnxwgOvxMQhppOMD1mOaTfAfm6JUo5Y=

and

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Ddevtools_blob_master_LICENSE.txt=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=aQjldjIi7GndHy-lJxQCB2Q16BPW913XWPYrXxWvbfU=WTgRHKB4JcU6hwwvwwWTeZQQwtPO7MMnB9RUaUqz4v0=

Can someone with more experience in this provide guidance on which is
correct?
-- 
Regards,
James Thomas

Re: [Bi-Weekly Tech Interchange] Call for agenda topics

[Vincent S Hou]

I would like to present the Jenkins CI for OpenWhisk.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Dascalita Dragos  wrote: -
To: dev@openwhisk.apache.org
From: Dascalita Dragos 
Date: 03/19/2019 12:08PM
Subject: [Bi-Weekly Tech Interchange] Call for agenda topics

Hi,
I'm starting this thread to start capturing topics to discuss for our call
tomorrow.
Please reply to this email to reserve your spot !

Bi-weekly Tech Interchange call details:
- Zoom: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_my_asfopenwhisk=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=4k5b6m3eq3AWF5UnQ_O8wXYfS0gQ-Q4bL0-nuqxWNis=tbRToEdvZdx_tpFXKR-W1dxIg94EOIN4JxWze8kVvKs=
- Wednesday March 20th
11AM EST(Eastern US)
5PM CET (Central Europe),
4PM UTC, 12AM CST (Beijing)

Thanks,
dragos

Re: [VOTE] release Apache OpenWhisk CLI 0.10.0-incubating

[Vincent S Hou]

+1 from me.

[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] DISCLAIMER is included.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[x] All files have license headers if necessary.
[x] No compiled archives bundled in source archive.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-James Thomas  wrote: -
To: dev@openwhisk.apache.org
From: James Thomas 
Date: 03/19/2019 08:15AM
Subject: Re: [VOTE] release Apache OpenWhisk CLI 0.10.0-incubating

+1

[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] DISCLAIMER is included.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[x] All files have license headers if necessary.
[x] No compiled archives bundled in source archive.

On Sat, 16 Mar 2019 at 18:57, David P Grove  wrote:

>
>
> This is a call to vote on releasing version 0.10.0-incubating of the Apache
> OpenWhisk CLI.
>
> The Apache OpenWhisk CLI provides the command line tooling for interacting
> with Apache OpenWhisk.
>
> This release comprises of source code distribution only. There are three
> modules (git repos) included in this CLI release. All artifacts were built
> by PR#249 in the openwhisk-release repo from the following Git commit IDs:
> * openwhisk-cli: eaf64ae
> * openwhisk-client-go: 4286a82
> * openwhisk-wskdeploy: 7d79fd7
>
> openwhisk-cli (55BEEB6D CDF621AB 7AA6098A 5DBCA55E 6D7E3B0C A3DAA7DF
> B44103F8 CE30ACC9 13411ECC BFF18519 3E142EC3 D27AA081 E1D47F63 14E9E708
> 90646EC7 C13756D6)
> src.tar.gz:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dcli-2D0.10.0-2Dincubating-2Dsources.tar.gz=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=Q3ePIMcrSrMTk5YRau4KJ3yonzOcphdte_KN8n07UJI=
> sha512 checksum:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dcli-2D0.10.0-2Dincubating-2Dsources.tar.gz.sha512=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=qir7ISkaEsAa9nDbXvqWREoSLrYkMFZsaKm--SJDlp4=
> signature:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dcli-2D0.10.0-2Dincubating-2Dsources.tar.gz.asc=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=fJrR3-25kgXmNsWMp7f_QAxzDLJXs94V8TU5qhk9lV8=
>
> openwhisk-client-go (068DBC87 533905DB D0089CAE 74FD0B91 109992D8 D843CAA4
> 01EA87B6 9CDC9550 6D555655 4679FF36 7A52414E DCC59126 E558085D 3E960DEB
> 18804581 6B2FA019)
> src.tar.gz:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dclient-2Dgo-2D0.10.0-2Dincubating-2Dsources.tar.gz=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=OOYCfesKrrDIXS0QA3AUk4Ulby14hUKXtmKnjYP-Ae4=
> sha512 checksum:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dclient-2Dgo-2D0.10.0-2Dincubating-2Dsources.tar.gz.sha512=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=lLtWohXlKMdewdg6uTQjhl_CMeEH8StqWKDEvJisYds=
> signature:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dclient-2Dgo-2D0.10.0-2Dincubating-2Dsources.tar.gz.asc=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=P85Rg_K65SyhW9oefaJd8kD3GcsQndGVBxI6pKbpFAA=TLbJxHCxkVIQIPwJNybBPqjZ-hbxTMyURiu8crWl3jg=
>
> openwhisk-wskdeploy (412B1E09 129F2884 A1D4E9DE 0A979B47 55A54FC5 61E1D328
> 325E8A12 AE504779 A2350B9F 4185582F 7782EEA5 AE9018CD 52E4AA4C 484B5211
> AA449B4B 9F9E2432)
> src.tar.gz:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D0.10.0-2Dincubating-2Drc1_openwhisk-2Dwskdeploy-2D0.10.0-2Dincubating-2Dsources.tar.gz=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHj

Re: [DISCUSS] graduation from the incubator

[Vincent S Hou]

I totally root for the graduation. To me, there is no blocker for OpenWhisk 
graduation under Apache, except something we can improve.

I have made some progress in terms of Jenkins pipeline build for OpenWhisk. 
Three of the VMs dedicated to OpenWhisk have been used as an distributed 
environment for openwhisk to deploy and test: 
https://builds.apache.org/view/O/view/OpenWhisk/job/openwhisk-test-pipeline/.

I am not sure if everyone can access this link and manually launch Jenkins 
build for OpenWhisk. I hope folks can give a test. This is the only thing I 
hope can be done before graduation.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: "OpenWhisk Dev" 
From: "David P Grove" 
Date: 03/15/2019 06:06PM
Subject: [DISCUSS] graduation from the incubator


I'd like to kick off a discussion to assess the project's readiness for
graduation from the incubator.

Per Rodric's recent stats [1], the community has developed nicely in terms
of code contribution.

We've released a number of software components following the Apache release
process.  We are in the midst of making our first "uber-release" across all
of our sub-components (expect at least 2 voting threads next week).

Overall I think the community is active.  Communication on the project
slack is frequent (avg of >160 messages a day) and is now digested daily to
the dev list. (See [2] for stats).

There are a couple procedural tasks we still need to complete, foremost
being the formal transfer of the OpenWhisk trademarks from IBM to the ASF.
But I think we can assume that these tasks will be completed and start
considering graduation in parallel.

Please share your thoughts,

--dave

[1]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.apache.org_thread.html_b2217c61caad5c7a0369699d06d44e5cf688d3cba982e354a45b8c78-40-253Cdev.openwhisk.apache.org-253E=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=29zSYpg--7xm2FpdH67pa8-BViED6kMm4TFRG8UbJZ8=6-QfzwikY26pJYG1gzQdCEF8M9XIaxwgo_ok7gWLsZ4=
[2]
https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_pages_viewpage.action-3FpageId-3D103091999=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=29zSYpg--7xm2FpdH67pa8-BViED6kMm4TFRG8UbJZ8=ERvvltgFZD20SHYfoI2C56IhYORzsm7IxA2FJbLZk9Q=

Current status of Jenkins setup for OpenWhisk

[Vincent S Hou]

Hi OpenWhiskers,

I have come back from my holiday last week, and officially start to work this 
week. During the past few days, I have made some progress in terms of getting 
the access to openwhisk VMs and Apache Jenkins.

Current state:
My apache ID has granted root access to the VMs:
openwhisk-vm1-he-de.apache.org
openwhisk-vm2-he-de.apache.org
openwhisk-vm3-he-de.apache.org

I am now able to use the command ssh openwhisk-vm1-he-de.apache.org -l  to access the VM via terminal.

My Apache ID has been added into the hudson-jobadmin group: 
https://whimsy.apache.org/roster/group/hudson-jobadmin, which means I have 
earned the admin access to Apache Jenkins environment at 
https://builds.apache.org/. I should be able to create build or pipeline.

I have granted the user "jenkins" root access within three of these VMs.

Work items to do:
Next, I will configured the ssh access among three of these VMs, since I plan 
to use one VM as the master, launching all the services except invoker, and the 
other two as designated nodes to launch invoker service.

Travis CI has already tested the case, when all the openwhisk services are 
installed on one server. I plan to use Jenkins to test openwhisk installed in a 
distributed way.

Welcome to chime in and add your comments, if you have any idea about how to 
use these three VMs for OpenWhisk.

Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: Agenda Items for Tech Interchange this Wed (December 5th)

[Vincent S Hou]

Hi Priti,

I would like to update the plan to implement Jenkins pipeline for OpenWhisk.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Moritz Raho  wrote: -
To: "dev@openwhisk.apache.org" 
From: Moritz Raho 
Date: 12/04/2018 12:26PM
Subject: Re: Agenda Items for Tech Interchange this Wed (December 5th)

Hi Priti,

If time permits, I would like to share a demo about a work in progress for the 
api-gateway. This might take around 10 minutes.
It’s a feature that allows the api-gateway to serve content in the place of web 
actions based on some custom return headers.
This is useful to web action developers that need to return a payload bigger 
than the response size limit.

Thanks!
Moritz

On 03.12.18, 21:13, "Priti Desai"  wrote:

Hello Whiskers,

It's time to collect topics for bi-weekly Tech Interchange this week 
(December 5th). Please send your agenda items here or message me 
(@pritidesai) on Slack. Also, please remind other whiskers to join the 
call. 

I have one on "OpenWhisk Catalog Installation using Whisk Deploy" for 5 
minutes.

I am confirming with Matt on what are we using this week, Zoom/Webex. Will 
send out update soon. 

Cheers
Priti

P.S.

CWIKI: 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FOPENWHISK%2FOpenWhisk%2BProject%2BWikidata=02%7C01%7Craho%40adobe.com%7C5fc888a9d5da4413536508d6595bc319%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636794647987240122sdata=UiZ5GhQUHpbIR8wozfG43C%2FepaZLeIfbOqnbU%2BgQZSg%3Dreserved=0


To view/add the recurring calendar entry click this link:

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcalendar.google.com%2Fevent%3Faction%3DTEMPLATE%26tmeid%3DM3RmZG04YW12cXVib2xwYzFycmEzYmFicGNfMjAxODA1MjNUMTUwMDAwWiBhcGFjaGVvcGVud2hpc2tAbQ%26tmsrc%3Dapacheopenwhisk%2540gmail.com%26scp%3DALLdata=02%7C01%7Craho%40adobe.com%7C5fc888a9d5da4413536508d6595bc319%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636794647987250131sdata=ImfytI6av6aNJ4cQPakm5sEpm5%2B0sTU6sJFzZ3%2BuU4Y%3Dreserved=0

Re: How to best run non-local tests in ASF (was: Performance tests for OpenWhisk)

[Vincent S Hou]

Great thanks to Adobe Inc for the donation to OpenWhisk.
I just touched based with Carlos about how we setup and Jenkins environment for 
OpenWhisk. I will pick up the Jenkins work for OpenWhisk.
For anyone, who is interested in the Jenkins Pipeline for OpenWhisk. Welcome to 
help.
Thank you.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Rodric Rabbah  wrote: -
To: dev@openwhisk.apache.org
From: Rodric Rabbah 
Date: 11/07/2018 02:31PM
Subject: Re: How to best run non-local tests in ASF (was: Performance tests for 
OpenWhisk)

Thank you Adobe Inc and the Adobe team for the donation and making it possible 
to have infra for the project! And thanks Carlos for also pushing this forward.

-r

> On Nov 7, 2018, at 2:25 PM, Carlos Santana  wrote:
> 
> We got the 3 VMs Woot !!
> it only took 6 months
> 
> The INFRA ticket [1] that I opened back in June I was able to close today.
> I ran a quick test from a Jenkins job to check the 3 VMs, I added the
> information in our Wiki page [2]
> 
> On behave of the Apache OpenWhisk (Incubating) community I want to thank
> Adobe Inc. for the donation of $1,000 (one thousand) US dollars to the ASF
> to allow us get these VMs dedicated to the project and be able to run
> Playground CICD tests.
> 
> [1] https://issues.apache.org/jira/browse/INFRA-16668
> [2]
> https://cwiki.apache.org/confluence/display/OPENWHISK/Jenkins+VMs+for+Playgrounds

Re: Tech Interchange call this Wed. Nov. 07 - add agenda topics here

[Vincent S Hou]

Hi folks,

Just a reminder: please send me the topic you would like to present on 
tomorrow's meeting. Thx.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 11/05/2018 09:41PM
Subject: Tech Interchange call this Wed. Nov. 07 - add agenda topics here

Hi OpenWhiskers,
 
Please send me the any agenda items you'd like to present at the Tech 
Interchange call this Wednesday (Nov 07).
 
Call details:
 
Web Meeting: Tech Interchange (bi-weekly):
- Day-Time: Wednesdays, 11AM EDT (Eastern US), 5PM CEST (Central Europe),
4PM UTC, 12PM CST (Beijing)
- Zoom: https://zoom.us/my/asfopenwhisk
 
Thanks,

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Tech Interchange call this Wed. Nov. 07 - add agenda topics here

[Vincent S Hou]

Hi OpenWhiskers,
 
Please send me the any agenda items you'd like to present at the Tech 
Interchange call this Wednesday (Nov 07).
 
Call details:
 
Web Meeting: Tech Interchange (bi-weekly):
- Day-Time: Wednesdays, 11AM EDT (Eastern US), 5PM CEST (Central Europe),
4PM UTC, 12PM CST (Beijing)
- Zoom: https://zoom.us/my/asfopenwhisk
 
Thanks,

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: Tech Interchange call this Wed. Oct. 24 - add agenda topics here

[Vincent S Hou]

Carlos,

I like to announce the work of the package renaming from whisk to 
org.apache.openwhisk for openwhisk main repository, asking folks to be aware of 
the change.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Carlos Santana  wrote: -
To: dev@openwhisk.apache.org
From: Carlos Santana 
Date: 10/23/2018 09:38AM
Subject: Re: Tech Interchange call this Wed. Oct. 24 - add agenda topics here

Thanks Michele looking forward +1


On Tue, Oct 23, 2018 at 7:33 AM Michele Sciabarra 
wrote:

> I would like to show my new "actionloop" based Scala runtime!
> Yes I know,  it is already possible to use Scala with the Java runtime.
> But you have to compile, create a jar, include libraries
> This one is based on the scripting shell "Ammonite" http://ammonite.io
> and works more like js and python.
>
> Here is a  simple demo:
>
> https://openwhisk.eu-de.bluemix.net/api/v1/web/sciabarra_cloud/scala/calc
>
> And this is the source code:
>
> 
> import play.api.libs.json._
> import scala.util.Try
>
> def main(args: JsObject) : JsObject = {
> val a = if(args \ "a" isDefined) {
> Try(args("a").as[String].toInt).getOrElse(0)
> } else 0
> val b = if(args \ "b" isDefined) {
> Try(args("b").as[String].toInt).getOrElse(0)
> } else 0
> if( args \ "add" isDefined) {
> html(Some(s"${a} + ${b} = ${a+b}"))
> } else if ( args \ "mul" isDefined) {
> html(Some(s"${a} * ${b} = ${a*b}"))
> } else html()
> }
>
> def html(msg: Option[String]=None) = {
> val body = s"""
> ${if(msg.isEmpty) "" else ""+msg.get+""}
> 
>   
>   
>   +
>   *
> """
> Json.obj("body" -> body)
> }
> 
>
> Deployed with this command:
>
> wsk action update scala/calc calc.sc -m512 --web true --docker
> msciab/actionloop-scala-v2.12
>
> The runtime is also part of a "collection" of runtimes based on the
> ActionLoop (the engine of the GoLang runtime) and I want to show how to
> build a new runtime for any language with just 3 files: a "compiler"
> script, a launcher and a Dockerfile.
>
> I already did the runtimes for Swift and Scala, and I have in mind many
> others (rust, haskell and kotlin  for example).
>
>
>
> --
>   Michele Sciabarra
>   mich...@sciabarra.com
>
> - Original message -
> From: Carlos Santana 
> To: "dev@openwhisk.apache.org" 
> Subject: Tech Interchange call this Wed. Oct. 24 - add agenda topics here
> Date: Mon, 22 Oct 2018 09:55:48 -0400
>
> Hi Whiskers,
>
> Please add to this thread any agenda items you'd like to present at the
> Tech Interchange call this Wednesday (October 24).
>
> Call details:
>
> Web Meeting: Tech Interchange (bi-weekly):
> - Day-Time: Wednesdays, 11AM EDT (Eastern US), 5PM CEST (Central Europe),
> 3PM UTC, 11PM CST (Beijing)
> - Zoom: https://zoom.us/my/asfopenwhisk
>
> Thanks,
>
> --carlos
>

Change the package name into org.apache.openwhisk for openwhisk modules

[Vincent S Hou]

Hi all,

In order to make OpenWhisk a real member of Apache, we need to make a overhaul 
for the package name existing in all openwhisk projects. This is a must-have to 
relase
1.0.0 or above. This mail is a call-for-action, making every whisker on the 
same page.

As I went through all the 12 modules, which have released under Apache for the 
first time, there are only 2 modules, which need their package names changed: 
OpenWhisk and openwhisk runtime java. Package really means a grouping mechanism 
in terms of compiling and building for Scala and Java.

For example, the package "whisk.***" will be changed into 
"org.apache.openwhisk.***".

All the Go modules do not need to change, since Go projects have their native 
way to define the structure.
Runtime nodejs, docker, swift, php, and python do not need to change, since 
they do not have the syntax for package, only directory.
Catalog does not need to change.
Apigateway does not need to change.

If you do not agree on my discovery, feel free to chime in with comments.

For companies with existing platforms built on top of openwhisk, this change of 
package name will bring in incompatibility to the legacy. There are two ways 
proposed here to cope with: 1. use the openwhisk 0.9.0 official release 
available under apache as the code base; 2. change the package name in the 
platform as well to cater for the package renaming.

For other openwhisk modules, which plan to launch releases under Apache. 
Double-check whether you have package, which needs to change into 
"org.apache.openwhisk***". 
The effort of changing the package will start soon. Be prepared.

Thanks for your attention. 


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: Instruction documented to release openwhisk projects under apache

[Vincent S Hou]

 
Thank you, Bertrand.
The page has been updated.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Bertrand Delacretaz  wrote: -
To: dev@openwhisk.apache.org
From: Bertrand Delacretaz 
Date: 10/09/2018 08:01AM
Subject: Re: Instruction documented to release openwhisk projects under apache

Hi,

(replying to dev@ only, no need for a private conversation here)

On Mon, Oct 1, 2018 at 9:49 PM Vincent S Hou  wrote:
> ...I have documented the instruction to release openwhisk module under Apache 
> as release manager at
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+release+OpenWhisk+under+Apache+as+incubator+project
>  ..

thank you!

I have one comment on the voting, there are no vetoes in Apache
release votes, as per https://www.apache.org/foundation/voting.html
vetoes only apply to code changes.

So I suggest changing the "Go through the voting process" section to say

***
...both parties to pass the vote, as per
https://www.apache.org/foundation/voting.html

* the vote email needs to be open for at least 72 hours;
* at least 3 positive votes are received from the binding members,
which means PPMC members in OpenWhisk community and IPMC members in
Apache;
* there are more positive than negative binding votes;
* once at least 72 hours have passed, the vote is tallied in a
[VOTE][RESULT] message.

***

I don't seem to have karma to make those changes myself on that wiki page.

Of course, negative votes should be taken into account if possible,
even if non-binding.

But that's not a formal requirement - we think it's more important for
the project to be able to move forward if that's what a majority of
voters wants.

-Bertrand

Instruction documented to release openwhisk projects under apache

[Vincent S Hou]

Hi openwhiskers,

I have documented the instruction to release openwhisk module under Apache as 
release manager at
https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+release+OpenWhisk+under+Apache+as+incubator+project

For folks, who are interested in driving the release effort of openwhisk in 
future. This is the guideline you can refer to.
You can give it a skim. Feedback is welcome.

Thanks.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[ANNOUNCE] Apache OpenWhisk nodejs, java, docker, python, php and swift runtimes (incubating) 1.12.0 released

[Vincent S Hou]

Hi everyone,

We are pleased to announce that Apache nodejs, java, docker, python, php and 
swift runtimes (incubating) 1.12.0 are released.

OpenWhisk has 6 default runtime environments for users to develop their 
actions: nodejs, java, docker, python, php and swift.

The download links of the current release is available at:
https://openwhisk.apache.org/downloads.html

Vincent Hou
On behalf of the OpenWhisk team

=
*DISCLAIMER*
Apache OpenWhisk Runtime nodejs (incubating) is an effort undergoing incubation 
at The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Apache OpenWhisk Runtime java (incubating) is an effort undergoing incubation 
at The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

*DISCLAIMER*
Apache OpenWhisk Runtime docker (incubating) is an effort undergoing incubation 
at The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Apache OpenWhisk Runtime python (incubating) is an effort undergoing incubation 
at The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

*DISCLAIMER*
Apache OpenWhisk Runtime php (incubating) is an effort undergoing incubation at 
The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Apache OpenWhisk Runtime swift (incubating) is an effort undergoing incubation 
at The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Re: Any Topics for next community Tech Interchange April-11 @3pm GMT / 11am EST / 8am PST

[Vincent S Hou]

Hi Chetan,

The greatest news can go to that OpenWhisk officially first-time released all 
the 12 modules under Apache as incubator project.
We have walked through the voting processes for all the modules, and we passed 
all the vote mails.

The download links are available here: 
http://openwhisk.incubator.apache.org/downloads.html
Some runtime links may return 404, since the Apache mirror is synchronizing. 
Eventually all the links will be update-to-date.

Next, the following bulletins will play out:
Each repo can plan its own release, but must follow the apache release process 
to plan new releases.
Based on the current design, OpenWhisk core service needs to pin specific 
versions for runtimes, CLI and any other possible modules for further release.
Each of the 12 modules needs to have changelog in future releases, and plan its 
own pace to release.
New runtime or openwhisk project needs to launch the same journey compliant 
with Apache process, if it is planned to release.
One artifact, including all modules, should be provided for download, and all 
modules work together after extracting. We need a to plan one future milestone 
version to catch all the modules. We need to discuss how to do it. My concern 
is whether we should include the runtimes, since the number of runtimes keeps 
on increasing. It is a good idea to package them into the unified artifact.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Chetan Mehrotra  wrote: -
To: dev@openwhisk.apache.org
From: Chetan Mehrotra 
Date: 04/10/2018 05:58AM
Subject: Any Topics for next community Tech Interchange April-11 @3pm GMT / 
11am EST / 8am PST

Please respond to this thread with any topics we should put on the
agenda for this week's (i.e., Wed. April 11th) OW Tech Interchange
call.

Possible topics

- OpenJ9 the Java runtime
- Release status
- ArtifactStore related work

Chetan Mehrotra

OpenWhisk officially first-time released all the 12 modules under Apache as incubator project.

[Vincent S Hou]

Hi OpenWhiskers,

After everybody's great effort, OpenWhisk has now successfully releases all the 
12 designated modules:
OpenWhisk
CLI
Catalog
Wskdeploy
Apigateway
Client Go library
Runtime Nodejs
Runtime Java
Runtime Docker
Runtime Swift
Runtime Python
Runtime PHP

under Apache as incubator project. Thank everyone for the great work.

All the download links are available at the official website of openwhisk: 
http://openwhisk.incubator.apache.org/downloads.html
Some runtime links may return 404, since the Apache mirror is synchronizing. 
Eventually all the links will be update-to-date.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[ANNOUNCE] Apache OpenWhisk Catalog and Apigateway (incubating) 0.9.0 released

[Vincent S Hou]

Hi everyone,

We are pleased to announce that Apache OpenWhisk Catalog and Apigateway 
(incubating) 0.9.0 are released.

Apache OpenWhisk Catalog maintains package catalogs of OpenWhisk, which 
provides an easy way to enhance your application with useful capabilities, and 
to access external services in the ecosystem.
Apache OpenWhisk Apigateway is a performant API Gateway based on Openresty and 
NGINX.

The download links of the current release is available at:
https://openwhisk.apache.org/downloads.html

Vincent Hou
On behalf of the OpenWhisk team

=
*DISCLAIMER*
Apache OpenWhisk Catalog (incubating) is an effort undergoing incubation at The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Apache OpenWhisk Apigateway (incubating) is an effort undergoing incubation at 
The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Re: [RESULT][VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and and swift runtimes[RC1]

[Vincent S Hou]

Yes.

I actually use my vote as a buffer. If there is one vote short, and the mail 
thread is open for a long time. I will count my vote in order to pass.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Carlos Santana  wrote: -
To: dev@openwhisk.apache.org
From: Carlos Santana 
Date: 09/18/2018 12:42PM
Subject: Re: [RESULT][VOTE] Release Apache OpenWhisk 1.12.0-incubating: 
OpenWhisk python, php and and swift runtimes[RC1]

FYI Vicent you can count your self in the votes for +1

What I have seeing is that the release manager usually gives a plus +1, and
is looking for 2 more at least :-)


On Tue, Sep 18, 2018 at 11:48 AM Vincent S Hou  wrote:

> Hi all,
>
> Thanks a lot for taking the time to vote the release 1.12.0 of python, php
> and and swift runtimes.
> The vote is passed with 3 +1s (binding) and 1 +1s (non-binding).
>
> Binding +1:
>
> Carlos Santana
> James Thomas
> Matt Rutkowski
>
> Non-binding +1:
>
> Justin Halsall
>
> There is no -1 vote or 0 vote.
>
> The vote has passed in the dev list of OpenWhisk, based on Apache voting
> policy.
> I am closing the vote mail thread, and will send out another email for
> IPMC to vote.
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> Cloud
>
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182 <(919)%20254-7182>
> Address: 4205 S Miami Blvd
> <https://maps.google.com/?q=4205+S+Miami+Blvd=gmail=g>
> (Cornwallis Drive), Durham, NC 27703, United States
>
> -Vincent S Hou/Raleigh/IBM wrote: -
> To: dev@openwhisk.apache.org
> From: Vincent S Hou/Raleigh/IBM
> Date: 09/11/2018 07:28PM
> Subject: [VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk
> python, php and and swift runtimes[RC1]
>
> Hi everyone,
>
> This is to call for a vote for the release of Apache OpenWhisk
> 1.12.0-incubating: OpenWhisk python, php and and swift runtimes.
>
> List of JIRA ticket(s) resolved for this release can be found at
> https://issues.apache.org/jira/browse/INCUBATOR-221.
>
> To learn more about Apache OpenWhisk, please visit
> https://openwhisk.apache.org/.
>
> This release comprises of source code distribution only. There are three
> modules within this release. The artifact were built from the following Git
> commit IDs:
> * openwhisk-runtime-python: ae1f013, Merge pull request #37 from
> houshengbo/revert-license-copyright
> * openwhisk-runtime-php: 93c1871, Revert the content of copyright to the
> content in the template
> * openwhisk-runtime-swift: 2b9bad5, Revert the content of copyright to the
> content in the template
>
> The source code artifact of openwhisk runtime python can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for the artifact of openwhisk runtime python is:
> openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz:
> CE78C962 05B22F78 0209C597 034684CE 48321E7D 39516DFC 3A93010C BF9CF4D0
> CA2263F6
>  287C9963 60A17082 398A1F61 32745543 0199DEEE 3BFABF6E 5C819230
> which can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.sha512
>
> The signature of the artifact of openwhisk runtime python can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.asc
>
>
> The source code artifact of openwhisk runtime php can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for the artifact of openwhisk runtime php is:
> openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz:
> 417DF65E 881BEC2E 6F58F135 45E1C9EA 4C8CA88A 67A31B82 361D6818 796CC605
> 46484A35
>  411E255C B29F1BAD 9298EB57 F89DD64E E340511C EF4ADBCE 948F87DB
> which can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.sha512
>
> The signature of the artifact of openwhisk runtime php can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/o

[RESULT][VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and and swift runtimes[RC1]

[Vincent S Hou]

Hi all,

Thanks a lot for taking the time to vote the release 1.12.0 of python, php and 
and swift runtimes.
The vote is passed with 3 +1s (binding) and 1 +1s (non-binding).

Binding +1:

Carlos Santana
James Thomas
Matt Rutkowski

Non-binding +1:

Justin Halsall

There is no -1 vote or 0 vote.

The vote has passed in the dev list of OpenWhisk, based on Apache voting policy.
I am closing the vote mail thread, and will send out another email for IPMC to 
vote. 
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 09/11/2018 07:28PM
Subject: [VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, 
php and and swift runtimes[RC1]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
1.12.0-incubating: OpenWhisk python, php and and swift runtimes.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-221.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are three 
modules within this release. The artifact were built from the following Git 
commit IDs:
* openwhisk-runtime-python: ae1f013, Merge pull request #37 from 
houshengbo/revert-license-copyright
* openwhisk-runtime-php: 93c1871, Revert the content of copyright to the 
content in the template 
* openwhisk-runtime-swift: 2b9bad5, Revert the content of copyright to the 
content in the template 

The source code artifact of openwhisk runtime python can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime python is:
openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz: 
CE78C962 05B22F78 0209C597 034684CE 48321E7D 39516DFC 3A93010C BF9CF4D0 CA2263F6
 287C9963 60A17082 398A1F61 32745543 0199DEEE 3BFABF6E 5C819230
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime python can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk runtime php can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime php is:
openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz: 
417DF65E 881BEC2E 6F58F135 45E1C9EA 4C8CA88A 67A31B82 361D6818 796CC605 46484A35
 411E255C B29F1BAD 9298EB57 F89DD64E E340511C EF4ADBCE 948F87DB
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime php can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk runtime swift can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime swift is:
openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz: 
E16164FE 9AD218DF 5ACDA598 BC360A43 B52A9B3F F59B2BF4 429B177B F539804A 8166AFED
 FBA9E0F0 8918EDFC 7A485DA6 545DF3C8 C7924B68 D9DE9C22 99F783AC
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime swift can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please vote on releasing this package as Apache OpenWhisk 1.12.0-incubating: 
OpenWhisk python, php and and swift runtimes.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and 
and swift runtimes
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference

Re: [VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and and swift runtimes[RC1]

[Vincent S Hou]

Hi openwhiskers,

Thank you for your votes. This mail thread is closing now.
I will consolidate the votes and send the result soon.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Matt Rutkowski  wrote: -
To: 
From: Matt Rutkowski 
Date: 09/17/2018 04:05PM
Subject: Re: [VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk 
python, php and and swift runtimes[RC1]

The vote will be open for at least 72 hours.
[X] +1 Release as Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and 
and swift 
[ ] +0 no opinion
[ ] -1 Do not release and the reason

On 2018/09/11 23:28:26, "Vincent S Hou"  wrote: 
> Hi everyone,
> 
> This is to call for a vote for the release of Apache OpenWhisk 
> 1.12.0-incubating: OpenWhisk python, php and and swift runtimes.
> 
> List of JIRA ticket(s) resolved for this release can be found at 
> https://issues.apache.org/jira/browse/INCUBATOR-221.
> 
> To learn more about Apache OpenWhisk, please visit 
> https://openwhisk.apache.org/.
> 
> This release comprises of source code distribution only. There are three 
> modules within this release. The artifact were built from the following Git 
> commit IDs:
> * openwhisk-runtime-python: ae1f013, Merge pull request #37 from 
> houshengbo/revert-license-copyright
> * openwhisk-runtime-php: 93c1871, Revert the content of copyright to the 
> content in the template 
> * openwhisk-runtime-swift: 2b9bad5, Revert the content of copyright to the 
> content in the template 
> 
> The source code artifact of openwhisk runtime python can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk runtime python is:
> openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz: 
> CE78C962 05B22F78 0209C597 034684CE 48321E7D 39516DFC 3A93010C BF9CF4D0 
> CA2263F6
>  287C9963 60A17082 398A1F61 32745543 0199DEEE 3BFABF6E 5C819230
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk runtime python can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.asc
> 
> 
> The source code artifact of openwhisk runtime php can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk runtime php is:
> openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz: 
> 417DF65E 881BEC2E 6F58F135 45E1C9EA 4C8CA88A 67A31B82 361D6818 796CC605 
> 46484A35
>  411E255C B29F1BAD 9298EB57 F89DD64E E340511C EF4ADBCE 948F87DB
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk runtime php can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.asc
> 
> 
> The source code artifact of openwhisk runtime swift can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk runtime swift is:
> openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz: 
> E16164FE 9AD218DF 5ACDA598 BC360A43 B52A9B3F F59B2BF4 429B177B F539804A 
> 8166AFED
>  FBA9E0F0 8918EDFC 7A485DA6 545DF3C8 C7924B68 D9DE9C22 99F783AC
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk runtime swift can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.asc
> 
> 
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
> 
> Please vote on releasing this package as Apache OpenWhisk 1.12.0-incubating: 
> OpenWhisk python, ph

Re: [VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk nodejs, java and and docker runtimes[RC1]

[Vincent S Hou]

Hi openwhiskers,

Thank you for your votes. This mail thread is closing now.
I will consolidate the votes and send the result soon.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Matt Rutkowski  wrote: -
To: 
From: Matt Rutkowski 
Date: 09/17/2018 04:06PM
Subject: Re: [VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk 
nodejs, java and and docker runtimes[RC1]

The vote will be open for at least 72 hours.
[X] +1 Release as Apache OpenWhisk 1.12.0-incubating: OpenWhisk nodejs, java 
and and docker runtimes
[ ] +0 no opinion
[ ] -1 Do not release and the reason

On 2018/09/11 23:26:24, "Vincent S Hou"  wrote: 
> Hi everyone,
> 
> This is to call for a vote for the release of Apache OpenWhisk 
> 1.12.0-incubating: OpenWhisk nodejs, java and and docker runtimes.
> 
> List of JIRA ticket(s) resolved for this release can be found at 
> https://issues.apache.org/jira/browse/INCUBATOR-220.
> 
> To learn more about Apache OpenWhisk, please visit 
> https://openwhisk.apache.org/.
> 
> This release comprises of source code distribution only. There are three 
> modules within this release. The artifact were built from the following Git 
> commit IDs:
> * openwhisk-runtime-nodejs: fcd42de, Revert the content of copyright to the 
> content in the template (#86)
> * openwhisk-runtime-java: 7cd1789, Revert the content of copyright to the 
> content in the template (#70) 
> * openwhisk-runtime-docker: 247baf5, Merge pull request #57 from 
> houshengbo/revert-copyright-license 
> 
> The source code artifact of openwhisk runtime nodejs can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk runtime nodejs is:
> openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz: 
> D046ED19 A813D9A9 96986002 C7065C7A 41FDF48A B87440D9 CF86B227 B4E2D3BF 
> A63DC4C0
>  7BAC979F 998B9867 3492A8A5 07F739ED 822BFC14 2E44EFA9 7D29DF23
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk runtime nodejs can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz.asc
> 
> 
> The source code artifact of openwhisk runtime java can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk runtime java is:
> openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz: 
> FADF0287 E4A65B8C F56F0CAD 128CB02E 89B701EA A621D394 6A8412FD 05522B44 
> 1AD4EC05
>  A52FF4CE 6B73FC6D 44B6730F E4023923 EE92C1C9 02DAC10F 1DB253C3
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk runtime java can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz.asc
> 
> 
> The source code artifact of openwhisk runtime docker can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk runtime docker is:
> openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz: 
> D668D079 CFBF8DBB 7356D50B 609F7A42 49C588BD 9BADC57B A06C025A CA5BFDFF 
> BB3A3E72
>  EF612A43 A4179A04 4EF12FD6 9BAA8047 46197280 6037C5EC BAA3F626
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk runtime docker can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz.asc
> 
> 
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
> 
> Please vote on releasing this package as Apache OpenWhisk 1.12.0-incubat

Re: [VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk nodejs, java and and docker runtimes[RC1]

[Vincent S Hou]

Thank you, David, for pointing out my mistake.
It seemed that my browser was not refreshed. Sorry about that. I will resend 
the vote email.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 09/10/2018 04:53PM
Subject: Re: [VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk 
nodejs, java and and docker runtimes[RC1]

Hi Vincent,

I think there is a cut-and-paste error in your vote email.  The email said

...
> The source code artifact of openwhisk runtime java can be found at:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for the artifact of openwhisk runtime java is:
> openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz:
> 6377552E 8780329A 22E78C7D A7C06E40 01F48D0C 06EDD1EE 848D400F BDE70FB2
19721297
> EA766B01 62A6FD63 667AF4DB DD791F15 09CC5674 8FCADC9D A5F58E7D
> which can be found via:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz.sha512

But the actual (and correct) SHA-512 checksum for
openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz which is at this
URL is:

openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz:
FADF0287 E4A65B8C F56F0CAD 128CB02E 89B701EA A621D394 6A8412FD 05522B44
1AD4EC05
 A52FF4CE 6B73FC6D 44B6730F E4023923 EE92C1C9 02DAC10F 1DB253C3

Do you need to resend the vote email?  Do we vote ignoring the typo since
the contents of the URL are correct?

thanks,

--dave

[VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and and swift runtimes[RC1]

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
1.12.0-incubating: OpenWhisk python, php and and swift runtimes.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-221.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are three 
modules within this release. The artifact were built from the following Git 
commit IDs:
* openwhisk-runtime-python: ae1f013, Merge pull request #37 from 
houshengbo/revert-license-copyright
* openwhisk-runtime-php: 93c1871, Revert the content of copyright to the 
content in the template 
* openwhisk-runtime-swift: 2b9bad5, Revert the content of copyright to the 
content in the template 

The source code artifact of openwhisk runtime python can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime python is:
openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz: 
CE78C962 05B22F78 0209C597 034684CE 48321E7D 39516DFC 3A93010C BF9CF4D0 CA2263F6
 287C9963 60A17082 398A1F61 32745543 0199DEEE 3BFABF6E 5C819230
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime python can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk runtime php can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime php is:
openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz: 
417DF65E 881BEC2E 6F58F135 45E1C9EA 4C8CA88A 67A31B82 361D6818 796CC605 46484A35
 411E255C B29F1BAD 9298EB57 F89DD64E E340511C EF4ADBCE 948F87DB
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime php can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk runtime swift can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime swift is:
openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz: 
E16164FE 9AD218DF 5ACDA598 BC360A43 B52A9B3F F59B2BF4 429B177B F539804A 8166AFED
 FBA9E0F0 8918EDFC 7A485DA6 545DF3C8 C7924B68 D9DE9C22 99F783AC
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime swift can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please vote on releasing this package as Apache OpenWhisk 1.12.0-incubating: 
OpenWhisk python, php and and swift runtimes.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and 
and swift runtimes
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk nodejs, java and and docker runtimes[RC1]

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
1.12.0-incubating: OpenWhisk nodejs, java and and docker runtimes.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-220.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are three 
modules within this release. The artifact were built from the following Git 
commit IDs:
* openwhisk-runtime-nodejs: fcd42de, Revert the content of copyright to the 
content in the template (#86)
* openwhisk-runtime-java: 7cd1789, Revert the content of copyright to the 
content in the template (#70) 
* openwhisk-runtime-docker: 247baf5, Merge pull request #57 from 
houshengbo/revert-copyright-license 

The source code artifact of openwhisk runtime nodejs can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime nodejs is:
openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz: 
D046ED19 A813D9A9 96986002 C7065C7A 41FDF48A B87440D9 CF86B227 B4E2D3BF A63DC4C0
 7BAC979F 998B9867 3492A8A5 07F739ED 822BFC14 2E44EFA9 7D29DF23
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime nodejs can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk runtime java can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime java is:
openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz: 
FADF0287 E4A65B8C F56F0CAD 128CB02E 89B701EA A621D394 6A8412FD 05522B44 1AD4EC05
 A52FF4CE 6B73FC6D 44B6730F E4023923 EE92C1C9 02DAC10F 1DB253C3
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime java can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk runtime docker can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime docker is:
openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz: 
D668D079 CFBF8DBB 7356D50B 609F7A42 49C588BD 9BADC57B A06C025A CA5BFDFF BB3A3E72
 EF612A43 A4179A04 4EF12FD6 9BAA8047 46197280 6037C5EC BAA3F626
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime docker can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please vote on releasing this package as Apache OpenWhisk 1.12.0-incubating: 
OpenWhisk nodejs, java and and docker runtimes.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 1.12.0-incubating: OpenWhisk nodejs, java 
and and docker runtimes
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[VOTE] Release Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and and swift runtimes[RC1]

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
1.12.0-incubating: OpenWhisk python, php and and swift runtimes.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-221.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are three 
modules within this release. The artifact were built from the following Git 
commit IDs:
* openwhisk-runtime-python: ae1f013, Merge pull request #37 from 
houshengbo/revert-license-copyright
* openwhisk-runtime-php: 93c1871, Revert the content of copyright to the 
content in the template 
* openwhisk-runtime-swift: 2b9bad5, Revert the content of copyright to the 
content in the template 

The source code artifact of openwhisk runtime python can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime python is:
openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz: 
CD7D8651 CA50F10D EC1F7A44 FE03B9DB D40D7F87 9393479B 48D0071D 4C7C17BE 156F198A
 0462AA96 BF53D1AC 46051C90 A3B0204B 53FA6F1E 3E83E396 BEEB635D
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime python can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk runtime php can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime php is:
openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz: 
EF7C2E08 23BE3B65 8C31A12C CC6F31DD 1A9FEB73 65342881 AFF4E5A9 B8D180B6 471B3FCF
 2835DD92 2D128112 76C0409F EFA74222 4754F075 391662AB 31EC1DAB
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime php can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk runtime swift can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk runtime swift is:
openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz: 
6FE03B61 EBB1633C B73495AA 646D98E7 7D8BABCC 80932BDA 9EB40545 07ED1569 8D45E4E3
 6E867903 DF1E7ED0 914F0725 E0937F03 548115F2 90E59F30 63854170
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk runtime swift can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please vote on releasing this package as Apache OpenWhisk 1.12.0-incubating: 
OpenWhisk python, php and and swift runtimes.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 1.12.0-incubating: OpenWhisk python, php and 
and swift runtimes
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[RESULT][VOTE] Release Apache OpenWhisk (Incubating): wskdeploy module 0.9.8

[Vincent S Hou]

Hi all,

Thanks a lot for taking the time to vote the release 0.9.8 of OpenWhisk: 
wskdeploy module

The vote is passed with 3 +1s (binding).

Binding +1:

Bertrand Delacretaz
Jim Jagielski
Justin Mclean

There is no -1 vote or 0 vote.

I will proceed with the next steps for the release.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: Bi-weekly Tech Interchange call tomorrow

[Vincent S Hou]

Hi Tyson,

I want to introduce the status of release, the plan to release runtimes, and 
the future version management.
Thank you.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Markus Thömmes"  wrote: -
To: dev@openwhisk.apache.org
From: "Markus Thömmes" 
Date: 08/28/2018 01:14PM
Subject: Re: Bi-weekly Tech Interchange call tomorrow

Hi Tyson,

shall we discuss the mechanics on how to start the prototype for the
future-arch discussion?

Cheers,
Markus

Am Di., 28. Aug. 2018 um 16:59 Uhr schrieb Tyson Norris
:

> Hi Whiskers!
>
> Please send any agenda items you would like to discuss at the Tech
> Interchange call tomorrow.
> Thanks
> Tyson
>
> Call details:
> Web Meeting: Tech Interchange (bi-weekly):
> - Day-Time: Wednesdays, 11AM EDT (Eastern US), 5PM CEST (Central Europe),
> 3PM UTC, 11PM CST (Beijing)
> - Zoom: https://zoom.us/my/asfopenwhisk
>

Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all runtimes for the first-time release under Apache

[Vincent S Hou]

Good. I am totally support getting rid of the old tagging system and embrace 
the way in Apache, and move on the future releases with it.
1.12.0 is the latest version for the old system across runtimes, and the 
earliest start for the new Apache version.
To me, it is a perfect pick.

In future, we should stop releasing multiple tags for different kinds in one 
repository. For example, nodejs 6 and nodejs 8, we should try to keep them
under the same versioning number. As long as code is in the same repo, it 
should stick to the same version. If it is not obeyed, we have to revive the 
old tagging system, we are using now.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/28/2018 03:46PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache

"Vincent S Hou"  wrote on 08/28/2018 03:14:38 PM:
>
> The version number we choose for openwhisk runtimes to be released
> under Apache as an incubator is a separate versioning system from
> what we have already as GitHub tags. The apache version will not
> break anything we have as legacy. The only difference it brings is
> just a new tag.
>
> If we pick up 1.12.0-incubating for all the runtimes, all the source
> code of runtimes are packaged in the artifacts available in
> Apache SVN server. When they are released, a new tag 1.12.0-
> incubating is added to the GitHub, but with some variations. Take
> nodejs for instance, we added two tags
> 6@1.12.0-incubating and 8@1.12.0-incubating to the same commit, so
> that nodejs 8 will push 1.12.0-incubating image to dockerhub and
> nodejs 6 will push 1.12.0-incubating as well. It is possible that
> the new 1.12.0-incubating nodejs 8 image equals to an existing
> image, like 1.9.0 or latest, but that is totally acceptable.
> The same rule applies to any other runtime repository.
>
> The old GitHub tagging system can still work and develop as planned.
> The new Apache versioning system can grow in parallel without any
> interference. Right now, the apache version always ends with -
> incubating because openwhisk is an incubator, so that we can clearly
> distinguish it. In future, when we graduate, we can make sure the
> apache version ends with -apache. All the docker images in dockerhub
> are tagged with -incubating or -apache, without affecting the
> existing GitHub tags we have.
>
> This is why I root for using the same Apache version for all the
> openwhisk runtimes. It does not influence anything we currently have.
>
>

Hi Vincent,

I don't object to starting at 1.12.0 (or whatever the lowest unused
number is across all previous tags).   Version number space is cheap, we
can skip some to align if you really want to do it that way.  I don't think
it is that useful, but I also don't think it is harmful.

However, I do think we need to stop using the old system and only
tag/release using the Apache process going forward. As pointed out in
Bertrand's blog post [1], there are very solid reasons to do it that way.
Assuming we do this, we will very quickly have runtimes having Apache
releases on their own cadence and the version numbers won't align with each
other or with openwhisk core.  I think this is fine, but I think we should
realize now that is going to happen and not assume we will have aligned
version numbers any time in the future (except perhaps for 2.0, 3.0. etc).

--dave

[1] https://blogs.apache.org/foundation/entry/success-at-apache-the-apache1

Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all runtimes for the first-time release under Apache

[Vincent S Hou]

Hi everyone,

The version number we choose for openwhisk runtimes to be released under Apache 
as an incubator is a separate versioning system from what we have already as 
GitHub tags. The apache version will not break anything we have as legacy. The 
only difference it brings is just a new tag.

If we pick up 1.12.0-incubating for all the runtimes, all the source code of 
runtimes are packaged in the artifacts available in
Apache SVN server. When they are released, a new tag 1.12.0-incubating is added 
to the GitHub, but with some variations. Take nodejs for instance, we added two 
tags
6@1.12.0-incubating and 8@1.12.0-incubating to the same commit, so that nodejs 
8 will push 1.12.0-incubating image to dockerhub and nodejs 6 will push 
1.12.0-incubating as well. It is possible that the new 1.12.0-incubating nodejs 
8 image equals to an existing image, like 1.9.0 or latest, but that is totally 
acceptable.
The same rule applies to any other runtime repository.

The old GitHub tagging system can still work and develop as planned. The new 
Apache versioning system can grow in parallel without any interference. Right 
now, the apache version always ends with -incubating because openwhisk is an 
incubator, so that we can clearly distinguish it. In future, when we graduate, 
we can make sure the apache version ends with -apache. All the docker images in 
dockerhub are tagged with -incubating or -apache, without affecting the 
existing GitHub tags we have.

This is why I root for using the same Apache version for all the openwhisk 
runtimes. It does not influence anything we currently have. 

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States




Hi David,

If I pick the commit ID 1fb97e9 for openwhisk-deploy-kube, which is a merge on 
Jun 28. Is it OK for the openwhisk release 0.9.0?


 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/27/2018 02:42PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache

Hi Vincent,

I respect the work that has been done and all that has been learned.  

I agree there is a core set of repositories that need to be released 
together to make a platform. 

But, we make a significant error in the order of release and continuing 
to use the "latest" tag in released branches.  This is not your fault.  We 
collectively missed it.

I am sorry but 0.9.0 openwhisk and 0.9.0 openwhisk-deploy-kube are not 
compatible.   The core openwhisk release is from June 29.  There have been 
multiple configuration changes in the core project since June 29 that have been 
reflected in openwhisk-0.9.0 deploy-kube.  If you built a set of docker images 
from the 0.9.0 openwhisk src release they could not be successfully deployed 
using the 0.9.0 deploy-kube src release because the set of configuration flags 
for the controller/invoker are not compatible.  

One possible solution to salvage 0.9.0 as a coherent set of source 
files is to remove openwhisk-kube-deploy from the 0.9.0 release.  I don't know 
if this will be enough. There have also been changes in the various runtime 
projects since June 29 to match changes made in the core system post 0.9.0.  It 
is possible that these are all forward/backward compatible, but I do not know 
that we have tested them to verify that.   We will need to do a significant 
amount of testing if we want to be able to tell uses that they can actually use 
the 0.9.0 release as a coherent set of source files to build an OpenWhisk 
deployment themselves.

--dave


"Vincent S Hou" ---08/27/2018 02:13:59 PM---Hi Dave, > As it is, the 0.9.0 
release is only useful for practice with the Apache

From:"Vincent S Hou" 
To:dev@openwhisk.apache.org
Date:08/27/2018 02:13 PM
Subject:Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for 
all runtimes for the first-time release under Apache



Hi Dave,

> As it is, the 0.9.0 release is only useful for practice with the Apache
> release process.  The various source artifacts tagged 0.9.0 are not
> actually compatible with each other.

I am upset if you say this. I have been working my bones out during the past 
months to make sure
openwhisk, openwhisk-catalog, openwhisk-cli, openwhisk-client-go, 
openwhisk-wskdeploy, openwhisk-apigateway, openwhisk-deploy-kube
under 0.9.x version matc

Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all runtimes for the first-time release under Apache

[Vincent S Hou]

Hi all,

There are 6 runtime projects to be release for the first time under Apache. I 
am gonna send off 6 vote mails soon for the votes, since each of them has 
individual version number. Please take your time to vote on them.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 08/27/2018 03:35PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache

Hi David,

If I pick the commit ID 1fb97e9 for openwhisk-deploy-kube, which is a merge on 
Jun 28. Is it OK for the openwhisk release 0.9.0?


 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/27/2018 02:42PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache

Hi Vincent,

I respect the work that has been done and all that has been learned.  

I agree there is a core set of repositories that need to be released 
together to make a platform. 

But, we make a significant error in the order of release and continuing 
to use the "latest" tag in released branches.  This is not your fault.  We 
collectively missed it.

I am sorry but 0.9.0 openwhisk and 0.9.0 openwhisk-deploy-kube are not 
compatible.   The core openwhisk release is from June 29.  There have been 
multiple configuration changes in the core project since June 29 that have been 
reflected in openwhisk-0.9.0 deploy-kube.  If you built a set of docker images 
from the 0.9.0 openwhisk src release they could not be successfully deployed 
using the 0.9.0 deploy-kube src release because the set of configuration flags 
for the controller/invoker are not compatible.  

One possible solution to salvage 0.9.0 as a coherent set of source 
files is to remove openwhisk-kube-deploy from the 0.9.0 release.  I don't know 
if this will be enough. There have also been changes in the various runtime 
projects since June 29 to match changes made in the core system post 0.9.0.  It 
is possible that these are all forward/backward compatible, but I do not know 
that we have tested them to verify that.   We will need to do a significant 
amount of testing if we want to be able to tell uses that they can actually use 
the 0.9.0 release as a coherent set of source files to build an OpenWhisk 
deployment themselves.

--dave


"Vincent S Hou" ---08/27/2018 02:13:59 PM---Hi Dave, > As it is, the 0.9.0 
release is only useful for practice with the Apache

From:"Vincent S Hou" 
To:dev@openwhisk.apache.org
Date:08/27/2018 02:13 PM
Subject:Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for 
all runtimes for the first-time release under Apache



Hi Dave,

> As it is, the 0.9.0 release is only useful for practice with the Apache
> release process.  The various source artifacts tagged 0.9.0 are not
> actually compatible with each other.

I am upset if you say this. I have been working my bones out during the past 
months to make sure
openwhisk, openwhisk-catalog, openwhisk-cli, openwhisk-client-go, 
openwhisk-wskdeploy, openwhisk-apigateway, openwhisk-deploy-kube
under 0.9.x version matching, and they work together. As long as the runtimes 
work ok with them, they are good to release even in one tar.gz to work as the 
openwhisk platform.

0.9.0 is not just an Apache practice. I know it is not perfect and has tons of 
things to improve it, but I have already tried my best. At the beginning, I 
hope all the modules including runtimes can have 0.9.0, so that all of them can 
release in one tar.gz, which is the basic standard I set for openwhisk to 
release for the first time under Apache. We are RELEASING really "intellectual 
asset" under Apache, that people can use. Not for practice with the Apache 
release process.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/27/2018 01:46PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for

Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all runtimes for the first-time release under Apache

[Vincent S Hou]

Hi David,

If I pick the commit ID 1fb97e9 for openwhisk-deploy-kube, which is a merge on 
Jun 28. Is it OK for the openwhisk release 0.9.0?


 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/27/2018 02:42PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache

Hi Vincent,

I respect the work that has been done and all that has been learned.  

I agree there is a core set of repositories that need to be released 
together to make a platform. 

But, we make a significant error in the order of release and continuing 
to use the "latest" tag in released branches.  This is not your fault.  We 
collectively missed it.

I am sorry but 0.9.0 openwhisk and 0.9.0 openwhisk-deploy-kube are not 
compatible.   The core openwhisk release is from June 29.  There have been 
multiple configuration changes in the core project since June 29 that have been 
reflected in openwhisk-0.9.0 deploy-kube.  If you built a set of docker images 
from the 0.9.0 openwhisk src release they could not be successfully deployed 
using the 0.9.0 deploy-kube src release because the set of configuration flags 
for the controller/invoker are not compatible.  

One possible solution to salvage 0.9.0 as a coherent set of source 
files is to remove openwhisk-kube-deploy from the 0.9.0 release.  I don't know 
if this will be enough. There have also been changes in the various runtime 
projects since June 29 to match changes made in the core system post 0.9.0.  It 
is possible that these are all forward/backward compatible, but I do not know 
that we have tested them to verify that.   We will need to do a significant 
amount of testing if we want to be able to tell uses that they can actually use 
the 0.9.0 release as a coherent set of source files to build an OpenWhisk 
deployment themselves.

--dave


"Vincent S Hou" ---08/27/2018 02:13:59 PM---Hi Dave, > As it is, the 0.9.0 
release is only useful for practice with the Apache

From:"Vincent S Hou" 
To:dev@openwhisk.apache.org
Date:08/27/2018 02:13 PM
Subject:Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for 
all runtimes for the first-time release under Apache



Hi Dave,

> As it is, the 0.9.0 release is only useful for practice with the Apache
> release process.  The various source artifacts tagged 0.9.0 are not
> actually compatible with each other.

I am upset if you say this. I have been working my bones out during the past 
months to make sure
openwhisk, openwhisk-catalog, openwhisk-cli, openwhisk-client-go, 
openwhisk-wskdeploy, openwhisk-apigateway, openwhisk-deploy-kube
under 0.9.x version matching, and they work together. As long as the runtimes 
work ok with them, they are good to release even in one tar.gz to work as the 
openwhisk platform.

0.9.0 is not just an Apache practice. I know it is not perfect and has tons of 
things to improve it, but I have already tried my best. At the beginning, I 
hope all the modules including runtimes can have 0.9.0, so that all of them can 
release in one tar.gz, which is the basic standard I set for openwhisk to 
release for the first time under Apache. We are RELEASING really "intellectual 
asset" under Apache, that people can use. Not for practice with the Apache 
release process.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/27/2018 01:46PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache



Justin Halsall  wrote on 08/27/2018 01:16:41 PM:
>
> I recently bumped into docker-compose always pulling in the latest
> version of our containers but then failing because we had changed
> some of the dependent variables in the docker image but forgot to do
> so in our Docker Compose configuration files. With the centralized
> runtime manifest we could easily lock our deployments (including
> docker compose) to a release version with limited hassle.
>

Also been thinking about this.  We do have a central manifest already
(runtime.json + ansible group_vars/all in the core project). The mistake we
made is that we left all these tags at "latest" in the 0.9.0 r

Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all runtimes for the first-time release under Apache

[Vincent S Hou]

Hi Dave,

> As it is, the 0.9.0 release is only useful for practice with the Apache
> release process.  The various source artifacts tagged 0.9.0 are not
> actually compatible with each other.

I am upset if you say this. I have been working my bones out during the past 
months to make sure
openwhisk, openwhisk-catalog, openwhisk-cli, openwhisk-client-go, 
openwhisk-wskdeploy, openwhisk-apigateway, openwhisk-deploy-kube
under 0.9.x version matching, and they work together. As long as the runtimes 
work ok with them, they are good to release even in one tar.gz to work as the 
openwhisk platform.

0.9.0 is not just an Apache practice. I know it is not perfect and has tons of 
things to improve it, but I have already tried my best. At the beginning, I 
hope all the modules including runtimes can have 0.9.0, so that all of them can 
release in one tar.gz, which is the basic standard I set for openwhisk to 
release for the first time under Apache. We are RELEASING really "intellectual 
asset" under Apache, that people can use. Not for practice with the Apache 
release process.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/27/2018 01:46PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache



Justin Halsall  wrote on 08/27/2018 01:16:41 PM:
>
> I recently bumped into docker-compose always pulling in the latest
> version of our containers but then failing because we had changed
> some of the dependent variables in the docker image but forgot to do
> so in our Docker Compose configuration files. With the centralized
> runtime manifest we could easily lock our deployments (including
> docker compose) to a release version with limited hassle.
>

Also been thinking about this.  We do have a central manifest already
(runtime.json + ansible group_vars/all in the core project). The mistake we
made is that we left all these tags at "latest" in the 0.9.0 release
(arguably because there had not been a release of the sub-projects yet, so
there was nothing else to use as a tag value).

In future releases, we need to first officially release any of the "leaf"
projects that aren't current, then branch the core repo into a release
branch, then commit a version of runtime.json (and other ansible files) on
this branch that pulls from a fixed tag (not latest) for all the other
projects.   Same thing for the kube-deploy, docker-compose, etc. -- branch,
commit fixed tags for images, then release.

As it is, the 0.9.0 release is only useful for practice with the Apache
release process.  The various source artifacts tagged 0.9.0 are not
actually compatible with each other.

--dave

Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all runtimes for the first-time release under Apache

[Vincent S Hou]

As far as I know, OpenWhisk has a big issue with the versioning we cannot 
disregard.

OpenWhisk runs as a whole platform, which consists of multiple 
projects/modules. The optimal pattern is that all the modules release at a time 
with the same version number, so that we can match them, and we know under this 
certain version number, all the modules will work together. 

Right now, we have the following modules under 0.9.0 or at least 0.9.X
openwhisk
openwhisk-catalog,
openwhisk-client-go
openwhisk-cli,
openwhisk-wskdeploy,
openwhisk-deploy-kube,
openwhisk-apigateway

I plan bundle all of them together in one tar.gz, so that they can be 
downloaded in one compressed file for convenience. I suggest and insist that at 
least 7 of these modules can keep up the same version and able to be released 
synchronously in future, because OpenWhisk is so far a platform, depending on 
multiple modules to release. If we mismatch the version numbers in future, how 
could we know whether 1.2.0 CLI is able to run on top of 1.1.0 openwhisk??

The same issue will happen to runtimes as well. How do we know if 1.13.0 nodejs 
can match the 1.1.0 openwhisk? Of course, each repository should run on its 
owns, and release on its own cycle. However, openwhisk is not that 
"INTELLIGENT" yet to do so. If we propose one version for the 6 runtimes, like 
1.12.0(I wish too much it could still be 0.9.0, but as a respect for the 
reality, I accept it can be some other version). After they are released, we 
can add a document somewhere, saying that 0.9.0 openwhisk modules match 1.12.0 
runtimes, and we can make sure that all the 1.12.0 runtimes able to run in 
0.9.0 openwhisk with no problem.

If we release runtimes individually, we should create a matrix describing like 
1.12.0 nodejs, docker skeleton v1.3.3, python v1.0.3, node8 v1.12.0, php7.2 
v1.0.2,
swift4.1 v1.0.8, java8 v1.1.2 can really work on 0.9.0 openwhisk. As each 
runtime module develops, we have to keep on updating this matrix. Is this 
something we love to have? Or is there a better way to do it?  Based on the 
reality, why don't we get the first release of all the modules of openwhisk out 
for the first time using the easiest way? We can come up to the solution later 
and keep this discussion open. Otherwise, we have to resolve this issue ASAP 
before we release anything.



Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/27/2018 01:34PM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache


"Vincent S Hou"  wrote on 08/27/2018 12:39:01 PM:
>
> For convenience of release management in Apache.
> * We can send one or two vote email(s) instead of 6.

I realize that it will make the initial release more convenient.  I don't
think this is a compelling reason however.

> * The download page of openwhisk.org can allocate one section to
> offer the download links of runtimes.


I don't think this is a good pattern.  I predict we will be releasing
runtimes in individual cadences, driven by changes in the upstream base
language runtime, CVEs that need to be fixed via a new runtime release,
etc.  So I think the download for the runtime needs to be organized by
runtime, then by version within each runtime, not by openwhisk version.

--dave

>
>
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud
>
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States
>
> -Rodric Rabbah  wrote: -
> To: dev@openwhisk.apache.org
> From: Rodric Rabbah 
> Date: 08/27/2018 11:45AM
> Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version
> for all runtimes for the first-time release under Apache
>
> Why do they all need to start from the same version?
>
> On Mon, Aug 27, 2018 at 11:40 AM, Vincent S Hou  wrote:
>
> > Hi OpenWhiskers,
> >
> > We are on our way to release OpenWhisk runtimes under Apache for the
first
> > time. As you may notice or not, each individual runtime repository has
> > already used
> > its own version numbers as the build tag for quite a while. In order
not
> > to disrupt the current versioning number and also accommodating the
release
> > work under Apache, I would like to propose 1.12.0 as the version number
for
> > the first time we release the six runtimes under Apache, because this
> > version number is the 

Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all runtimes for the first-time release under Apache

[Vincent S Hou]

For convenience of release management in Apache.
* We can send one or two vote email(s) instead of 6.
* The download page of openwhisk.org can allocate one section to offer the 
download links of runtimes.


 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Rodric Rabbah  wrote: -
To: dev@openwhisk.apache.org
From: Rodric Rabbah 
Date: 08/27/2018 11:45AM
Subject: Re: [DISCUSSION]: Proposing to use 1.12.0 as the version for all 
runtimes for the first-time release under Apache

Why do they all need to start from the same version?

On Mon, Aug 27, 2018 at 11:40 AM, Vincent S Hou  wrote:

> Hi OpenWhiskers,
>
> We are on our way to release OpenWhisk runtimes under Apache for the first
> time. As you may notice or not, each individual runtime repository has
> already used
> its own version numbers as the build tag for quite a while. In order not
> to disrupt the current versioning number and also accommodating the release
> work under Apache, I would like to propose 1.12.0 as the version number for
> the first time we release the six runtimes under Apache, because this
> version number is the minimum
> nominator I find for all the runtimes so far.
>
> We now have following runtimes, which have already released with their
> version numbers:
> docker skeleton v1.3.3
> python2 v1.0.3
> python3 v.1.0.3
> node8 v1.12.0
> node6 v1.12.0
> php7.2 v1.0.2
> swift4.1 v1.0.8
> java8 v1.1.2
>
> I think 1.12.0 can match them all, and then use it as a common ground to
> move on with further version numbers. I would like to hear your comments.
> If no objection is heard, I will move on with 1.12.0 for the runtimes to
> be released under Apache for the first time.
>
> Best wishes,
> Vincent Hou
>
>
>

[DISCUSSION]: Proposing to use 1.12.0 as the version for all runtimes for the first-time release under Apache

[Vincent S Hou]

Hi OpenWhiskers,

We are on our way to release OpenWhisk runtimes under Apache for the first 
time. As you may notice or not, each individual runtime repository has already 
used
its own version numbers as the build tag for quite a while. In order not to 
disrupt the current versioning number and also accommodating the release work 
under Apache, I would like to propose 1.12.0 as the version number for the 
first time we release the six runtimes under Apache, because this version 
number is the minimum
nominator I find for all the runtimes so far.

We now have following runtimes, which have already released with their version 
numbers:
docker skeleton v1.3.3
python2 v1.0.3
python3 v.1.0.3
node8 v1.12.0
node6 v1.12.0
php7.2 v1.0.2
swift4.1 v1.0.8
java8 v1.1.2

I think 1.12.0 can match them all, and then use it as a common ground to move 
on with further version numbers. I would like to hear your comments.
If no objection is heard, I will move on with 1.12.0 for the runtimes to be 
released under Apache for the first time. 

Best wishes,
Vincent Hou

[RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk catalog and apigateway

[Vincent S Hou]

Hi all,

Thanks a lot for taking the time to vote the release 0.9.0 of OpenWhisk catalog 
and apigateway.
The vote is passed with 3 +1s (binding) and 2 +1s (non-binding).

Binding +1:

Bertrand Delacretaz 
David Grove
Vincent Hou

Non-binding +1:

Justin Halsall
Matt Hamann


There is no -1 vote or 0 vote.

The vote has passed in the dev list of OpenWhisk, based on Apache voting 
policy. 
I am closing the vote mail thread, and will send out another email for IPMC to 
vote.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Forwarded by Vincent S Hou/Raleigh/IBM on 08/05/2018 10:11PM -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 07/31/2018 06:36PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client 
go and CLI

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk client go and CLI.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-215.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are two modules 
within this release. The artifact were built from the following Git commit IDs:
* openwhisk-client-go: 90976ef, Update the doc of client go to make it clear 
for 0.9.0
* openwhisk-cli: 4a5a372, Bump gradle and scoverage version

The source code artifact of openwhisk client go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk cli can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: client go and CLI
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk catalog and apigateway

[Vincent S Hou]

Hi everyone,

I am closing this vote email thread and count the votes for OpenWhisk catalog 
and apigateway for 0.9.0.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 08/23/2018 06:00PM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk 
catalog and apigateway

I have verified the checklist for both of the modules, and they are all fine.
I go with the vote +1 to release catalog and apigateway.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 08/21/2018 02:49PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk 
catalog and apigateway

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk catalog and apigateway.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-218.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are two  modules 
within this release. The artifact were built from the following Git commit IDs:
* openwhisk-catalog: 5c4f2a8,  Revert the copyright to the content in the 
template  
* openwhisk-apigateway: eb22ac6, Revert the copyright to the content in the 
template

The source code artifact of openwhisk catalog can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk catalog is:
openwhisk-catalog-0.9.0-incubating-sources.tar.gz: 
3BA28A6A 88B7700D 92929843 E742D6ED 65F3D48A DD537965 C0BA9822 E2414DCD 010EFE8B
 4774D652 1CA6E3F7 6DFF6BEE 76FA982D 5070290B 20CBA110 7750F7ED
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk catalog can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk apigateway can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk apigateway is:
openwhisk-apigateway-0.9.0-incubating-sources.tar.gz: 
F62A50B7 970540B8 CA3C1796 13A75743 537B4374 3F0B9EA5 F4A35396 98A57D8E EAA0EFA5
 AB8AF26D 46E2E6A4 7794AE50 03887F11 6D7D9825 2EA08733 77B369DA
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk apigateway can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating: 
OpenWhisk catalog and apigateway.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: OpenWhisk catalog and 
apigateway
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk wskdeploy

[Vincent S Hou]

Hi everyone,

I am closing this vote email thread and count the votes for OpenWhisk wskdeploy 
module for 0.9.8.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 08/23/2018 06:00PM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk 
wskdeploy

I have verified all the bulletins in the checklist.
I vote +1 to release wskdeploy module.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 08/20/2018 11:03PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk 
wskdeploy

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.8-incubating: OpenWhisk wskdeploy.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-217.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are only one 
module within this release number 0.9.8. The artifact were built from the 
following Git commit IDs:
* openwhisk-wskdeploy: cd3c3c4

The source code artifact of openwhisk wskdeploy can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk wskdeploy is
openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz: 
B1979B93 573BB04B B495FA1A 8D0C1D93 ACD6371D 96BED392 A47D972C 6232AE41 0E1FA1DF
 DB79D4AA B2D10F87 1942ED94 BF83A200 6D82EABB 2BCE951C 31B5A8D3
which can can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk wskdeploy can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS


Please vote on releasing this package as Apache OpenWhisk 0.9.8-incubating: 
OpenWhisk wskdeploy.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[RESULT][VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk wskdeploy

[Vincent S Hou]

Hi all,

Thanks a lot for taking the time to vote the release 0.9.8 of OpenWhisk 
wskdeploy.
The vote is passed with 5 +1s (binding) and 2 +1s (non-binding).

Binding +1:

Bertrand Delacretaz
Chetan Mehrotra 
David Grove
Matt Rutkowski
Vincent Hou

Non-binding +1:

Justin Halsall
Priti Desai


There is no -1 vote or 0 vote.

The vote has passed in the dev list of OpenWhisk, based on Apache voting 
policy. 
I am closing the vote mail thread, and will send out another email for IPMC to 
vote.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Forwarded by Vincent S Hou/Raleigh/IBM on 08/05/2018 10:11PM -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 07/31/2018 06:36PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client 
go and CLI

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk client go and CLI.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-215.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are two modules 
within this release. The artifact were built from the following Git commit IDs:
* openwhisk-client-go: 90976ef, Update the doc of client go to make it clear 
for 0.9.0
* openwhisk-cli: 4a5a372, Bump gradle and scoverage version

The source code artifact of openwhisk client go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk cli can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: client go and CLI
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk Deploy Kube

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk Deploy Kube.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-219.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are only one 
module within this release number 0.9.0. The artifact were built from the 
following Git commit IDs:
* openwhisk-deploy-kube: 5344a67, Release openwhisk deploy kube for the version 
0.9.0 (#233) 

The source code artifact of openwhisk deploy kube can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-deploy-kube-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk deploy kube is
openwhisk-deploy-kube-0.9.0-incubating-sources.tar.gz: 
569578F0 E7E29B34 3718EC7D 4EEEA473 DC9A642F F4861730 57957B07 29A6F43B C8834AE2
 B33DC791 78AA75BF DE50784E 170424A2 628A49E7 72CB9DF7 1F2D7D2E
which can can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-deploy-kube-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk deploy kube can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-deploy-kube-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS


Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating: 
OpenWhisk Deploy Kube.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: openwhisk deploy kube
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk wskdeploy

[Vincent S Hou]

I have verified all the bulletins in the checklist.
I vote +1 to release wskdeploy module.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 08/20/2018 11:03PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk 
wskdeploy

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.8-incubating: OpenWhisk wskdeploy.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-217.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are only one 
module within this release number 0.9.8. The artifact were built from the 
following Git commit IDs:
* openwhisk-wskdeploy: cd3c3c4

The source code artifact of openwhisk wskdeploy can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk wskdeploy is
openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz: 
B1979B93 573BB04B B495FA1A 8D0C1D93 ACD6371D 96BED392 A47D972C 6232AE41 0E1FA1DF
 DB79D4AA B2D10F87 1942ED94 BF83A200 6D82EABB 2BCE951C 31B5A8D3
which can can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk wskdeploy can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS


Please vote on releasing this package as Apache OpenWhisk 0.9.8-incubating: 
OpenWhisk wskdeploy.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk catalog and apigateway

[Vincent S Hou]

I have verified the checklist for both of the modules, and they are all fine.
I go with the vote +1 to release catalog and apigateway.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 08/21/2018 02:49PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk 
catalog and apigateway

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk catalog and apigateway.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-218.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are two  modules 
within this release. The artifact were built from the following Git commit IDs:
* openwhisk-catalog: 5c4f2a8,  Revert the copyright to the content in the 
template  
* openwhisk-apigateway: eb22ac6, Revert the copyright to the content in the 
template

The source code artifact of openwhisk catalog can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk catalog is:
openwhisk-catalog-0.9.0-incubating-sources.tar.gz: 
3BA28A6A 88B7700D 92929843 E742D6ED 65F3D48A DD537965 C0BA9822 E2414DCD 010EFE8B
 4774D652 1CA6E3F7 6DFF6BEE 76FA982D 5070290B 20CBA110 7750F7ED
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk catalog can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk apigateway can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk apigateway is:
openwhisk-apigateway-0.9.0-incubating-sources.tar.gz: 
F62A50B7 970540B8 CA3C1796 13A75743 537B4374 3F0B9EA5 F4A35396 98A57D8E EAA0EFA5
 AB8AF26D 46E2E6A4 7794AE50 03887F11 6D7D9825 2EA08733 77B369DA
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk apigateway can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating: 
OpenWhisk catalog and apigateway.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: OpenWhisk catalog and 
apigateway
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk wskdeploy

[Vincent S Hou]

Hi Chetan,

The gpg: WARNING message is normal. The signature is fine based on the result.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Chetan Mehrotra  wrote: -
To: dev@openwhisk.apache.org
From: Chetan Mehrotra 
Date: 08/23/2018 10:57AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk 
wskdeploy

+1 for release.

Minor issue around signature validation

$ gpg --verify openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.asc
openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz
gpg: Signature made Tue Aug 21 02:45:00 2018 IST
gpg:using RSA key 72AF0CC22C4CF320
gpg: Good signature from "Vincent Hou (Release manager of OpenWhisk) <
houshen...@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: FFB5 D1D5 0881 271B 849D  AE38 72AF 0CC2 2C4C F320
--
sha512 was matching

$ gpg --print-md SHA512 openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz
openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz:
B1979B93 573BB04B B495FA1A 8D0C1D93 ACD6371D 96BED392 A47D972C 6232AE41
0E1FA1DF
 DB79D4AA B2D10F87 1942ED94 BF83A200 6D82EABB 2BCE951C 31B5A8D

Chetan Mehrotra


On Thu, Aug 23, 2018 at 7:23 PM Matt Rutkowski 
wrote:

>
> Please vote on releasing this package as Apache OpenWhisk
> 0.9.8-incubating: OpenWhisk wskdeploy.
>
> The vote will be open for at least 72 hours.
> [X] +1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
> [ ] +0 no opinion
> [ ] -1 Do not release and the reason
>
> On 2018/08/21 03:03:45, "Vincent S Hou"  wrote:
> > Hi everyone,
> >
> > This is to call for a vote for the release of Apache OpenWhisk
> 0.9.8-incubating: OpenWhisk wskdeploy.
> >
> > List of JIRA ticket(s) resolved for this release can be found at
> https://issues.apache.org/jira/browse/INCUBATOR-217.
> >
> > To learn more about Apache OpenWhisk, please visit
> https://openwhisk.apache.org/.
> >
> > This release comprises of source code distribution only. There are only
> one module within this release number 0.9.8. The artifact were built from
> the following Git commit IDs:
> > * openwhisk-wskdeploy: cd3c3c4
> >
> > The source code artifact of openwhisk wskdeploy can be found at:
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz
> >
> > The SHA-512 checksum for the artifact of openwhisk wskdeploy is
> > openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz:
> > B1979B93 573BB04B B495FA1A 8D0C1D93 ACD6371D 96BED392 A47D972C 6232AE41
> 0E1FA1DF
> >  DB79D4AA B2D10F87 1942ED94 BF83A200 6D82EABB 2BCE951C 31B5A8D3
> > which can can be found via:
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.sha512
> >
> > The signature of the artifact of openwhisk wskdeploy can be found via:
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.asc
> >
> >
> > KEYS file is available here:
> > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
> >
> >
> > Please vote on releasing this package as Apache OpenWhisk
> 0.9.8-incubating: OpenWhisk wskdeploy.
> >
> > The vote will be open for at least 72 hours.
> > [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
> > [ ] +0 no opinion
> > [ ] -1 Do not release and the reason
> >
> > Checklist for reference:
> > [ ] Download links are valid.
> > [ ] Checksums and PGP signatures are valid.
> > [ ] DISCLAIMER is included.
> > [ ] Source code artifacts have correct names matching the current
> release.
> > [ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
> > [ ] All files have license headers if necessary.
> > [ ] No compiled archives bundled in source archive.
> >
> > Thank you very much.
> >
> > Best wishes.
> > Vincent Hou (侯胜博)
> >
> > Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> Cloud
> >
> > Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> > Phone: +1(919)254-7182
> > Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
> States
> >
> >
>

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk catalog and apigateway

[Vincent S Hou]

Hi Justin,

Please be advised that this line of code: 
https://github.com/apache/incubator-openwhisk-catalog/blob/master/tools/travis/build.sh#L66
VCAP_SERVICES_FILE="$(readlink -f $ROOTDIR/tests/credentials.json)"

The credentials are saved in credentials.json, which is generated by the Travis 
from credentials.json.enc. This is the encrypted file of the credentials.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Justin Halsall  wrote: -
To: dev@openwhisk.apache.org
From: Justin Halsall 
Date: 08/23/2018 04:00PM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk 
catalog and apigateway

I vote +1 Release as Apache OpenWhisk 0.9.0-incubating: apigateway
+1 Release as Apache OpenWhisk 0.9.0-incubating: catalog

- Justin

> On Aug 23, 2018, at 3:51 PM, David P Grove  wrote:
> 
> I vote: 
> +1 Release as Apache OpenWhisk 0.9.0-incubating: apigateway
> +1 Release as Apache OpenWhisk 0.9.0-incubating: catalog
> 
> Checklist for reference:
> [X ] Download links are valid.
> [X ] Checksums and PGP signatures are valid.
> [X ] DISCLAIMER is included.
> [X ] Source code artifacts have correct names matching the current release.
> [X ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
> [X ] All files have license headers if necessary.
> [X ] No compiled archives bundled in source archive.
> 
> 
> Minor point, it is not a compiled archive, but I am wondering about the 
> binary file credentials.json.enc in the catalog src tar file. Should this 
> file be in the release? What is its purpose?
> 
> --dave
> 
> "Vincent S Hou" ---08/21/2018 02:49:35 PM---Hi everyone, This is to call for 
> a vote for the release of Apache OpenWhisk 0.9.0-incubating: OpenWh
> 
> From: "Vincent S Hou" 
> To: dev@openwhisk.apache.org
> Date: 08/21/2018 02:49 PM
> Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk 
> catalog and apigateway
> 
> 
> 
> 
> Hi everyone,
> 
> This is to call for a vote for the release of Apache OpenWhisk 
> 0.9.0-incubating: OpenWhisk catalog and apigateway.
> 
> List of JIRA ticket(s) resolved for this release can be found at 
> https://issues.apache.org/jira/browse/INCUBATOR-218 
> <https://issues.apache.org/jira/browse/INCUBATOR-218>.
> 
> To learn more about Apache OpenWhisk, please visit 
> https://openwhisk.apache.org/ <https://openwhisk.apache.org/>.
> 
> This release comprises of source code distribution only. There are two  
> modules within this release. The artifact were built from the following Git 
> commit IDs:
> * openwhisk-catalog: 5c4f2a8,  Revert the copyright to the content in the 
> template  
> * openwhisk-apigateway: eb22ac6, Revert the copyright to the content in the 
> template
> 
> The source code artifact of openwhisk catalog can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz
>  
> <https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz>
> 
> The SHA-512 checksum for the artifact of openwhisk catalog is:
> openwhisk-catalog-0.9.0-incubating-sources.tar.gz: 
> 3BA28A6A 88B7700D 92929843 E742D6ED 65F3D48A DD537965 C0BA9822 E2414DCD 
> 010EFE8B
> 4774D652 1CA6E3F7 6DFF6BEE 76FA982D 5070290B 20CBA110 7750F7ED
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512
>  
> <https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512>
> 
> The signature of the artifact of openwhisk catalog can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc
>  
> <https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc>
> 
> 
> The source code artifact of openwhisk apigateway can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz
>  
> <https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-source

[VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk catalog and apigateway

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk catalog and apigateway.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-218.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are two  modules 
within this release. The artifact were built from the following Git commit IDs:
* openwhisk-catalog: 5c4f2a8,  Revert the copyright to the content in the 
template  
* openwhisk-apigateway: eb22ac6, Revert the copyright to the content in the 
template

The source code artifact of openwhisk catalog can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk catalog is:
openwhisk-catalog-0.9.0-incubating-sources.tar.gz: 
3BA28A6A 88B7700D 92929843 E742D6ED 65F3D48A DD537965 C0BA9822 E2414DCD 010EFE8B
 4774D652 1CA6E3F7 6DFF6BEE 76FA982D 5070290B 20CBA110 7750F7ED
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk catalog can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk apigateway can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk apigateway is:
openwhisk-apigateway-0.9.0-incubating-sources.tar.gz: 
F62A50B7 970540B8 CA3C1796 13A75743 537B4374 3F0B9EA5 F4A35396 98A57D8E EAA0EFA5
 AB8AF26D 46E2E6A4 7794AE50 03887F11 6D7D9825 2EA08733 77B369DA
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk apigateway can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating: 
OpenWhisk catalog and apigateway.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: OpenWhisk catalog and 
apigateway
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[ANNOUNCE] Apache OpenWhisk, Client Go and CLI (incubating) 0.9.0 released

[Vincent S Hou]

Hi everyone,

We are pleased to announce that Apache OpenWhisk, Client Go and CLI 
(incubating) 0.9.0 are released.

OpenWhisk Client Go is a client library used to access OpenWhisk service 
written in Go. OpenWhisk CLI is command-line interface used to access OpenWhisk 
service. OpenWhisk is cloud-first distributed event-based programming service. 
It  provides a programming model to upload event handlers to a cloud service, 
and register the handlers to respond to various events. This is the first time 
that OpenWhisk is released under Apache as an incubator project.

The download links of the current release is available at:
https://openwhisk.apache.org/downloads.html

Vincent Hou
On behalf of the OpenWhisk team

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1: OpenWhisk wskdeploy

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.8-incubating: OpenWhisk wskdeploy.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-217.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are only one 
module within this release number 0.9.8. The artifact were built from the 
following Git commit IDs:
* openwhisk-wskdeploy: cd3c3c4

The source code artifact of openwhisk wskdeploy can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk wskdeploy is
openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz: 
B1979B93 573BB04B B495FA1A 8D0C1D93 ACD6371D 96BED392 A47D972C 6232AE41 0E1FA1DF
 DB79D4AA B2D10F87 1942ED94 BF83A200 6D82EABB 2BCE951C 31B5A8D3
which can can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk wskdeploy can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS


Please vote on releasing this package as Apache OpenWhisk 0.9.8-incubating: 
OpenWhisk wskdeploy.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[RESULT][VOTE] Release Apache OpenWhisk (Incubating): Client Go and CLI 0.9.0 [RC1]

[Vincent S Hou]

Hi all,

Thanks a lot for taking the time to vote the release 0.9.0 of OpenWhisk: Client 
Go and CLI modules

The vote is passed with 3 +1s (binding).

Binding +1:

Bertrand Delacretaz
Jim Jagielski
Justin Mclean

There is no -1 vote or 0 vote.

I will proceed with the next steps for the release.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[VOTE]: Release Apache OpenWhisk (Incubating): Client Go and CLI 0.9.0 [RC1]

[Vincent S Hou]

Dear IPMC members,

This is a call for vote to release Apache OpenWhisk (Incubating): Client Go and 
CLI, Version 0.9.0.

The Apache OpenWhisk community has voted on and approved a proposal to release 
Apache OpenWhisk (Incubating): Client Go and CLI, Version 0.9.0.

We now kindly request the Incubator PMC members to review and vote on this 
incubator release.

Apache OpenWhisk Client Go is a Go client library to access Openwhisk API.
Apache OpenWhisk CLI is a command-line interface, based on Go client library, 
to access Openwhisk API.

OpenWhisk Client Go and CLI vote thread:
https://lists.apache.org/thread.html/da01355c62ec6aedf8cd049ad7449ebdc796528e9015fdb1220a19ad@%3Cdev.openwhisk.apache.org%3E

OpenWhisk Client Go and CLI vote result thread:
https://lists.apache.org/thread.html/55f6a6e9218a21ad02c6a13624c368d78d40b68d22e1095543ffdd3c@%3Cdev.openwhisk.apache.org%3E

This release comprises of source code distribution only.


For Client Go:
The source code artifact of OpenWhisk Client Go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for OpenWhisk Client Go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512

The signature for OpenWhisk Client Go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc


For CLI:
The source code artifact of OpenWhisk CLI can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for OpenWhisk CLI can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512

The signature for OpenWhisk CLI can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
This key has been validated here: 
http://pgp.mit.edu/pks/lookup?search=houshengbo=index

This is the first time that Apache OpenWhisk: Client Go and CLI request for a 
release, so there is no file of CHANGELOG.

The documentation can be found at:
https://github.com/apache/incubator-openwhisk-release/blob/master/releases/0.9.0-incubating/INSTALL.md
 or
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md

We are currently using the tool called 
openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
release all the modules of OpenWhisk. The instruction for release managers can 
be found at: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
 This tool
supports both manual and automated modes to package the source code, sign the 
artifacts and upload the artifacts into Apache SVN repositories.

The vote will be open for at least 72 hours or until necessary number of votes 
are reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [DISCUSSION]: Release plan of OpenWhisk 0.9.0 for all modules

[Vincent S Hou]

Hi Dave,

Runtimes can release standlone, so I need the version numbers for all the 
runtimes, which are acceptable at this moment to release in Apache.
Could you help me create the list of version numbers?

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 08/06/2018 11:32AM
Subject: Re: [DISCUSSION]: Release plan of OpenWhisk 0.9.0 for all modules



"Vincent S Hou"  wrote on 08/03/2018 11:42:56 AM:
>
> In order to keep you on the same page, I will discuss my release
> plan for openwhisk 0.9.0 of all the 13 modules.
>
> As you know, we have already released OpenWhisk main module for
> Version 0.9.0 in Apache for the first time. There are still 12 other
> modules/projects on the roadmap. I would like to release the rest of
> them in groups:
>
> * client go and cli as a group,
> * catalog and apigateway as a group,
> * wskdeploy and deploy cube as a group,
> * Nodejs, Java and Swift runtimes as a group,
> * Docker, Php and Python as a group,
>
> till all the modules are released under 0.9.0, which means I will
> send out emails for votes based on different groups. Please prepare
> for them. I expect another month to release all the rest modules, on
> top of main module.
>


Hi Vincent,

Releasing in groups makes sense to me to reduce the number of VOTE
email chains.

However, I do not think it is desirable to release the various
runtimes with a 0.9.0-incubating version number.  This is going to be
confusing to users because there are already "nightly snapshot" tags with
version numbers greater than 0.9.0 for all of the runtime git repos.   I
think instead we should be making official Apache releases with numbering
schemes that are compatible with the most recent pre-existing snapshot tag
for each runtime.   For example, openwhisk-runtime-python-1.0.2-incubating
for the Python runtime (or 1.0.3 if we want/need to bump the minor number
to pick up the latest master branch in the official release).
We expect the runtimes will be released on independent cadences in
the future, so the version numbers aren't going to stay synchronized with
each other (or the core system).  So I don't see that we should try to
force a uniform starting number now.

regards,

--dave

[RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client go and CLI

[Vincent S Hou]

Hi all,

Thanks a lot for taking the time to vote the release 0.9.0 of OpenWhisk client 
go and CLI.
The vote is passed with 3 +1s (binding).

Binding +1:

Daisy Guo
Matt Rutkowski
Vincent Hou

There is no -1 vote or 0 vote.

The vote has passed in the dev list of OpenWhisk, based on Apache voting 
policy. 
I am closing this mail thread, and will send out another email for IPMC to vote.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Forwarded by Vincent S Hou/Raleigh/IBM on 08/05/2018 10:11PM -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 07/31/2018 06:36PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client 
go and CLI

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk client go and CLI.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-215.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are two modules 
within this release. The artifact were built from the following Git commit IDs:
* openwhisk-client-go: 90976ef, Update the doc of client go to make it clear 
for 0.9.0
* openwhisk-cli: 4a5a372, Bump gradle and scoverage version

The source code artifact of openwhisk client go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk cli can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: client go and CLI
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [DISCUSSION]: Release plan of OpenWhisk 0.9.0 for all modules

[Vincent S Hou]

Hi Rodric,

A group means nothing else but to release them together.
We can put any two or few projects together as a GROUP. We still release 
separate tar files, even if they are in a group. Like in the mail thread for 
client go and cli, we still
release two artifacts:
The source code artifact of openwhisk client go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz

The source code artifact of openwhisk cli can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz

but they are in a GROUP.

The reason I want to group them is to avoid sending out 13 mail for votes. 
Instead, I only need to send out 5 or 6. Don't get it complicated.

A GROUP is just a group, which does not mean the items have any interaction or 
mixture.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Rodric Rabbah  wrote: -
To: dev@openwhisk.apache.org
From: Rodric Rabbah 
Date: 08/04/2018 09:47AM
Subject: Re: [DISCUSSION]: Release plan of OpenWhisk 0.9.0 for all modules

Hi Vincent,

what do you mean by a group - is it a single tar ball that includes a
directory for each git repository?
without knowing specifically what you mean by a group, the following may
not make sense but

- catalog and apigatway should be orthogonal - can you explain the logic
behind coupling them
- wskdeploy and kube deploy also orthogonal (one is user facing the other
operator facing)
- we should include the compose deployment (if we group compose and kube
together, that makes more sense to me)
- docker, python and swift as a group might make more sense since the
latter depend on docker image
- nodejs, java, php (eventually ruby and ballerina) are all independent
runtimes

-r

On Fri, Aug 3, 2018 at 11:42 AM, Vincent S Hou  wrote:

> Hi all,
>
> In order to keep you on the same page, I will discuss my release plan for
> openwhisk 0.9.0 of all the 13 modules.
>
> As you know, we have already released OpenWhisk main module for Version
> 0.9.0 in Apache for the first time. There are still 12 other
> modules/projects on the roadmap. I would like to release the rest of them
> in groups:
>
> * client go and cli as a group,
> * catalog and apigateway as a group,
> * wskdeploy and deploy cube as a group,
> * Nodejs, Java and Swift runtimes as a group,
> * Docker, Php and Python as a group,
>
> till all the modules are released under 0.9.0, which means I will send out
> emails for votes based on different groups. Please prepare for them. I
> expect another month to release all the rest modules, on top of main module.
>
> I will tag all of them as Version 0.9.0-incubating to be consistent with
> the main module, so far in the end we will have all the 13 modules under
> the same version number for users to pick, build and install.
>
> I also offer a full-set artifact named openwhisk-0.9.0-incubating-all.tar.gz
> including all the 13 modules for one-stop download, after all the 13
> modules are released.
>
> The reason why we would not release all the modules at a time was
> discussed here:https://www.mail-archive.com/dev@openwhisk.apache.org/m
> sg01893.html. This release plan I proposed above is a compromise of
> release all at a time and release one-by-one. I would like to hear the
> comments from about this release plan. If no objection is received, we will
> go with it.
>
> Thank you.
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> Cloud
>
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
> States
>
>

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client go and CLI

[Vincent S Hou]

 
I vote +1 for the release of Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk 
client go and CLI.

Checklist for reference:
[X] Download links are valid.
[X] Checksums and PGP signatures are valid.
[X] DISCLAIMER is included.
[X] Source code artifacts have correct names matching the current release.
[X] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[X] All files have license headers if necessary.
[X] No compiled archives bundled in source archive.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Ying Chun Guo"  wrote: -
To: dev@openwhisk.apache.org
From: "Ying Chun Guo" 
Date: 08/03/2018 04:03AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk 
client go and CLI

I vote +1 Release as Apache OpenWhisk 0.9.0-incubating: client go and CLI.
Thanks to Vincent for taking this effort.

Checklist for reference:
[X] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[X] DISCLAIMER is included.
[X] Source code artifacts have correct names matching the current release.
[X] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[X] All files have license headers if necessary.
[X] No compiled archives bundled in source archive.

Best regards
Ying Chun Guo (Daisy)


-"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 08/01/2018 06:36AM
Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client 
go and CLI

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk client go and CLI.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-215.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are two modules 
within this release. The artifact were built from the following Git commit IDs:
* openwhisk-client-go: 90976ef, Update the doc of client go to make it clear 
for 0.9.0
* openwhisk-cli: 4a5a372, Bump gradle and scoverage version

The source code artifact of openwhisk client go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk cli can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: client go and CLI
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[DISCUSSION]: Release plan of OpenWhisk 0.9.0 for all modules

[Vincent S Hou]

Hi all,

In order to keep you on the same page, I will discuss my release plan for 
openwhisk 0.9.0 of all the 13 modules.

As you know, we have already released OpenWhisk main module for Version 0.9.0 
in Apache for the first time. There are still 12 other modules/projects on the 
roadmap. I would like to release the rest of them in groups:

* client go and cli as a group,
* catalog and apigateway as a group,
* wskdeploy and deploy cube as a group,
* Nodejs, Java and Swift runtimes as a group,
* Docker, Php and Python as a group,

till all the modules are released under 0.9.0, which means I will send out 
emails for votes based on different groups. Please prepare for them. I expect 
another month to release all the rest modules, on top of main module.

I will tag all of them as Version 0.9.0-incubating to be consistent with the 
main module, so far in the end we will have all the 13 modules under the same 
version number for users to pick, build and install.

I also offer a full-set artifact named openwhisk-0.9.0-incubating-all.tar.gz 
including all the 13 modules for one-stop download, after all the 13 modules 
are released.

The reason why we would not release all the modules at a time was discussed 
here:https://www.mail-archive.com/dev@openwhisk.apache.org/msg01893.html. This 
release plan I proposed above is a compromise of release all at a time and 
release one-by-one. I would like to hear the comments from about this release 
plan. If no objection is received, we will go with it. 

Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1: OpenWhisk client go and CLI

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: OpenWhisk client go and CLI.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-215.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are two modules 
within this release. The artifact were built from the following Git commit IDs:
* openwhisk-client-go: 90976ef, Update the doc of client go to make it clear 
for 0.9.0
* openwhisk-cli: 4a5a372, Bump gradle and scoverage version

The source code artifact of openwhisk client go can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk client go can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc


The source code artifact of openwhisk cli can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk cli can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating: client go and CLI
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[ANNOUNCE] Apache OpenWhisk, main module (incubating) 0.9.0 released

[Vincent S Hou]

Hi everyone,

We are pleased to announce that Apache OpenWhisk, main module (incubating) 
0.9.0 is released.

OpenWhisk is a cloud-first distributed event-based programming service. It 
provides a programming model to upload event handlers to a cloud service, and 
register the handlers to respond to various events. This is the first time that 
OpenWhisk is released under Apache as an incubator project.

The download links of the current release is available at:
https://openwhisk.apache.org/downloads.html

Vincent Hou
On behalf of the OpenWhisk team

=
*DISCLAIMER*
Apache OpenWhisk (incubating) is an effort undergoing incubation at The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

[ANNOUNCE] Apache OpenWhisk, main module (incubating) 0.9.0 released

[Vincent S Hou]

Hi everyone,

This is the announcement of the 0.9.0 release of OpenWhisk, main module.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Forwarded by Vincent S Hou/Raleigh/IBM on 07/19/2018 02:40PM -
To: gene...@incubator.apache.org
From: "Vincent S Hou" 
Date: 07/19/2018 02:32PM
Subject: [ANNOUNCE] Apache OpenWhisk, main module (incubating) 0.9.0 released

Hi everyone,

We are pleased to announce that Apache OpenWhisk, main module (incubating) 
0.9.0 is released.

OpenWhisk is a cloud-first distributed event-based programming service. It 
provides a programming model to upload event handlers to a cloud service, and 
register the handlers to respond to various events. This is the first time that 
OpenWhisk is released under Apache as an incubator project.

The release is available at:
https://www.apache.org/dist/incubator/openwhisk/apache-openwhisk-0.9.0-incubating/

The official website of OpenWhisk, https://openwhisk.apache.org/, is currently 
working on the webpage for the download links.

Vincent Hou
On behalf of the OpenWhisk team


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE]: Release Apache OpenWhisk (Incubating): main module 0.9.0 [RC2]

[Vincent S Hou]

Hi all,

Thanks a lot for taking the time to vote the release 0.9.0 of OpenWhisk main 
module.

The vote is passed with 5 +1s (binding).

Binding +1:

Bertrand Delacretaz
Jim Jagielski
Justin Mclean
Mark Struberg
Matt Sicker

There is no -1 vote or 0 vote.

I will proceed with the next steps for the release.
 

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: gene...@incubator.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 07/11/2018 10:38AM
Subject: [VOTE]: Release Apache OpenWhisk (Incubating): main module 0.9.0 [RC2]

Dear IPMC members,

This is a call for vote to release Apache OpenWhisk (Incubating): main module 
version 0.9.0.

The Apache OpenWhisk community has voted on and approved a proposal to release 
Apache OpenWhisk (Incubating): main module version 0.9.0.

We now kindly request the Incubator PMC members to review and vote on this 
incubator release.

Apache OpenWhisk (incubating) is a serverless, open source cloud platform that 
executes functions in response to events at any scale.

OpenWhisk main module vote thread:
https://lists.apache.org/thread.html/3d4952420a38936cbc6caeddf1979270f77469928e6092df84299ca1@%3Cdev.openwhisk.apache.org%3E

OpenWhisk main module vote result thread:
https://lists.apache.org/thread.html/a825791284657c9860e0f63ec68f08d085da818e93cc14a6756273dc@%3Cdev.openwhisk.apache.org%3E

This release comprises of source code distribution only. There is one module 
within this release. The artifact was built from the following Git commit ID:
* openwhisk: b1476b9, add until for all ansible retries (#3806), 
https://github.com/apache/incubator-openwhisk/commit/b1476b9992bab90c077ac2f1fbdc67d10d9d2c39
It will be tagged with the version.

The source code artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for each artifact can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.sha512

The signature of this artifact can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.asc

KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
This key has been validated here: 
http://pgp.mit.edu/pks/lookup?search=houshengbo=index

This is the first time that Apache OpenWhisk: main module requests for a 
release, so there is no file of CHANGELOG.

The documentation can be found at:
https://github.com/apache/incubator-openwhisk-release/blob/master/releases/0.9.0-incubating/INSTALL.md
 or
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/doc/INSTALL.md

We are currently using the tool called 
openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
release all the modules of OpenWhisk. The instruction for release managers can 
be found at: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
 This tool
supports both manual and automated modes to package the source code, sign the 
artifacts and upload the artifacts into Apache SVN repositories.

The vote will be open for at least 72 hours or until necessary number of votes 
are reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Best wishes.
Vincent Hou

Apache OpenWhisk team

[VOTE]: Release Apache OpenWhisk (Incubating): main module 0.9.0 [RC2]

[Vincent S Hou]

Dear IPMC members,

This is a call for vote to release Apache OpenWhisk (Incubating): main module 
version 0.9.0.

The Apache OpenWhisk community has voted on and approved a proposal to release 
Apache OpenWhisk (Incubating): main module version 0.9.0.

We now kindly request the Incubator PMC members to review and vote on this 
incubator release.

Apache OpenWhisk (incubating) is a serverless, open source cloud platform that 
executes functions in response to events at any scale.

OpenWhisk main module vote thread:
https://lists.apache.org/thread.html/3d4952420a38936cbc6caeddf1979270f77469928e6092df84299ca1@%3Cdev.openwhisk.apache.org%3E

OpenWhisk main module vote result thread:
https://lists.apache.org/thread.html/a825791284657c9860e0f63ec68f08d085da818e93cc14a6756273dc@%3Cdev.openwhisk.apache.org%3E

This release comprises of source code distribution only. There is one module 
within this release. The artifact was built from the following Git commit ID:
* openwhisk: b1476b9, add until for all ansible retries (#3806), 
https://github.com/apache/incubator-openwhisk/commit/b1476b9992bab90c077ac2f1fbdc67d10d9d2c39
It will be tagged with the version.

The source code artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for each artifact can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.sha512

The signature of this artifact can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.asc

KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
This key has been validated here: 
http://pgp.mit.edu/pks/lookup?search=houshengbo=index

This is the first time that Apache OpenWhisk: main module requests for a 
release, so there is no file of CHANGELOG.

The documentation can be found at:
https://github.com/apache/incubator-openwhisk-release/blob/master/releases/0.9.0-incubating/INSTALL.md
 or
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/doc/INSTALL.md

We are currently using the tool called 
openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
release all the modules of OpenWhisk. The instruction for release managers can 
be found at: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
 This tool
supports both manual and automated modes to package the source code, sign the 
artifacts and upload the artifacts into Apache SVN repositories.

The vote will be open for at least 72 hours or until necessary number of votes 
are reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Best wishes.
Vincent Hou

Apache OpenWhisk team

Re: [RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module

[Vincent S Hou]

Plus, we have another two binding votes for OpenWhisk main module RC2.

+1 (binding), Dragos Dascalita Haut  
+1 (binding), Matt Rutkowski

We have already received 8 +1 votes (bindings), 2 +1 votes (non-binding) and no 
0 or -1 votes.
The vote has passed in the dev list of OpenWhisk, based on Apache voting 
policy. 
I am closing this mail thread, and will send out another email for IPMC to vote.

Thanks.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: gene...@incubator.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 07/10/2018 04:35PM
Cc: dev@openwhisk.apache.org
Subject: [RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main 
OpenWhisk module

Dear IPMC members,

This vote has passed with 6 +1 votes (bindings), 2 +1 votes (non-binding) and 
no 0 or -1 votes.

+1 (binding), David Grove
+1 (binding), James Dubee
+1 (binding), James Thomas
+1 (binding), Rodric Rabbah
+1 (binding), Vincent Hou
+1 (binding), Ying Chun Guo


+1 (non-binding), Justin Halsall
+1 (non-binding), Priti Desai

Please vote on the OpenWhisk main module to be released as a candidate for 
OpenWhisk 0.9.0. Thank you very much.

We are currently using the tool called 
openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
release all the modules of OpenWhisk. The instruction for release managers can 
be found at: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.

This tool supports both manual and automated modes to package the source code, 
sign the artifacts and upload the artifacts into Apache SVN repositories.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 07/03/2018 02:55PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk 
module

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 0.9.0-incubating 
rc2: main OpenWhisk module.

We have resolved all the issues regarding the dependency's license, gradle 
wrapper, some documentation issues, etc, based on we discussed during last 
voting mail thread for rc1.

This release comprises of source code distribution only. There is one module 
within this release. The artifact was built from the following Git commit ID:
* openwhisk: b1476b9, add until for all ansible retries (#3806)

The source code artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for each artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.sha512

The signature of this artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.asc

KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating rc2.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

[RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module

[Vincent S Hou]

Dear IPMC members,

This vote has passed with 6 +1 votes (bindings), 2 +1 votes (non-binding) and 
no 0 or -1 votes.

+1 (binding), David Grove
+1 (binding), James Dubee
+1 (binding), James Thomas
+1 (binding), Rodric Rabbah
+1 (binding), Vincent Hou
+1 (binding), Ying Chun Guo


+1 (non-binding), Justin Halsall
+1 (non-binding), Priti Desai

Please vote on the OpenWhisk main module to be released as a candidate for 
OpenWhisk 0.9.0. Thank you very much.

We are currently using the tool called 
openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
release all the modules of OpenWhisk. The instruction for release managers can 
be found at: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.

This tool supports both manual and automated modes to package the source code, 
sign the artifacts and upload the artifacts into Apache SVN repositories.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Vincent S Hou/Raleigh/IBM wrote: -
To: dev@openwhisk.apache.org
From: Vincent S Hou/Raleigh/IBM
Date: 07/03/2018 02:55PM
Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk 
module

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 0.9.0-incubating 
rc2: main OpenWhisk module.

We have resolved all the issues regarding the dependency's license, gradle 
wrapper, some documentation issues, etc, based on we discussed during last 
voting mail thread for rc1.

This release comprises of source code distribution only. There is one module 
within this release. The artifact was built from the following Git commit ID:
* openwhisk: b1476b9, add until for all ansible retries (#3806)

The source code artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz

The SHA-512 checksum for each artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.sha512

The signature of this artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.asc

KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating rc2.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module

[Vincent S Hou]

Thank everybody for the votes. 

I will consolidate the result and forward it to the IPMC at 
gene...@incubator.apache.org, for further approval.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Priti Desai"  wrote: -
To: dev@openwhisk.apache.org
From: "Priti Desai" 
Date: 07/10/2018 03:30PM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main 
OpenWhisk module

I vote +1 for Release as Apache OpenWhisk 0.9.0-incubating

Checklist for reference:
[X] Download links are valid.
[O] Checksums and PGP signatures are valid.
[X] Source code artifacts have correct names matching the current release.
[X] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[X] All files have license headers if necessary.
[O] No compiled archives bundled in source archive.

Cheers
Priti




From:   Rodric Rabbah 
To: dev@openwhisk.apache.org
Date:   07/10/2018 08:34 AM
Subject:Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: 
main OpenWhisk module



I vote +1 for Release as Apache OpenWhisk 0.9.0-incubating

Checklist for reference:
[X] Download links are valid.
[X] Checksums and PGP signatures are valid.
[X] Source code artifacts have correct names matching the current release.
[X] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[X] All files have license headers if necessary.
[X] No compiled archives bundled in source archive.

On Tue, Jul 10, 2018 at 10:55 AM, Ying Chun Guo  
wrote:

> I vote +1 for Release as Apache OpenWhisk 0.9.0-incubating
>
> Checklist for reference:
> [X] Download links are valid.
> [O] Checksums and PGP signatures are valid.
> [X] Source code artifacts have correct names matching the current 
release.
> [X] LICENSE and NOTICE files are correct for each OpenWhisk repo.
> [X] All files have license headers if necessary.
> [X] No compiled archives bundled in source archive.
>
>
> Best regards
> Ying Chun Guo (Daisy)
>
>
> -"Vincent S Hou"  wrote: -
> To: dev@openwhisk.apache.org
> From: "Vincent S Hou" 
> Date: 07/04/2018 02:55AM
> Subject: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main
> OpenWhisk module
>
> Hi everyone,
>
> This is to call for a vote for the release of Apache OpenWhisk
> 0.9.0-incubating rc2: main OpenWhisk module.
>
> We have resolved all the issues regarding the dependency's license, 
gradle
> wrapper, some documentation issues, etc, based on we discussed during 
last
> voting mail thread for rc1.
>
> This release comprises of source code distribution only. There is one
> module within this release. The artifact was built from the following 
Git
> commit ID:
> * openwhisk: b1476b9, add until for all ansible retries (#3806)
>
> The source code artifacts can be found at:
> 
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/

> apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.
> 0-incubating-sources.tar.gz
>
> The MD5 checksum for each artifact can be found via:
> 
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/

> apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.
> 0-incubating-sources.tar.gz.md5
>
> The SHA-512 checksum for each artifact can be found via:
> 
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/

> apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.
> 0-incubating-sources.tar.gz.sha512
>
> The signature of this artifact can be found via:
> 
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/

> apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.
> 0-incubating-sources.tar.gz.asc
>
> KEYS file is available here:
> 
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

>
> The documentation can be found via:
> 
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/

> apache-openwhisk-0.9.0-incubating-rc2/doc/INSTALL.md
>
> Please vote on releasing this package as Apache OpenWhisk 
0.9.0-incubating
> rc2.
>
> The vote will be open for at least 72 hours.
> [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release and the reason
>
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] Source code artifacts have correct names matching the current 
release.
> [ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
> [ ] All files have license headers if necessary.
> [ ] No compiled archives bundled in source archive.
>
> Thank you very much.
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> Cloud
>
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
> States
>
>
>
>

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module

[Vincent S Hou]

Thank Dave for the vote and comments. I am updating the doc now to make it more 
straightforward.

I vote +1 as well to release OpenWhisk 0.9.0-incubating rc2 module

Checklist for reference:
[ X ] Download links are valid.(Please disregard the md5 link, since we do not 
need it)
[ X ] Checksums and PGP signatures are valid.
[ X ] Source code artifacts have correct names matching the current release.
[ X ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ X ] All files have license headers if necessary.
[ X ] No compiled archives bundled in source archive.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 07/03/2018 06:22PM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main 
OpenWhisk module

I vote

+1 Release as Apache OpenWhisk 0.9.0-incubating

Checklist for reference:
[ X ] Download links are valid.
[ X ] Checksums and PGP signatures are valid.
[ X ] Source code artifacts have correct names matching the current
release.
[ X ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ X ] All files have license headers if necessary.  (assuming I ran
scancode correctly...see below).
[ X ] No compiled archives bundled in source archive.

I also verified that the release built on MacOS and that I could deploy it
an invoke the echo message per the release documentation.

Two very small things that could be improved in the release documentation
file.  I do not see either of these as release blockers (thus the +1 vote).

(1)  In the "Run OpenWhisk" section, it uses both `wsk` and `bin/wsk`.  We
should probably either say `$OPENWHISK_HOME/bin/wsk` uniformly or say that
we assume that the user has put the wsk CLI on their path.

(2) I think it would be better to include the exact commands for running
scancode to verify that all files have license headers instead of
referencing the scancode tutorial.  For example, I am not 100% positive if
by following the tutorial (see shell transcript below) really checked the
right rules or if I needed to invoke scancode with a specific configuration
file.

--dave

daves-mbp-3:incubator-openwhisk-0.9.0-incubating dgrove$ python
~/code/openwhisk/incubator-openwhisk-utilities/scancode/scanCode.py .
Reading configuration file
[/Users/dgrove/code/openwhisk/incubator-openwhisk-utilities/scancode/scanCode.cfg]...
Scanning files starting at [.]...
All checks passed.

[VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 0.9.0-incubating 
rc2: main OpenWhisk module.

We have resolved all the issues regarding the dependency's license, gradle 
wrapper, some documentation issues, etc, based on we discussed during last 
voting mail thread for rc1.

This release comprises of source code distribution only. There is one module 
within this release. The artifact was built from the following Git commit ID:
* openwhisk: b1476b9, add until for all ansible retries (#3806)

The source code artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz

The MD5 checksum for each artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.md5

The SHA-512 checksum for each artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.sha512

The signature of this artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.asc

KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating rc2.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: No test code in the release? (was: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module)

[Vincent S Hou]

Hi Bertrand,

The reason we do not ship the tests in the artifact for this release is that 
there are test files with unidentified licenses, which may bring risks in when 
we distribute them.

After we resolve the license issues, we will package them in the source code 
artifact.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Bertrand Delacretaz  wrote: -
To: dev@openwhisk.apache.org
From: Bertrand Delacretaz 
Date: 07/03/2018 04:33AM
Subject: No test code in the release? (was: [DISCUSS] Release Apache OpenWhisk 
0.9.0-incubating: main OpenWhisk module)

Hi,

On Mon, Jul 2, 2018 at 10:52 PM Vincent S Hou  wrote:
> ...I have proposed a PR fixing all the issues raised in this mail thread: 
> https://github.com/apache/incubator-openwhisk-release/pull/218 ...

I noticed the "Since this release does not ship the code of test
cases.." comment there.

What's the plan for these test cases, are they part of a separate module?

If yes, I think future releases of these modules should be synced, so
that people know which set of tests to use against a version of the
core release.

This is not an urgent problem, I'm just trying to understand the idea.

-Bertrand

Re: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

I have proposed a PR fixing all the issues raised in this mail thread: 
https://github.com/apache/incubator-openwhisk-release/pull/218
Welcome to review it.
When this PR is merged, we will have the artifact generated for rc2.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Carlos Santana  wrote: -
To: dev@openwhisk.apache.org
From: Carlos Santana 
Date: 07/01/2018 10:21PM
Subject: Re: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main 
OpenWhisk module

Thank you Vincent this is what having RCs process in place is for, no problem 
or issues on having multiple candidates as we move forward we will do less RCs 
in future releases as everything settles.  

- Carlos Santana
@csantanapr

> On Jul 1, 2018, at 9:45 PM, Vincent S Hou  wrote:
> 
> I have replied to the mail thread [VOTE] Release Apache OpenWhisk 
> 0.9.0-incubating: main OpenWhisk module, regarding my plan.
> 
> I will open another mail thread to vote openwhisk rc2, after I fix the issues 
> based on people's comments. OpenWhisk is currently ready to pick up a new 
> commit.
> I still need to work on the issues for documentation: 
> https://github.com/apache/incubator-openwhisk-release/issues
> 
> Stay tuned.
> 
> Thank you for the votes.
> 
> 
> 
> Best wishes.
> Vincent Hou (侯胜博)
> 
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
> 
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
> 
> -Carlos Santana  wrote: -
> To: dev@openwhisk.apache.org
> From: Carlos Santana 
> Date: 06/30/2018 08:05AM
> Subject: Re: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main 
> OpenWhisk module
> 
> Sorry Rodric my second part of my email was intended for Vincent
> 
> Vincent you want to do an RC2 and address or continue since you are release
> manager I don’t want to impose anything on you.
> 
> But if you want to continue I think you have enough votes to close it and
> move forward with IPMC.
>> On Sat, Jun 30, 2018 at 5:44 AM Rodric Rabbah  wrote:
>> 
>> I figured out the issue - posted it as a comment on GitHub.
>> 
>> -r
>> 
>>> On Jun 30, 2018, at 1:40 AM, Carlos Santana 
>> wrote:
>>> 
>>> Rodric
>>> I ran it on my mac and think I made sure I unset my OPENWHISK_HOME.
>>> 
>>> I can try again with a clean OS using a fresh Vagrant Ubuntu14 and using
>>> the tgz and give it a go,
>>> 
>>> Are you sure is not easier to do an RC2 and fix this issues in the
>> artifact?
>>> 
>>> If you want to proceed, then go ahead and close the vote result in dev
>> and
>>> start the new vote on in incubator list to see what would be the vote
>>> results, but take into account you will need to be on top of the findings
>>> which would be similar as the found in the dev list.
>>> 
>>> -- Carlos
>>> 
>>>> On Fri, Jun 29, 2018 at 2:19 PM Rodric Rabbah  wrote:
>>>> 
>>>> Thanks.
>>>> 
>>>> -r
>>>> 
>>>>> On Jun 29, 2018, at 11:28 AM, Vincent S Hou  wrote:
>>>>> 
>>>>> Hi Rodric,
>>>>> 
>>>>> I think all the issues can be resolved by updating the instruction of
>>>> installation.
>>>>> 
>>>>> I can definitely work on that.
>>>>> 
>>>>> Our vote for main OpenWhisk module is effective. After consolidating
>> the
>>>> result and fixing the document, we should proceed with the release.
>>>>> 
>>>>> I have tried the local deployment, which turned out to be fine. I have
>>>> documented some known issues in the instruction.
>>>>> 
>>>>> 
>>>>> 
>>>>> Best wishes.
>>>>> Vincent Hou (侯胜博)
>>>>> 
>>>>> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
>>>> Cloud
>>>>> 
>>>>> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
>>>>> Phone: +1(919)254-7182 <(919)%20254-7182>
>>>>> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
>>>> States
>>>>> 
>>>>> -Rodric Rabbah  wrote: -
>>>>> To: de

Re: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

I have replied to the mail thread [VOTE] Release Apache OpenWhisk 
0.9.0-incubating: main OpenWhisk module, regarding my plan.

I will open another mail thread to vote openwhisk rc2, after I fix the issues 
based on people's comments. OpenWhisk is currently ready to pick up a new 
commit.
I still need to work on the issues for documentation: 
https://github.com/apache/incubator-openwhisk-release/issues

Stay tuned.

Thank you for the votes.



Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Carlos Santana  wrote: -
To: dev@openwhisk.apache.org
From: Carlos Santana 
Date: 06/30/2018 08:05AM
Subject: Re: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main 
OpenWhisk module

Sorry Rodric my second part of my email was intended for Vincent

Vincent you want to do an RC2 and address or continue since you are release
manager I don’t want to impose anything on you.

But if you want to continue I think you have enough votes to close it and
move forward with IPMC.
On Sat, Jun 30, 2018 at 5:44 AM Rodric Rabbah  wrote:

> I figured out the issue - posted it as a comment on GitHub.
>
> -r
>
> > On Jun 30, 2018, at 1:40 AM, Carlos Santana 
> wrote:
> >
> > Rodric
> >  I ran it on my mac and think I made sure I unset my OPENWHISK_HOME.
> >
> > I can try again with a clean OS using a fresh Vagrant Ubuntu14 and using
> > the tgz and give it a go,
> >
> > Are you sure is not easier to do an RC2 and fix this issues in the
> artifact?
> >
> > If you want to proceed, then go ahead and close the vote result in dev
> and
> > start the new vote on in incubator list to see what would be the vote
> > results, but take into account you will need to be on top of the findings
> > which would be similar as the found in the dev list.
> >
> > -- Carlos
> >
> >> On Fri, Jun 29, 2018 at 2:19 PM Rodric Rabbah  wrote:
> >>
> >> Thanks.
> >>
> >> -r
> >>
> >>> On Jun 29, 2018, at 11:28 AM, Vincent S Hou  wrote:
> >>>
> >>> Hi Rodric,
> >>>
> >>> I think all the issues can be resolved by updating the instruction of
> >> installation.
> >>>
> >>> I can definitely work on that.
> >>>
> >>> Our vote for main OpenWhisk module is effective. After consolidating
> the
> >> result and fixing the document, we should proceed with the release.
> >>>
> >>> I have tried the local deployment, which turned out to be fine. I have
> >> documented some known issues in the instruction.
> >>>
> >>>
> >>>
> >>> Best wishes.
> >>> Vincent Hou (侯胜博)
> >>>
> >>> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> >> Cloud
> >>>
> >>> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> >>> Phone: +1(919)254-7182 <(919)%20254-7182>
> >>> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
> >> States
> >>>
> >>> -Rodric Rabbah  wrote: -
> >>> To: dev@openwhisk.apache.org
> >>> From: Rodric Rabbah 
> >>> Date: 06/29/2018 08:38AM
> >>> Subject: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main
> >> OpenWhisk module
> >>>
> >>> I am breaking this out into a DISCUSS thread so not to pollute the
> vote.
> >> In
> >>> completing this checking list:
> >>>
> >>> [x] Download links are valid.
> >>> [x] Checksums and PGP signatures are valid.
> >>> [x] Source code artifacts have correct names matching the current
> >> release.
> >>> [x] LICENSE and NOTICE files are correct for each OpenWhisk repo.
> >>> [x] All files have license headers if necessary. (checked with
> scan-code)
> >>> [x] No compiled archives bundled in source archive (modulo
> >>> gradle-wrapper.jar).
> >>>
> >>> I ran into a few hiccups (some duplicates with Bertrand's) for which I
> >>> opened the following issues:
> >>>
> >>> https://github.com/apache/incubator-openwhisk-release/issues/207
> >>> https://github.com/apache/incubator-openwhisk-release/issues/208
> >>> https://github.com/apache/incubator-openwhisk-release/issues/209 (bug)
> >>> https://github.com/apache/incubator-openwhisk-release/issues/210
> >>> https://github.com/apache/incubator-openwhisk-release/issues/211 (bug)
> >>> https://github.com/apache/incubator-openwhisk-release/issues/212
> >>> https://github.com/apache/incubator-openwhisk-release/issues/213 (bug,
> >>> blocks deployment)
> >>> https://github.com/apache/incubator-openwhisk-release/issues/214
> >>>
> >>> Carlos I'm not sure how you deployed successfully and ran hello world.
> >> I'd
> >>> like to know if this is isolated to me. It looks like both Betrand and
> I
> >>> ran into issues with deployment (beyond the doc bug).
> >>>
> >>> -r
> >>>
> >>
>

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

Thank everybody for your active vote.

We have received enough votes to approve the release in this mail thread, but I 
realized that we still need to resolve the license issue for the spray caching 
and remove the gradle wrapper. I have made these changes on openwhisk repo, and 
will propose another candidate RC2 for folks to vote.

In addition, I will fix the some issues for the documentation as well. You can 
find them with the tag "release" at this link 
https://github.com/apache/incubator-openwhisk-release/issues.

This mail thread is closed. I will open another mail thread to vote openwhisk 
rc2. Stay tuned.

Thank you for your votes.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-----"Vincent S Hou"  wrote: -
To: dev@openwhisk.apache.org
From: "Vincent S Hou" 
Date: 06/29/2018 03:11PM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk 
module

Correction:
We removed the gradle wrapper in the package. Instead, users need to download 
it and place it in the correct folder to build the source code.

Regarding the copyright, we will remove the one for lightbend, and keep the one 
for spray project.


Hi Luciano,

We will remove the md5.

Version number will be added.

We have a comprehensive definition about which kind of source files include 
long or short version of license header.
Please refer to this link: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md.
 Ansible files will be equipped with short version of license header. Both full 
and short versions are acceptable.

OpenWhisk is a scala-based project, which relies on gradle build. The gradle 
jar is included for build purpose only. We were investigating whether we should 
include this gradle jar. We did not find any official documents regarding that, 
but we see many other scal-based Apache project released their source code with 
the gradle jar, since it is used for the basic build need. For example, apache 
beam, available https://dist.apache.org/repos/dist/release/beam/2.5.0/.
So we decided to release it together with the source code.

We are now doubling confirming the copyright of spray caching.

Thanks for the comments.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Luciano Resende  wrote: -
To: dev@openwhisk.apache.org
From: Luciano Resende 
Date: 06/29/2018 08:36AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk 
module

We are recommending not to use MD5 anymore, so before going to IPMC please
delete that.

The source tar file extracts to incubator-openwhisk without the version
info, which might be overwritten by next release.

Most of the ansible files do not have the full Apache License header, but
something like a two-liner version of it, is this acceptable?

Also, could you please check the proper info/copyright for the Spray
dependency, the link provided on the license says:
Copyright © 2011-2015 the spray project <http://spray.io>
But the openwhisky license file has copyright info like:
Copyright (C) 2017 Lightbend Inc. <http://www.lightbend.com/>

Also, we recommend that source distributions have no binary files, and this
seem to have a gradle related jar bundled together.

I am +0, but most of the items above are issues that may come up when you
reach IPMC, so be prepared to have an answer for them.

On Mon, Jun 25, 2018 at 2:27 PM Vincent S Hou  wrote:

> Hi everyone,
>
> This is to call for a vote for the release of Apache OpenWhisk
> 0.9.0-incubating: main OpenWhisk module.
>
> List of JIRA ticket(s) resolved for this release can be found at
> https://issues.apache.org/jira/browse/INCUBATOR-213.
>
> To learn more about Apache OpenWhisk, please visit
> https://openwhisk.apache.org/.
>
> This  release comprises of source code distribution only. There is one
> module within this release. The artifact was built from  the following Git
> commit ID:
> * openwhisk: 76dadd2, Bump gradle and scoverage version
>
> The source code artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz
>
> The MD5 checksum for each artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.md5
>
> The SHA-512 checksum for each artifact can be foun

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

Correction:
We removed the gradle wrapper in the package. Instead, users need to download 
it and place it in the correct folder to build the source code.

Regarding the copyright, we will remove the one for lightbend, and keep the one 
for spray project.


Hi Luciano,

We will remove the md5.

Version number will be added.

We have a comprehensive definition about which kind of source files include 
long or short version of license header.
Please refer to this link: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md.
 Ansible files will be equipped with short version of license header. Both full 
and short versions are acceptable.

OpenWhisk is a scala-based project, which relies on gradle build. The gradle 
jar is included for build purpose only. We were investigating whether we should 
include this gradle jar. We did not find any official documents regarding that, 
but we see many other scal-based Apache project released their source code with 
the gradle jar, since it is used for the basic build need. For example, apache 
beam, available https://dist.apache.org/repos/dist/release/beam/2.5.0/.
So we decided to release it together with the source code.

We are now doubling confirming the copyright of spray caching.

Thanks for the comments.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Luciano Resende  wrote: -
To: dev@openwhisk.apache.org
From: Luciano Resende 
Date: 06/29/2018 08:36AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk 
module

We are recommending not to use MD5 anymore, so before going to IPMC please
delete that.

The source tar file extracts to incubator-openwhisk without the version
info, which might be overwritten by next release.

Most of the ansible files do not have the full Apache License header, but
something like a two-liner version of it, is this acceptable?

Also, could you please check the proper info/copyright for the Spray
dependency, the link provided on the license says:
Copyright © 2011-2015 the spray project <http://spray.io>
But the openwhisky license file has copyright info like:
Copyright (C) 2017 Lightbend Inc. <http://www.lightbend.com/>

Also, we recommend that source distributions have no binary files, and this
seem to have a gradle related jar bundled together.

I am +0, but most of the items above are issues that may come up when you
reach IPMC, so be prepared to have an answer for them.

On Mon, Jun 25, 2018 at 2:27 PM Vincent S Hou  wrote:

> Hi everyone,
>
> This is to call for a vote for the release of Apache OpenWhisk
> 0.9.0-incubating: main OpenWhisk module.
>
> List of JIRA ticket(s) resolved for this release can be found at
> https://issues.apache.org/jira/browse/INCUBATOR-213.
>
> To learn more about Apache OpenWhisk, please visit
> https://openwhisk.apache.org/.
>
> This  release comprises of source code distribution only. There is one
> module within this release. The artifact was built from  the following Git
> commit ID:
> * openwhisk: 76dadd2, Bump gradle and scoverage version
>
> The source code artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz
>
> The MD5 checksum for each artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.md5
>
> The SHA-512 checksum for each artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.sha512
>
> The signature of this artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.asc
>
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
>
> The documentation can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md
>
> Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.
>
> The vote will be open for at least 72 hours.
> [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release and the reason
>
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] Source code artifacts have correct names matching the current release.
> [ ] LICENSE and NOTICE files are correc

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

Hi Luciano,

The issue regarding the license in Spray. Here is something interesting I just 
found:
We actually rewrote some implementation by copying some code from 
spray.caching.Cache and spray.caching.SimpleLruCache.
The spray version we use is 1.3.4, which used to be license apache 2.0 with 
Copyright © 2011-2015 the spray project.

However, spray is superseded by Akka http later, and the copyright became 
Copyright (C) 2017 Lightbend Inc.

I am not sure which we shall keep.

I tend to keep the one with Copyright © 2011-2015 the spray project, because 
this is the version we refer to, and the copyright it used to be.
For the latest version of Akka http, replacing spray, we cannot find 
spray.caching.Cache and spray.caching.SimpleLruCache, any more, as the code
evolves. 

What is your opinion on it? Thx.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Luciano Resende  wrote: -
To: dev@openwhisk.apache.org
From: Luciano Resende 
Date: 06/29/2018 08:36AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk 
module

We are recommending not to use MD5 anymore, so before going to IPMC please
delete that.

The source tar file extracts to incubator-openwhisk without the version
info, which might be overwritten by next release.

Most of the ansible files do not have the full Apache License header, but
something like a two-liner version of it, is this acceptable?

Also, could you please check the proper info/copyright for the Spray
dependency, the link provided on the license says:
Copyright © 2011-2015 the spray project <http://spray.io>
But the openwhisky license file has copyright info like:
Copyright (C) 2017 Lightbend Inc. <http://www.lightbend.com/>

Also, we recommend that source distributions have no binary files, and this
seem to have a gradle related jar bundled together.

I am +0, but most of the items above are issues that may come up when you
reach IPMC, so be prepared to have an answer for them.

On Mon, Jun 25, 2018 at 2:27 PM Vincent S Hou  wrote:

> Hi everyone,
>
> This is to call for a vote for the release of Apache OpenWhisk
> 0.9.0-incubating: main OpenWhisk module.
>
> List of JIRA ticket(s) resolved for this release can be found at
> https://issues.apache.org/jira/browse/INCUBATOR-213.
>
> To learn more about Apache OpenWhisk, please visit
> https://openwhisk.apache.org/.
>
> This  release comprises of source code distribution only. There is one
> module within this release. The artifact was built from  the following Git
> commit ID:
> * openwhisk: 76dadd2, Bump gradle and scoverage version
>
> The source code artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz
>
> The MD5 checksum for each artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.md5
>
> The SHA-512 checksum for each artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.sha512
>
> The signature of this artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.asc
>
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
>
> The documentation can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md
>
> Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.
>
> The vote will be open for at least 72 hours.
> [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release and the reason
>
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] Source code artifacts have correct names matching the current release.
> [ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
> [ ] All files have license headers if necessary.
> [ ] No compiled archives bundled in source archive.
>
> Thank you very much.
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> Cloud
>
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
> States
>
>

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

Can we use the current key for the release of 0.9.0, and change the key later?
OpenWhisk looks fine so far regarding the release process. If we resign it, we 
have to re-run the vote.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Luciano Resende  wrote: -
To: dev@openwhisk.apache.org
From: Luciano Resende 
Date: 06/29/2018 11:11AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk 
module

On Fri, Jun 29, 2018 at 7:29 AM Vincent S Hou  wrote:

> This is the key, which is used by the Travis job. The private key is
> encrypted in the repo of incubator-openwhisk-release.
>
> For further releases, what email and use id can we use? Do we have them
> handy somewhere? @Bertrand, do you have suggestions?
>

What we recommend is to use the release manager personal key for signing
the release, he would usually have his own apache account info for
e-mail/id.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

Hi Luciano,

We will remove the md5.

Version number will be added.

We have a comprehensive definition about which kind of source files include 
long or short version of license header.
Please refer to this link: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md.
 Ansible files will be equipped with short version of license header. Both full 
and short versions are acceptable.

We are now doubling confirming the copyright of spray caching, and figuring out 
the gradle jar issue.

Thanks for the comments.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Luciano Resende  wrote: -
To: dev@openwhisk.apache.org
From: Luciano Resende 
Date: 06/29/2018 08:36AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk 
module

We are recommending not to use MD5 anymore, so before going to IPMC please
delete that.

The source tar file extracts to incubator-openwhisk without the version
info, which might be overwritten by next release.

Most of the ansible files do not have the full Apache License header, but
something like a two-liner version of it, is this acceptable?

Also, could you please check the proper info/copyright for the Spray
dependency, the link provided on the license says:
Copyright © 2011-2015 the spray project <http://spray.io>
But the openwhisky license file has copyright info like:
Copyright (C) 2017 Lightbend Inc. <http://www.lightbend.com/>

Also, we recommend that source distributions have no binary files, and this
seem to have a gradle related jar bundled together.

I am +0, but most of the items above are issues that may come up when you
reach IPMC, so be prepared to have an answer for them.

On Mon, Jun 25, 2018 at 2:27 PM Vincent S Hou  wrote:

> Hi everyone,
>
> This is to call for a vote for the release of Apache OpenWhisk
> 0.9.0-incubating: main OpenWhisk module.
>
> List of JIRA ticket(s) resolved for this release can be found at
> https://issues.apache.org/jira/browse/INCUBATOR-213.
>
> To learn more about Apache OpenWhisk, please visit
> https://openwhisk.apache.org/.
>
> This  release comprises of source code distribution only. There is one
> module within this release. The artifact was built from  the following Git
> commit ID:
> * openwhisk: 76dadd2, Bump gradle and scoverage version
>
> The source code artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz
>
> The MD5 checksum for each artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.md5
>
> The SHA-512 checksum for each artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.sha512
>
> The signature of this artifact can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.asc
>
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
>
> The documentation can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md
>
> Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.
>
> The vote will be open for at least 72 hours.
> [ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release and the reason
>
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] Source code artifacts have correct names matching the current release.
> [ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
> [ ] All files have license headers if necessary.
> [ ] No compiled archives bundled in source archive.
>
> Thank you very much.
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> Cloud
>
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
> States
>
>

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

Hi Rodric,

I think all the issues can be resolved by updating the instruction of 
installation. 

I can definitely work on that.

Our vote for main OpenWhisk module is effective. After consolidating the result 
and fixing the document, we should proceed with the release.
 
I have tried the local deployment, which turned out to be fine. I have 
documented some known issues in the instruction.



Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Rodric Rabbah  wrote: -
To: dev@openwhisk.apache.org
From: Rodric Rabbah 
Date: 06/29/2018 08:38AM
Subject: [DISCUSS] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk 
module

I am breaking this out into a DISCUSS thread so not to pollute the vote. In
completing this checking list:

[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[x] All files have license headers if necessary. (checked with scan-code)
[x] No compiled archives bundled in source archive (modulo
gradle-wrapper.jar).

I ran into a few hiccups (some duplicates with Bertrand's) for which I
opened the following issues:

https://github.com/apache/incubator-openwhisk-release/issues/207
https://github.com/apache/incubator-openwhisk-release/issues/208
https://github.com/apache/incubator-openwhisk-release/issues/209 (bug)
https://github.com/apache/incubator-openwhisk-release/issues/210
https://github.com/apache/incubator-openwhisk-release/issues/211 (bug)
https://github.com/apache/incubator-openwhisk-release/issues/212
https://github.com/apache/incubator-openwhisk-release/issues/213 (bug,
blocks deployment)
https://github.com/apache/incubator-openwhisk-release/issues/214

Carlos I'm not sure how you deployed successfully and ran hello world. I'd
like to know if this is isolated to me. It looks like both Betrand and I
ran into issues with deployment (beyond the doc bug).

-r

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

This is the key, which is used by the Travis job. The private key is encrypted 
in the repo of incubator-openwhisk-release.

For further releases, what email and use id can we use? Do we have them handy 
somewhere? @Bertrand, do you have suggestions?
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Rodric Rabbah  wrote: -
To: dev@openwhisk.apache.org
From: Rodric Rabbah 
Date: 06/29/2018 08:04AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk 
module

As Bertrand wrote:

gpg: Signature made Mon Jun 25 23:11:21 2018 CEST using RSA key ID 22CC20CC
> gpg: Good signature from "OpenWhisk Release Bot (Release of OpenWhisk)
> " [unknown]
>

The key does not appear to be verified. Further can we not use an @
apache.org email address vs this gmail id (who owns that)?

-r

[VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk module

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 
0.9.0-incubating: main OpenWhisk module.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-213.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This  release comprises of source code distribution only. There is one module 
within this release. The artifact was built from  the following Git commit ID:
* openwhisk: 76dadd2, Bump gradle and scoverage version

The source code artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz

The MD5 checksum for each artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.md5

The SHA-512 checksum for each artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.sha512

The signature of this artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-0.9.0-incubating-sources.tar.gz.asc

KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

The documentation can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md

Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

Thank you very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

[Vincent S Hou]

Bertrand,

For the module main openwhisk to be released for the first time, we do not ship 
the test cases, since there are many packages as the test data, we do not want 
to ship so far. After we configure out how risky they are, we will ship the 
test cases.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Bertrand Delacretaz  wrote: -
To: dev@openwhisk.apache.org
From: Bertrand Delacretaz 
Date: 06/23/2018 05:39AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

Hi Rodric,

On Fri, Jun 22, 2018 at 2:52 PM Rodric Rabbah  wrote:
> > On Jun 22, 2018, at 8:18 AM, Vincent S Hou  wrote:
> > ...I mean if only release this go client code, there is nothing we can run 
> > it against.

> And that is entirely fine per all the ASF docs I’ve read. Is there a 
> requirement that the code must be
> functional in some extended capacity?...

There's no such requirement for a podling release, especially not for
your first Incubator release.

I would expect that the released module has unit tests that pass when
building it, but that module not being usable in isolation is not a
problem, from the Incubator PMC's point of view.

Of course the ultimate goal is for OpenWhisk to release fantastic
software, we're not doing all this just to keep "the system" happy ;-)

But I think "priming the system" as Matt says, by releasing a single
module, will get us there faster and with less effort.

-Bertrand

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

[Vincent S Hou]

Chetan,

That is really good to use Apache Maven Staging repo for our release process in 
future.
So far our release tool is openwhisk-release: 
https://github.com/apache/incubator-openwhisk-release. Either manual or 
automated mode can push the artifacts into
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/.

I was wondering if Maven release can be integrated to current process. Feel 
free to open an issue and draft the plan.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Chetan Mehrotra  wrote: -
To: dev@openwhisk.apache.org
From: Chetan Mehrotra 
Date: 06/25/2018 06:40AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

> Based on all the discussion on a VOTE mail thread, we can go with the
release of one module, which the main openwhisk module, for the initial
Apache release

@Vincent Looking at current released artifacts it appears we are only
releasing source tars. Going forward we should look into including Maven
release of various sub modules in main OpenWhisk repo like
openwhisk-common, openwhisk-controller etc as part of vote. Until vote they
would be present in Apache Maven Staging repo and post vote they would be
publish to global Maven repo. See [1] for reference.

Chetan Mehrotra
[1] http://www.apache.org/dev/publishing-maven-artifacts.html

On Sat, Jun 23, 2018 at 3:09 PM, Bertrand Delacretaz  wrote:

> Hi Rodric,
>
> On Fri, Jun 22, 2018 at 2:52 PM Rodric Rabbah  wrote:
> > > On Jun 22, 2018, at 8:18 AM, Vincent S Hou  wrote:
> > > ...I mean if only release this go client code, there is nothing we can
> run it against.
>
> > And that is entirely fine per all the ASF docs I’ve read. Is there a
> requirement that the code must be
> > functional in some extended capacity?...
>
> There's no such requirement for a podling release, especially not for
> your first Incubator release.
>
> I would expect that the released module has unit tests that pass when
> building it, but that module not being usable in isolation is not a
> problem, from the Incubator PMC's point of view.
>
> Of course the ultimate goal is for OpenWhisk to release fantastic
> software, we're not doing all this just to keep "the system" happy ;-)
>
> But I think "priming the system" as Matt says, by releasing a single
> module, will get us there faster and with less effort.
>
> -Bertrand
>

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

[Vincent S Hou]

Based on all the discussion on a VOTE mail thread, we can go with the release 
of one module, which the main openwhisk module, for the initial Apache release.
I will prepare another VOTE mail separately. Let's close this mail thread, 
unless someone opposes to release main openwhisk.

Thanks.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 06/22/2018 09:39AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

+1

--dave

Carlos Santana ---06/22/2018 09:23:55 AM---I will take Bertrand's mentorship 
advice and release 1 module This is just to go thru the ASF releas

From:Carlos Santana 
To:dev@openwhisk.apache.org
Date:06/22/2018 09:23 AM
Subject:Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating



I will take Bertrand's mentorship advice and release 1 module

This is just to go thru the ASF release process and voting.
To verify that the source code is free from legal problems, and follows all
the legal requirements

We just need to go thru one round with the IPMC and explain that this is
our first practice run to get the go-client 0.9.0 module
Stating that this module is part of a larger suite that will come after

Not required, but if folks want to test something about the code in the
single tgz they can run the go tests (this will compiled and run go unit
tests)

And then follow with the other 12 modules same version 0.9.0 as their
initial version for each module.

Take into account we can separate what we communicate to the outside
OpenWhisk end user community as a downloadable, deployable openwhisk
platform stack.
For example I will hold off a blog post and twitter announcement, until we
have a full suite of modules blessed/released and in the ASF dist download
site, and have a single page on the webstie (openwhisik.apache.org), that
end users that want to download and install the serverless platform stack,
can go there and and be able to download all the modules and deploy them
together, or pick one of the modules if they only need one.

--cs




On Fri, Jun 22, 2018 at 8:52 AM Rodric Rabbah  wrote:

>
> > On Jun 22, 2018, at 8:18 AM, Vincent S Hou  wrote:
> >
> > I mean if only release this go client code, there is nothing we can run
> it against.
>
> And that is entirely fine per all the ASF docs I’ve read. Is there a
> requirement that the code must be functional in some extended capacity?
>
> The ASF docs point out verification steps but none include actually
> running anything from what I’ve learned so far.
>
> I don’t think Bertrand, Rob, or I are saying not to release all 13 but
> rather go through with just 1 repository first end to end.
>
> The Apache motto is release early release often, no?
>
> -r



  

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

[Vincent S Hou]

Hi Ron,

Thanks for the reply. 

Based on the current nature of openwhisk, all the 13 repos/modules are working 
together. If we only release one module, for example, the client go(go sdk) as 
suggested, it is a purely client tool, which needs the openwhisk service 
running, in order to run against. If there is only this client go(go sdk) 
offered to ASF incubator with no other components, how can they verify the 
functionality? If they have no idea whether it works correctly, how could this 
initial go sdk get passed, unless you have a different opinion? This is my 
concern to merely release one for the first time.

All the modules by far need to run as complete platform. We have openwhisk 
offering the service, client go, cli and other tools as the client to access 
them. We need to have different runtimes to make sure openwhisk supports. It is 
like a FIFA World CUP team, which needs 11 players to field in order to play.

To make life easier, I can consolidate all the modules into tar and come up 
with a instruction and scripts to make installation and verification explained. 
Folks can download it only once, read the instructions, run the scripts as 
needed, and bingo. What do you think??
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Rob Allen  wrote: -
To: dev@openwhisk.apache.org
From: Rob Allen 
Date: 06/22/2018 01:46AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

> On 22 Jun 2018, at 05:14, Vincent S Hou  wrote:
> 
> Great thanks to folks with votes and the comments.

Wow, a lot happened on my travel day! 

> As a recap of current replies we have received, we have opened a list of 
> issues to be fixed for OpenWhisk in the coming release or further releases:

I’m happy with items 1-5. As long as the ASF incubator people are happy with a 
release that doesn’t have the org.apache.openwhisk.* package name, it all seems 
fine.

> Regarding how many repositories we are going to release, we decided to 
> continue with the release of 13 repositories, after my discussions with many 
> OpenWhiskers. All the 13 repos by far are great intelligent assets, which 
> have been evolving during the past months or even years. 

FWiW, I strongly disagree with this. Bertrand took a fairly cursory look over 
the first attempt at a release and came up with a laundry list of items to be 
addressed - none of which were related to the operation of the code itself or 
even the build process. 

It’s reasonable to assume that when it goes to the Incubator people, they are 
going to have another list of items to address that are again nothing to do 
with the operation of the code.

It seems to me that it would be much easier and *polite* to get all the way 
through to a release tarball on the Apache servers with a single component 
that’s reasonably easy for the Incubator people to assess and check that we’ve 
got everything right. 

It really doesn’t matter what it is as it’s all about the release process 
details. Rodric suggested wskdeploy or the GoSDK. Either would work really well 
as they are small and easily buildable.

I see no reason why once we successfully get the first tarball onto the Apache 
servers, we can’t start rolling the “big” product (the 13 inter-related 
tarballs) the following day as 0.9.1. If we really want 0.9.0 to be the full 
caboodle, then, we can do the “get-our-ducks-in-row” release of wskdeploy as 
0.8.0.

Regards,

Rob

-- 
(“-ra” just looks wrong!)

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

[Vincent S Hou]

This is pure go source code as the client. If there is no server(openwhisk not 
release or available), how do we test? If there is an openwhisk, we just grab 
it and run it. We need to add the steps as the instructions, but it is based on 
there is an openwhisk service running. I mean if only release this go client 
code, there is nothing we can run it against.

No need to build it, since it is not CLI. We do not need to generate anything.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Rodric Rabbah  wrote: -
To: dev@openwhisk.apache.org
From: Rodric Rabbah 
Date: 06/22/2018 03:40AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

> It’s reasonable to assume that when it goes to the Incubator people, they are 
> going to have another list of items to address that are again nothing to do 
> with the operation of the code.

Quite likely - I’m of the same opinion. So reducing the surface makes sense to 
me. Getting through all the way with a successful first step to release at 
least one of the repos is a sensible strategy given this is a first Apache 
release for the project. 

I looked through https://github.com/apache/incubator-openwhisk-client-go and it 
is the entirely self contained - all go code, no deps on other openwhisk repos.

The readme doesn’t have a built step though   (Or test although there are a 
handful of go tests in the repo).

I also don’t see why we have to use different release numbers. Each of the 
components was broken out to make them independently managed so why couldn’t 
they all eventually be released as 0.9 as part of the overall first 
distributions?

-r

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

[Vincent S Hou]

Great thanks to folks with votes and the comments.

As a recap of current replies we have received, we have opened a list of issues 
to be fixed for OpenWhisk in the coming release or further releases:

1. Add the tutorial for 0.9.0 to build and deploy locally with source code
https://github.com/apache/incubator-openwhisk-release/issues/197, we will 
resolve it for 0.9.0

2. Add the instruction on how to verify the license header for each valid 
source code file
https://github.com/apache/incubator-openwhisk-release/issues/196, we will 
resolve it for 0.9.0

3. Add scripts to make download, unzip and installation of source code easier
https://github.com/apache/incubator-openwhisk-release/issues/198, we will 
resolve it for 0.9.0

4. Add the instruction to the private key and credentials
https://github.com/apache/incubator-openwhisk/issues/3800, we will resolve it 
for 0.9.0

5. Renaming the package from whisk.* into org.apache.openwhisk.* 
https://github.com/apache/incubator-openwhisk/issues/3797 We need to defer it 
for next release, since all the repos depend on the naming convention so far. 
It takes great effort and collaboration, because it affects existing offerings. 

Regarding how many repositories we are going to release, we decided to continue 
with the release of 13 repositories, after my discussions with many 
OpenWhiskers. All the 13 repos by far are great intelligent assets, which have 
been evolving during the past months or even years. They all play important 
roles to make openwhisk complete, and users/contributors are longing to see 
them distributed. Contributors in OpenWhisk have done great work to all of them 
and we are confident with source code, and there will be more openwhisk 
repositories in future, as openwhisk attracts more contributors with good 
ideas. Based on my experiences with cooperating with people from Apache, I also 
believe that Apache members are passionate about technologies and desire to try 
out new projects, by fulfilling their duties with their evaluations and 
feedback.

Except the issues we have above, does anyone have any other concerns we need to 
take into account for the 0.9.0 release? If so, this is the chance to raise it; 
if not, we shall proceed the, after we made the minor fixes to the above listed 
issues.

Thank you.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"Matt Rutkowski"  wrote: -
To: dev@openwhisk.apache.org
From: "Matt Rutkowski" 
Date: 06/21/2018 12:08PM
Cc: "Vincent S Hou" 
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

Hi Bertrand,


>>>> ...Plus a single repo. source is not usable by itself and its build 
dependent
>>>> on the other parts as I mentioned earlier...

>>Right, it if cannot be built that's a problem - but if you say that I
>>suppose there's a build order that must be followed?

>>If that's correct those overall build instructions should be included
>>with the set of release archives.

As required, the main openwhisk README (and supporting) docs include 
instructions on how to build (and tooling that makes it quite easy).  We 
can open an issue to better document suggest manual build order.  Will 
talk to Vincent to see if he has time today as I am leaving soon to return 
Monday.

-mr




From:   Bertrand Delacretaz 
To: dev@openwhisk.apache.org
Date:   06/21/2018 11:00 AM
Subject:Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating



Hi Matt,
On Thu, Jun 21, 2018 at 5:27 PM Matt Rutkowski  
wrote:
> ...Are you saying you believe the Incubator PMC
> will fail us strictly due to having 13 tgz/tar files vs. 1 for a first
> release?...

I don't know (and someone's welcome to ask on the
general@incubator.a.o list to find out), but that looks unusual to me,
and more work for reviewers that might need to unpack 13 archives to
find similar issues in several of them.

That's why I focused on just one archive here, and found a few
interesting things already - the other 12 archives have not been
useful for my initial review.

> ...Are you saying they need to be "eased into the concept" because we 
will
> have 13 (now and more eventually); at some point the board will be 
exposed
> to multiples...

No, it's just a practical question and fairness for the reviewers,
where multiple archives might not say much more than one about the
readiness of OpenWhisk to make Apache Releases.

The ASF Board is not involved with releases, it's just the Incubator
PMC in this case, for a podling.

> ...Plus a single repo. source is not usable by itself and its build 
dependent
> on the other parts as I mentioned earlier...

Right, it if cannot be built that's a problem - b

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

[Vincent S Hou]

Hi Bertrand,

Thank you very much for your comments.

Let me clarify what you mean by one module:
Does it mean we can try to release one of the 13 modules, like openwhisk, or 
openwhisk-cli, or consolidate all the 13 projects into one for release?

* The key can be accessed at 
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS. You missed 
"dev/" in your link.
* So far the header is not verified with RAT. We have a unitiy repo call 
openwhisk-utility(https://github.com/apache/incubator-openwhisk-utilities) to 
scan all the code. RAT has issues, since I have never got it running correctly 
in openwhisk. The Travis build uses this openwhisk-utility to verify the 
headers for every incoming commit.
* RSA private key should have some instructions. We will work on it.
* We do not release binary this time.
* We will look at the .scala code files.
* For README, let me make the build instruction more clear.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Bertrand Delacretaz  wrote: -
To: dev@openwhisk.apache.org
From: Bertrand Delacretaz 
Date: 06/21/2018 07:04AM
Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating

Hi Vincent,

Thanks for your work in preparing this release!

On Wed, Jun 20, 2018 at 11:16 PM Vincent S Hou  wrote:
> ...There are totally 13 OpenWhisk projects within this release

As mentioned earlier I don't think it is a good idea to release
multiple modules in your first Incubator release: if a single module
has a problem the whole release will fail, and it's not convenient for
Incubator PMC reviewers (who might not be very familiar with your
code) to review multiple modules in one go. I'm not sure if the
Incubator PMC would even accept voting on multiple artifacts with a
single vote.

I recommend releasing one module first, to validate the release voting
process and to get feedback that's probably applicable for other
modules as well.

With this in mind I have just looked at
openwhisk-0.9.0-incubating-sources.tar.gz so far, here are my
comments:

1) The digests match.

2) The 22CC20CC key used to sign the release is not available at
https://dist.apache.org/repos/dist/release/incubator/openwhisk/KEYS
(that file doesn't exist) nor at
https://people.apache.org/keys/group/openwhisk.asc

3) I don't find build instructions in the README (which is also at
https://github.com/apache/incubator-openwhisk), for convenience

I'm not very familiar with gradle, tried this:

./gradlew tasks
  doesn't show anything specific to OpenWhisk IIUC

./gradlew tasks --all
  shows many tasks, it's unclear where to start

I usually expect to see clear build instructions in such a release
archive, but maybe I missed something.

4) LICENSE, DISCLAIMER, NOTICE look good to me

5) The .scala code files are in whisk.* packages, that should be
org.apache.openwhisk.* for an Apache project.

6) I suppose you used Apache Rat to validate the license headers, I
don't see instructions on how to run it to make those checks myself.

7) There's an RSA private key in the source archive, if it's for
testing purposes it should be clearly identified as such (ideally
named test- something) to reassure people that it's not problematic to
distribute it (./ansible/roles/nginx/files/openwhisk-server-key.pem).

8) I don't see binary files in the release archive which is good,
except for ./gradle/wrapper/gradle-wrapper.jar which I think is
acceptable - but its digest should be kept track of, maybe in a jira
ticket so people can validate it if they want.

Those are the types of comments that you might get when the Incubator
PMC validates releases, I suppose many of them apply to multiple
projects so it's  easier to start with just one module, fix or clarify
these things and then do the rest.

-Bertrand (with my incubation mentor hat on)

[VOTE] Release Apache OpenWhisk 0.9.0-incubating

[Vincent S Hou]

Hi everyone,

This is to call for a vote for the release of Apache OpenWhisk 0.9.0-incubating.

List of JIRA ticket(s) resolved for this release can be found at 
https://issues.apache.org/jira/browse/INCUBATOR-213.

To learn more about Apache OpenWhisk, please visit 
https://openwhisk.apache.org/.

This release comprises of source code distribution only. There are totally 13 
OpenWhisk projects within this release. The artifacts were built from the 
following Git commit IDs:
* openwhisk: 071d841, Make test-instances of Exec depend on the loaded manifest.
* openwhisk-client-go: 1e50522, Add the DISCLAIMER file for Apache incubator 
project
* openwhisk-cli: 461f94f, add OS and CPU architecture to user agent header
* openwhisk-catalog: 517341d, Add the DISCLAIMER file for Apache incubator 
project
* openwhisk-wskdeploy: 7620ef7, disabling export integration
* openwhisk-apigateway: 2b87366, Fix awk command in init.sh generating 
resolvers.conf file
* openwhisk-deploy-kube: cb9c3f5, Update runtimes for upstream changes.
* openwhisk-runtime-nodejs: 557c4bd, update nodejs 6 & 8 to latest security 
patch
* openwhisk-runtime-java: b20f90e, Add skip_pull_runtimes for Travis CI
* openwhisk-runtime-swift: 06c4972, update travis to push "master" tag to 
Docker on "master" branch merges
* openwhisk-runtime-python: a2098d9, update travis to push "master" tag to 
Docker on "master" branch merges
* openwhisk-runtime-php: b0834a5, Fix travis publish 72
* openwhisk-runtime-docker: 650842a, Add ActionProxyContainer tests

All the source code artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/

Each source code artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/[project
 name]-0.9.0-incubating-sources.tar.gz

The MD5 checksum for each artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/[project
 name]-0.9.0-incubating-sources.tar.gz.md5

The SHA-512 checksum for each artifact can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/[project
 name]-0.9.0-incubating-sources.tar.gz.sha512

KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS


Please vote on releasing this package as Apache OpenWhisk 0.9.0-incubating.

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.9.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Thank you very much.


Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Re: [Release] Preparing the release of OpenWhisk

[Vincent S Hou]

So far, we can formally name the first version incubator-0.9.0 to indicate the 
incubator status as well, and use subversion like rc1, rc2, etc, before moving 
the artifacts to the final release SVN URL.

For incubator-0.9.0-rc1, the package of source code openwhisk in the dev SVN 
URL is named after openwhisk-apigateway-incubator-0.9.0-sources.tar.gz
under the folder of apache-openwhisk-incubator-0.9.0-rc1.

Shall we include the name "incubator" as part of the version name? Or it does 
not sound attractive. 

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-James Thomas  wrote: -
To: dev@openwhisk.apache.org
From: James Thomas 
Date: 06/20/2018 01:17PM
Subject: Re: [Release] Preparing the release of OpenWhisk

0.9 makes sense to me.

Something to think about it - what would constitute a 1.0 release? Whilst
the platform is still evolving rapidly, it has been in production on
multiple providers for over 12 months. What things would we like to tick
off before reaching this stage?

On 20 June 2018 at 17:38, Michele Sciabarra  wrote:

> I agree with 0.9.0
>
> --
>   Michele Sciabarra
>   openwh...@sciabarra.com
>
> On Wed, Jun 20, 2018, at 6:37 PM, Michele Sciabarra wrote:
> > I agree with 0.9.0.
> >
> > --
> >   Michele Sciabarra
> >   mich...@sciabarra.com
> >
> > On Wed, Jun 20, 2018, at 6:31 PM, Rob Allen wrote:
> > > On 20 Jun 2018, at 16:24, Matt Rutkowski  wrote:
> > > >
> > > > Can we go with 0.9.0?
> > > >
> > >
> > > 0.9.0 is fine with me.
> > >
> > > Regards,
> > >
> > > Rob
> > >
>



-- 
Regards,
James Thomas

Re: [Release] Preparing the release of OpenWhisk

[Vincent S Hou]

Dave,

We will release the artifacts for source code only, so there will not be tagged 
docker images. It does not matter what we have tagged the existing images.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-"David P Grove"  wrote: -
To: dev@openwhisk.apache.org
From: "David P Grove" 
Date: 06/20/2018 08:27AM
Subject: Re: [Release] Preparing the release of OpenWhisk



"Vincent S Hou"  wrote on 06/20/2018 06:47:25 AM:
>
> We are currently working on the first release of OpenWhisk. The
> version name is called incubator-1.0.0, and the subversion is
> rc2(rc1 as a pilot, has been existing for while).
>
> There will be 13 openwhisk projected to be released.
> The PR in OpenWhisk release repo contains all the information of the
> hash values of all the repositories: https://
> urldefense.proofpoint.com/v2/url?
>
u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Drelease_pull_190=DwIFaQ=jf_iaSHvJObTbx-

> siA1ZOg=Fe4FicGBU_20P2yihxV-
> apaNSFb6BSj6AlkptSF2gMk=fyO8VqoMt6Yv9Lv7Yf5eUOQgH74eoKPi_3p_WU-
> hZEw=mONyOT6wjdWl4JJQg685CHlwAU469EtEj_c49PytCnI=. The artifacts
> will be generated, when this PR is merged.
>
> If you have any questions or concerns, please chime in with your
comments.
>

This is great!!

I had a procedural question, is part of the release process changing the
various "latest" tags for docker images (openwhisk/invoker, etc) to
"incubator-1.0.0" in the ansible/yaml files that specify docker images to
pull, or is that not needed because this is a source only release and there
will not be matching docker images?

--dave

[Release] Preparing the release of OpenWhisk

[Vincent S Hou]

Hi OpenWhiskers, 

We are currently working on the first release of OpenWhisk. The version name is 
called incubator-1.0.0, and the subversion is rc2(rc1 as a pilot, has been 
existing for while).

There will be 13 openwhisk projected to be released.
The PR in OpenWhisk release repo contains all the information of the hash 
values of all the repositories: 
https://github.com/apache/incubator-openwhisk-release/pull/190. The artifacts 
will be generated, when this PR is merged.

If you have any questions or concerns, please chime in with your comments.

Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

Pick up the project incubator-openwhisk-deploy-kube in our first release in Apache

[Vincent S Hou]

 Hi OpenWhiskers,
 
 Please be advised that we would like to add the project  
incubator-openwhisk-deploy-kube into the list of the first time  OpenWhisk 
release in Apache.
 Based on my conversation with Matt, and other OpenWhisk developers in the 
community, we believe openwhisk-deploy-kube has met all the criteria and 
followed the Apache
 release policy. This project has reached the maturity to be released to our 
OpenWhisk users.
 
 Please feel free to add your comment regarding this decision. Thank you very 
much.
 
 Best wishes.
 Vincent Hou (侯胜博)
 
 Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
 
 Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
 Phone: +1(919)254-7182
 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States 
   

Re: Updates of OpenWhisk Release

[Vincent S Hou]

Hi Bertrand,

The responsibility of the repository incubator-openwhisk-release is to make
sure openwhisk will be released based on Apache release process for
projects, and compliant with Apache requirements. The implementation
follows all the necessary steps in order to release the project, including
but not limited to, packaging the source code with valid notice and
license, signing the artifacts with PGP key, uploading them into the apache
directory for vote, etc. This is a tool facilitating the release manager
from having source code only to having all the artifacts ready online for
vote. When we pass the vote, the artifacts can be moved to the release
folder of apache. If not, we can retrospect to any earlier step to prepare
another set of artifacts proposed to release.

So far, as Carlos said, we are almost ready o release the source code,
except that we need to verify in each repository that there are correct
license headers for source code files.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States



From:   Carlos Santana <csantan...@gmail.com>
To: dev@openwhisk.apache.org
Date:   03/27/2018 12:42 PM
Subject:Re: Updates of OpenWhisk Release



Good progress Vincent
   I reviewed the tutorial with steps for doing the release  and opened an
issue [1] to update the document that there needs to be a second vote on
incubator list, which is the one that would provide the final set of votes
to release.

Bertrand.
>Are those tools ready for the PPMC to start preparing the first
release of a significant OpenWhisk module?

I think we almost ready, Only thing I think there are a set of source files
that are missing the Apache License header.
Other than this I think we should be ready to cut the first RC and start
vote on dev list.

[1]
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Drelease_issues_72=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=QxcCo-Ge42RjHK-kC6S18kf8r0DQKA0Mw5HDwpg7XK8=mIp_-xVzi9uELfc9ydoytMZPw39VHT4olqwSvgk9nuY=



-- Carlos


On Tue, Mar 27, 2018 at 7:16 AM Bertrand Delacretaz
<bdelacre...@apache.org>
wrote:

> Hi,
>
> On Mon, Mar 26, 2018 at 4:40 PM, Vincent S Hou <s...@us.ibm.com> wrote:
> > ...Our tool to manage the release process of OpenWhisk is currently on
> track
> > and open to any tests and comments
>
> As an incubation mentor I'm not necessarily interested in all the
> details of the release tools, but more on the overall release process
> and artifacts.
>
> Are those tools ready for the PPMC to start preparing the first
> release of a significant OpenWhisk module?
>
> If yes I think that's the best way of validating them and the
> understanding of the release process by the PPMC.
>
> The way it works is that a release candidate is voted upon here before
> moving to the Incubator PMC vote which is required to authorize the
> release.
>
> So having imperfect release candidates is not a problem, they can be
> discussed and improved here without bothering the Incubator PMC.
>
> -Bertrand
>

Fw: Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose?

[Vincent S Hou]

Dear OpenWhiskers,

I will bring this question and the current solution to the dev list.

Our Travis build of openwhisk-release, it will import the public key(
https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_pub.gpg
) and the private key(
https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_sec.gpg.enc
), available in openwhisk-release repo. Private key is encrypted.

The public key has already uploaded to the SVN repo as well:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS, so it can
be used to verify the signature of each artifact.

The name of this pair of keys is OpenWhisk Release Bot, and the email I
used is openwhisk-release-...@apache.org. They are used to indicate that
the Travis build is the guy which pushes the release artifacts.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States
- Forwarded by Vincent S Hou/Raleigh/IBM on 03/13/2018 05:17 PM -

From:   "Vincent S Hou" <s...@us.ibm.com>
To: priv...@openwhisk.apache.org
Date:   03/08/2018 11:13 AM
Subject:Does OpenWhisk have general account to generate PGP keys and
update apache SVN repository for automated build purpose?



Dear OpenWhisk mentors,

So far we have been automating the release process of OpenWhisk, and
already created a repository dedicated to it:
https://github.com/apache/incubator-openwhisk-release

We are now able to release the source code artifacts in manual mode and
automated mode, and Travis build is used in the automated mode to sign the
artifacts and push them to the SVN.
We try to avoid using some private accounts to generate the PGP keys and
update the SVN repository.

I am wondering what can be the proper credentials I can use to generate the
PGP keys and access the apache SVN. Do we have a general account for the
build purpose?

Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States

Fw: Does OpenWhisk have general account to generate PGP keys and update apache SVN repository for automated build purpose?

[Vincent S Hou]

Dear OpenWhiskers,

I will bring this question and the current solution to the dev list.

Our Travis build of openwhisk-release, it will import the public key(
https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_pub.gpg
) and the private key(
https://github.com/apache/incubator-openwhisk-release/blob/master/tools/key_sec.gpg.enc
), available in openwhisk-release repo. Private key is encrypted.

The public key has already uploaded to the SVN repo as well:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS, so it can
be used to verify the signature of each artifact.

The name of this pair of keys is OpenWhisk Release Bot, and the email I
used is openwhisk-release-...@apache.org. They are used to indicate that
the Travis build is the guy which pushes the release artifacts.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States
- Forwarded by Vincent S Hou/Raleigh/IBM on 03/13/2018 05:17 PM -

From:   "Vincent S Hou" <s...@us.ibm.com>
To: priv...@openwhisk.apache.org
Date:   03/08/2018 11:13 AM
Subject:Does OpenWhisk have general account to generate PGP keys and
update apache SVN repository for automated build purpose?



Dear OpenWhisk mentors,

So far we have been automating the release process of OpenWhisk, and
already created a repository dedicated to it:
https://github.com/apache/incubator-openwhisk-release

We are now able to release the source code artifacts in manual mode and
automated mode, and Travis build is used in the automated mode to sign the
artifacts and push them to the SVN.
We try to avoid using some private accounts to generate the PGP keys and
update the SVN repository.

I am wondering what can be the proper credentials I can use to generate the
PGP keys and access the apache SVN. Do we have a general account for the
build purpose?

Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States

Does anyone use the tool Apache Tentacles before, to check the LICENSE and NOTICE?

[Vincent S Hou]

Hi OpenWhiskers,

We were trying to use Apache Tentacles(http://creadur.apache.org/tentacles/
) to verify the LICENSE and NOTICE files under OpenWhisk projects, but the
report generated by Apache Tentacles command: "java -ea -jar
apache-tentacles-0.1-SNAPSHOT-jar-with-dependencies.jar
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/openwhisk-incubator-rc1/
"
turned out to be empty. We are sure that all the source code artifacts
under the link contain the LICENSE and NOTICE files.

Does anyone have similar issues before? Is this a bug for Apache Tentacles
or what could be the problems with the artifacts under
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/openwhisk-incubator-rc1/
?

Thank you in advance.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States

Specification being drafted for the OpenWhisk release process in Apache - Re: Using Apache Creadur to audit in the release process

[Vincent S Hou]

Dear OpenWhiskers,

Currently, my team members and I are trying to figure out how we can
release OpenWhisk in Apache in an automated way on a regular basis.
We have created a repo called incubator-openwhisk-release:
https://github.com/apache/incubator-openwhisk-release, targeting to become
a tool to do the release for all openwhisk projects.

From the source code as they are in Github, to the packaged artifacts
available in staging repository to vote on, and to the official release
version.
We are working on the whole process from one end to the other end.

I am drafting some specifications about how to implement as a PR:
https://github.com/apache/incubator-openwhisk-release/pull/15
You can also access it via my fork:
https://github.com/houshengbo/incubator-openwhisk-release/blob/draft-plan/docs/general_spec.md

In general, we will try to use Travis CI as much as possible to do all the
work. Since we are developing scripts for Travis to run, we can run them
locally as well. We opened a couple of issues, as you can see here:
https://github.com/apache/incubator-openwhisk-release/issues, and already
earned some folks' comment on them. Thank you for your care.

We are looking at tools, like Apache Creadur, Apache Tentacles, some
building tools, like gradle, maven, gogradle, etc, to find our how they can
play out to smooth our release process.

Feel free to comment out my PR(
https://github.com/apache/incubator-openwhisk-release/pull/15), or open an
issue at(https://github.com/apache/incubator-openwhisk-release/issues) with
your suggestions and comments for the openwhisk release process. Thank you
very much.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States



From:   Michael Marth <mma...@adobe.com.INVALID>
To: "dev@openwhisk.apache.org" <dev@openwhisk.apache.org>
Date:   01/25/2018 10:43 AM
Subject:Re: Using Apache Creadur to audit in the release process



Hi Daisy,



Tangential question (sorry): is there a wiki or GH page describing the
overall plan for releases? I am especially interested in the Travis part,
but would be great to see the full picture.



Thanks!

Michael







On 25/01/18 15:04, "Ying Chun Guo" <guoyi...@cn.ibm.com> wrote:



Hi, all



As we are setting up the release process, I'm investigating how Apache
Creadur[1] - the auditing tools - can help us in the release process. This
email describes what I found and what I propose. We can discuss together.



First of all, we need to understand audit is very important in a Apache
release process. "every ASF release MUST comply with ASF licensing policy.
This requirement is of utmost importance and an audit SHOULD be performed
before any full release is created.", described by Apache Release Policy
[2]. Apache Creadur is such audit tooling to help us.



Apache Creadur includes three projects:

- Apache Rat audits license headers. It will check if files have Apache
License or not, and generate a report.

- Apache Tentacles helps to audit in bulk components uploaded to a
staging repository. It will check if there is a LICENSE and NOTICE files
under each archived source package and compiled package. A HTML report will
be generated.

- Apache Whisker will generate a correct legal documentation if a
package bundles code under several licenses.



I propose to use:

- Apache Rat to check license headers during the release of the source
package. We can develop a program to auto 'read' the report generated by
Rat. If the report doesn't find any issues, the release can be continued.
Or else, it will be stopped and errors will be returned.

- Apache Tentacles to check if every archived package has a LICENSE and
a NOTICE file. The check need to be done both in the release of the source
package and the release of the compiled package after the artifacts are
uploading to a staging repository. Similar as Rat report, we will develop
program to auto "read" the report and decide whether there are issues.



Apache Whisker is not relevant to us up to now, because we don't have
codes under none Apache licenses. ( Correct me if I'm wrong ). In the
future, we may need it.



Let me know if you have any comments and suggestions to the audit
process and tooling.



Best regards

Daisy Guo



[1]
https://urldefense.proofpoint.com/v2/url?u=http-3A__creadur.apache.org=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=JUb9mfEl9cRtHgYOrMM3A07G5ZTPwjvr9Ok9zPN0spM=8PO1bIlCFxzTwRl134HTfpui88duotT66lYPYdawRcU=


[2]
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_legal_release-2Dpolicy.html-23licensing=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=JUb9mfEl9cRtHgYOrMM3A07G5ZTPwjvr9Ok9zPN0spM=FQulTVxLUmkyW1xsBBatCTdL7GSZJAKJCd2izHOGFso=

Re: Using Apache Creadur to audit in the release process

[Vincent S Hou]

Hi Michael,

I am drafting the specs as much as I can.
you can find it over here:
https://github.com/apache/incubator-openwhisk-release/pull/15
or on my fork:
https://github.com/houshengbo/incubator-openwhisk-release/tree/draft-plan

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States



From:   Michael Marth <mma...@adobe.com.INVALID>
To: "dev@openwhisk.apache.org" <dev@openwhisk.apache.org>
Date:   01/25/2018 10:43 AM
Subject:Re: Using Apache Creadur to audit in the release process



Hi Daisy,



Tangential question (sorry): is there a wiki or GH page describing the
overall plan for releases? I am especially interested in the Travis part,
but would be great to see the full picture.



Thanks!

Michael







On 25/01/18 15:04, "Ying Chun Guo" <guoyi...@cn.ibm.com> wrote:



Hi, all



As we are setting up the release process, I'm investigating how Apache
Creadur[1] - the auditing tools - can help us in the release process. This
email describes what I found and what I propose. We can discuss together.



First of all, we need to understand audit is very important in a Apache
release process. "every ASF release MUST comply with ASF licensing policy.
This requirement is of utmost importance and an audit SHOULD be performed
before any full release is created.", described by Apache Release Policy
[2]. Apache Creadur is such audit tooling to help us.



Apache Creadur includes three projects:

- Apache Rat audits license headers. It will check if files have Apache
License or not, and generate a report.

- Apache Tentacles helps to audit in bulk components uploaded to a
staging repository. It will check if there is a LICENSE and NOTICE files
under each archived source package and compiled package. A HTML report will
be generated.

- Apache Whisker will generate a correct legal documentation if a
package bundles code under several licenses.



I propose to use:

- Apache Rat to check license headers during the release of the source
package. We can develop a program to auto 'read' the report generated by
Rat. If the report doesn't find any issues, the release can be continued.
Or else, it will be stopped and errors will be returned.

- Apache Tentacles to check if every archived package has a LICENSE and
a NOTICE file. The check need to be done both in the release of the source
package and the release of the compiled package after the artifacts are
uploading to a staging repository. Similar as Rat report, we will develop
program to auto "read" the report and decide whether there are issues.



Apache Whisker is not relevant to us up to now, because we don't have
codes under none Apache licenses. ( Correct me if I'm wrong ). In the
future, we may need it.



Let me know if you have any comments and suggestions to the audit
process and tooling.



Best regards

Daisy Guo



[1]
https://urldefense.proofpoint.com/v2/url?u=http-3A__creadur.apache.org=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=JUb9mfEl9cRtHgYOrMM3A07G5ZTPwjvr9Ok9zPN0spM=8PO1bIlCFxzTwRl134HTfpui88duotT66lYPYdawRcU=


[2]
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_legal_release-2Dpolicy.html-23licensing=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=JUb9mfEl9cRtHgYOrMM3A07G5ZTPwjvr9Ok9zPN0spM=FQulTVxLUmkyW1xsBBatCTdL7GSZJAKJCd2izHOGFso=

Re: Committers may need to "accept invite" to Apache.org

[Vincent S Hou]

Thank Matt for reminding all the committers. I have lost the access and
regained it by clicking on the invitation button.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States



From:   "Matt Rutkowski" <mrutk...@us.ibm.com>
To: d...@openwhisk.incubator.apache.org
Date:   12/12/2017 02:50 PM
Subject:Committers may need to "accept invite" to Apache.org



There was a "glitch" this weekend I am told that will cause Committers to
have to accept a new invitation to Apache.org at:
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=LUNmCHjmrhrkjp9ZF9fhwg=t2_4Foy4jAnicG2ZTZ6viykksQlmbKFEhN1TxHc7aGk=uhy5X6b-rDJJ68PJ42yyNh0cjyESGDqJiE5O-nqV2cw=


There should be a notice/button near the top...

otherwise you may find your Committer ACLs not to be working.

Kind regards,
Matt

Request to be added into the dev and commit mail lists

[Vincent S Hou]

Hi everyone in openwhisk community,

My name is Shengbo Hou. Most of the time I go by Vincent Hou. The Apache
account name I applied is houshengbo.
I am working with IBM and the initial contributor to OpenWhisk project.

I actually submitted the ICLA to Apache secretary one month ago on Dec
14th, 2016, but I have not received any response yet. I sent to the
secretary several follow-up mails, but also no answer. I am not sure of my
status with apache. I did not receive any mail from
d...@openwhisk.incubator.apache.org. I hope someone over here can help to
add me into both of the mail lists.

Thank you.

Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenStack Contributor, IaaS and OpenStack
Department, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United
States