Re: release verification help
I believe the shell script tooling can be used for quickly validating the release for votes. We can enhance the web tooling to simplify process for preparing the release which still has some manual aspects. 1. Generate a email from a template with required links 2. Compute the list of commits/issue (or better have a git release link) which describes what all is new from last release. Current release vote mail only lists the sha and legal stuff which is of not much use to end user. So having links to set of issues/PR included in the release would be useful Chetan Mehrotra On Mon, Mar 25, 2019 at 11:10 PM Carlos Santana wrote: > Using the website I would think it doesn’t count as verifying the > artifacts. > > Just playing devils advocate here. > > Going to a website and selecting something from a Dropbox and see green > checks don’t know if the useful for the person doing the voting. Maybe > taking the code from the website or bash scripts and running locally seems > more real. > > - Carlos Santana > @csantanapr > > > On Mar 25, 2019, at 12:18 PM, James Thomas wrote: > > > > If anyone has any feature requests for http://apache.jamesthom.as please > > open issues @ > > https://github.com/jthomas/openwhisk-release-verification/issues > > > > PRs always welcome ;) It is just three (simple) Node.js openwhisk actions > > powering the backend to do the verification. > > > > On Mon, 25 Mar 2019 at 15:05, Chetan Mehrotra > > > wrote: > > > >> Thanks Rodric and James for such tooling. This would greatly reduce the > >> friction in voting for releases. > >> > >> In Apache Sling we have evolved the voting process over the time [1] > which > >> has helped in getting people to vote. > >> > >> Chetan Mehrotra > >> [1] > >> > >> > https://sling.apache.org/documentation/development/release-management.html#starting-the-vote > >> > >> > >>> On Mon, Mar 25, 2019 at 8:19 PM Rodric Rabbah > wrote: > >>> > >>> This email is in response to Chetan raising the following "May be we > >>> automate some of the steps using a shell script similar to > >>> > >>> > >> > https://github.com/apache/sling-tooling-release/blob/master/check_staged_release.sh > >>> " > >>> in one of the recent release vote threads. > >>> > >>> Thanks to James Thomas, we have a web-based verification tool that > >>> automates the release candidate checks so it's much easier now to > verify > >>> and vote on the releases. Source available at > >>> https://github.com/jthomas/openwhisk-release-verification and you can > >> try > >>> it out here http://apache.jamesthom.as/ per comment on Slack earlier > >>> today. > >>> > >>> And I opened a PR to add my bash scripts which I called `rcverify` here > >>> https://github.com/apache/incubator-openwhisk-release/pull/254. This > was > >>> previously a gist which I'll delete if the PR is accepted (see [1] for > >>> reference). > >>> > >>> [1] rcverify gist > >>> https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041 > >>> > >>> -r > >>> > >> > > > > > > -- > > Regards, > > James Thomas >
Re: [DISCUSS] graduation from the incubator
Hi At the beginning I'd like to write I like the job you do with development of OpenWhisk and I like this platform very much. I was talking about it some weeks ago and may people were interested in it. I hope you will be able to graduate soon and become a TLP. I see actually some problems with Slack too. It's a good communication channel, when you want to discuss something quickly. I used it as well to discuss some questions with Rodric. And I liked that Rodric sent a summary of our discussion to @dev. It worked like it really should work when channels other than email are used for discussion. But I see that not all discussions are summarized in dev@. The digests are good for archiving, but it's difficult join a discussion in a specific thread, especially when the thread is old. The messages in Slack are no more visible after some time (e.g. I cannot see today messaged older than 31st January, I see following message "To see and search this channel's full history, upgrade to one of our paid plans") With email threads it's easier to join the discussion for the particular thread or simply reference the thread (e.g. by url of the thread) You have also a huge amount of know-how, tips and tricks and solutions in Github issues and pull requests. They can be easily found when searching for problem solutions in Google. But it would be nice to have it on the mailing list as well. I agree with Matt's and Bertrand's suggestions. I think it will make the participation in this community easier for people who prefer more asynchronous communication via mailing list. When we improve the communication on the dev@ list I see no more big issues on the way to become a TLP. Best regards Krzysztof On 25.03.2019 11:28, Bertrand Delacretaz wrote: Hi, On Tue, Mar 19, 2019 at 7:27 PM Matt Sicker wrote: ...My suggestion as to how to improve this wouldn't be the daily digest. My suggestion would be to ensure any development conversations that take place on Slack should be recreated on the mailing lists... I agree with the intention, but having to "recreate" conversations can be counter-productive, I'd rather say that any "important" conversation needs to move out of Slack into a place which is fully open (as in findable with a Google search), asynchronous and has a persistent URL. Git tickets or pull requests fit the bill for that IMO, but the problem is that they are scattered among multiple Git repositories and it's hard to follow them "from afar" while not missing important things. To me, the essence of "if it didn't happen on the dev list it didn't happen" is being able to follow the project without missing anything important by just subscribing to this list. It doesn't mean everything has to really happen here (which I understand would not be popular) but everything important has to be reflected here, one way or another, so as to raise people's attention. The automated Slack digests are useful for archiving things here but as Matt Sicker says not really usable to quickly skim things. I think the following should help convince the Incubator that this project is ready to graduate as far as Apache-style communications are concerned: a) Guidelines (on http://openwhisk.apache.org/community.html probably) on how to use Slack as opposed to more persistent and async channels. That's basically "anything important needs to be fully open and discoverable from the dev list, with a persistent URL", doesn't need to be complicated but should reassure the Incubator that the project is clear about this. b) Weekly news on this list about what's going on generally and which PRs and tickets one should look at to stay informed. Might be automated or semi-automated but I suppose some redactional content helps. As I suppose the "full-timers" on this project are all on Slack, maybe a bot that collects /news items and sends them once a week would make this easy? -Bertrand -- Krzysztof Sobkowiak JEE & OSS Architect, Integration Architect Apache Software Foundation Member (http://apache.org/) Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/) Apache Incubator PMC Member (https://incubator.apache.org/) Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: release verification help
Using the website I would think it doesn’t count as verifying the artifacts. Just playing devils advocate here. Going to a website and selecting something from a Dropbox and see green checks don’t know if the useful for the person doing the voting. Maybe taking the code from the website or bash scripts and running locally seems more real. - Carlos Santana @csantanapr > On Mar 25, 2019, at 12:18 PM, James Thomas wrote: > > If anyone has any feature requests for http://apache.jamesthom.as please > open issues @ > https://github.com/jthomas/openwhisk-release-verification/issues > > PRs always welcome ;) It is just three (simple) Node.js openwhisk actions > powering the backend to do the verification. > > On Mon, 25 Mar 2019 at 15:05, Chetan Mehrotra > wrote: > >> Thanks Rodric and James for such tooling. This would greatly reduce the >> friction in voting for releases. >> >> In Apache Sling we have evolved the voting process over the time [1] which >> has helped in getting people to vote. >> >> Chetan Mehrotra >> [1] >> >> https://sling.apache.org/documentation/development/release-management.html#starting-the-vote >> >> >>> On Mon, Mar 25, 2019 at 8:19 PM Rodric Rabbah wrote: >>> >>> This email is in response to Chetan raising the following "May be we >>> automate some of the steps using a shell script similar to >>> >>> >> https://github.com/apache/sling-tooling-release/blob/master/check_staged_release.sh >>> " >>> in one of the recent release vote threads. >>> >>> Thanks to James Thomas, we have a web-based verification tool that >>> automates the release candidate checks so it's much easier now to verify >>> and vote on the releases. Source available at >>> https://github.com/jthomas/openwhisk-release-verification and you can >> try >>> it out here http://apache.jamesthom.as/ per comment on Slack earlier >>> today. >>> >>> And I opened a PR to add my bash scripts which I called `rcverify` here >>> https://github.com/apache/incubator-openwhisk-release/pull/254. This was >>> previously a gist which I'll delete if the PR is accepted (see [1] for >>> reference). >>> >>> [1] rcverify gist >>> https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041 >>> >>> -r >>> >> > > > -- > Regards, > James Thomas
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 http://www.apache.org/licenses/LICENSE-2.0.txt 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://github.com/apache/incubator-openwhisk-wskdeploy/blob/master/LICENSE.txt and https://github.com/apache/incubator-openwhisk-devtools/blob/master/LICENSE.txt Can someone with more experience in this provide guidance on which is correct? -- Regards, James Thomas
Re: release verification help
If anyone has any feature requests for http://apache.jamesthom.as please open issues @ https://github.com/jthomas/openwhisk-release-verification/issues PRs always welcome ;) It is just three (simple) Node.js openwhisk actions powering the backend to do the verification. On Mon, 25 Mar 2019 at 15:05, Chetan Mehrotra wrote: > Thanks Rodric and James for such tooling. This would greatly reduce the > friction in voting for releases. > > In Apache Sling we have evolved the voting process over the time [1] which > has helped in getting people to vote. > > Chetan Mehrotra > [1] > > https://sling.apache.org/documentation/development/release-management.html#starting-the-vote > > > On Mon, Mar 25, 2019 at 8:19 PM Rodric Rabbah wrote: > > > This email is in response to Chetan raising the following "May be we > > automate some of the steps using a shell script similar to > > > > > https://github.com/apache/sling-tooling-release/blob/master/check_staged_release.sh > > " > > in one of the recent release vote threads. > > > > Thanks to James Thomas, we have a web-based verification tool that > > automates the release candidate checks so it's much easier now to verify > > and vote on the releases. Source available at > > https://github.com/jthomas/openwhisk-release-verification and you can > try > > it out here http://apache.jamesthom.as/ per comment on Slack earlier > > today. > > > > And I opened a PR to add my bash scripts which I called `rcverify` here > > https://github.com/apache/incubator-openwhisk-release/pull/254. This was > > previously a gist which I'll delete if the PR is accepted (see [1] for > > reference). > > > > [1] rcverify gist > > https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041 > > > > -r > > > -- Regards, James Thomas
Re: [VOTE] Release Apache OpenWhisk CLI (incubating) version 0.10.0
The voting is closed; the vote has passed with 3 +1 binding votes from IPMC Members in addition to the 6 +1 votes from OpenWhisk PPMC members on the podling voting thread. Bertrand Delacretaz voted +1 on this thread. Matt Sicker and Krzysztof Sobkowiak voted +1 on the podling release vote thread referenced below. Thanks to all who participated in the vote. The OpenWhisk podling will proceed with publishing and announcing the release of Apache OpenWhisk CLI (incubating) version 0.10.0 regards, --dave On 2019/03/20 15:28:29, "David P Grove" wrote: > > > The Apache OpenWhisk community has voted to release Apache OpenWhisk CLI > (incubating) version 0.10.0. The voting thread can be found here: > https://lists.apache.org/thread.html/78028145da802baa3dc37e53094443550e3f5d8d66486e00d6c28406@%3Cdev.openwhisk.apache.org%3E > > One binding +1 vote from mentor Matt Sicker carries over from the dev list > thread; at least two more +1 votes are needed. > > We request that IPMC Members please review and vote on this incubator > release. > > 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://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz > sha512 checksum: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz.sha512 > signature: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz.asc > > openwhisk-client-go (068DBC87 533905DB D0089CAE 74FD0B91 109992D8 D843CAA4 > 01EA87B6 9CDC9550 6D555655 4679FF36 7A52414E DCC59126 E558085D 3E960DEB > 18804581 6B2FA019) > src.tar.gz: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz > sha512 checksum: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz.sha512 > signature: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz.asc > > openwhisk-wskdeploy (412B1E09 129F2884 A1D4E9DE 0A979B47 55A54FC5 61E1D328 > 325E8A12 AE504779 A2350B9F 4185582F 7782EEA5 AE9018CD 52E4AA4C 484B5211 > AA449B4B 9F9E2432) > src.tar.gz: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz > sha512 checksum: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz.sha512 > signature: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz.asc > > All release artifacts were signed with key 72AF0CC22C4CF320. > KEYS file is available here: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS > > How to verify the artifacts can be found at: > https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the > +release+checklist+and+vote+on+OpenWhisk+modules+under+Apache > > Please vote on releasing the three components of Apache OpenWhisk CLI > 0.10.0-incubating as described above. > > The vote will be open for at least 72 hours. > [ ] +1 Release as Apache OpenWhisk 0.10.0-incubating: openwhisk-cli, > openwhisk-client-go, openwhisk-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 repository. > [ ] All files have license headers if necessary. > [ ] No compiled archives bundled in source archive. > > regards, > > --dave >
Re: release verification help
Thanks Rodric and James for such tooling. This would greatly reduce the friction in voting for releases. In Apache Sling we have evolved the voting process over the time [1] which has helped in getting people to vote. Chetan Mehrotra [1] https://sling.apache.org/documentation/development/release-management.html#starting-the-vote On Mon, Mar 25, 2019 at 8:19 PM Rodric Rabbah wrote: > This email is in response to Chetan raising the following "May be we > automate some of the steps using a shell script similar to > > https://github.com/apache/sling-tooling-release/blob/master/check_staged_release.sh > " > in one of the recent release vote threads. > > Thanks to James Thomas, we have a web-based verification tool that > automates the release candidate checks so it's much easier now to verify > and vote on the releases. Source available at > https://github.com/jthomas/openwhisk-release-verification and you can try > it out here http://apache.jamesthom.as/ per comment on Slack earlier > today. > > And I opened a PR to add my bash scripts which I called `rcverify` here > https://github.com/apache/incubator-openwhisk-release/pull/254. This was > previously a gist which I'll delete if the PR is accepted (see [1] for > reference). > > [1] rcverify gist > https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041 > > -r >
release verification help
This email is in response to Chetan raising the following "May be we automate some of the steps using a shell script similar to https://github.com/apache/sling-tooling-release/blob/master/check_staged_release.sh; in one of the recent release vote threads. Thanks to James Thomas, we have a web-based verification tool that automates the release candidate checks so it's much easier now to verify and vote on the releases. Source available at https://github.com/jthomas/openwhisk-release-verification and you can try it out here http://apache.jamesthom.as/ per comment on Slack earlier today. And I opened a PR to add my bash scripts which I called `rcverify` here https://github.com/apache/incubator-openwhisk-release/pull/254. This was previously a gist which I'll delete if the PR is accepted (see [1] for reference). [1] rcverify gist https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041 -r
Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)
+1 Release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0-incubating [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. May be we automate some of the steps using a shell script similar to [1] Chetan Mehrotra [1] https://github.com/apache/sling-tooling-release/blob/master/check_staged_release.sh On Sat, Mar 23, 2019 at 2:44 AM David P Grove wrote: > > > This is a call to vote on releasing version 2.0.0-incubating of Apache > OpenWhisk Package Alarm, Package Cloudant, and Package Kafka. This is the > first Apache release of these OpenWhisk components. > > These three Apache OpenWhisk packages provide basic event-based programming > capabilities to an OpenWhisk deployment. > > This release comprises of source code distribution only. There are three > components (git repos) included in this release of the OpenWhisk Packages > Group. All release artifacts were built by PR#251 in the openwhisk-release > repo from the following Git commit IDs: > * openwhisk-package-alarms: dd6ab4d81c8893436e7242170d57951c089d5185 > * openwhisk-package-cloudant: ce5dac9cb0204fb2f78195d9e3f9364236613a31 > * openwhisk-package-kafka: 49820dd24170f24a37c02fae6ba7ec06e190423f > > openwhisk-package-alarms (C158D76 B5D9A53A AC10AC42 4CD5060C 7A6467D5 > E9624519 117E9C8C AB171590 CCC3505D 5C7E630D C41769B4 44F85F03 BBA40A6A > E04D2264 79FFA78B B3C5BFB8) > src.tar.gz: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz > sha512 checksum: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz > .sha512 > signature: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz > .asc > > openwhisk-package-cloudant (380E1BA8 EC3C72A8 09B10DCF 03BC1D2D 4BFA7E4F > 892995EE 39D26BBE 758AFD5D FA680E81 54A9C726 A0D386C5 B447C947 70D26385 > 2A8D07BF 5848318A 42A3BBDD) > src.tar.gz: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz > sha512 checksum: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz > .sha512 > signature: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz > .asc > > openwhisk-package-kafka (303B8286 AA9B945D 1A740FCB 0DE908D5 A287FAF5 > C20A9DF9 4BBD2F16 C488DF4B 3E82A75B 9D071B1A E1CCDB54 7B623A36 5AC88E5D > 9994539B 00ECEA5D A066D156) > src.tar.gz: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz > sha512 checksum: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz > .sha512 > signature: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz > .asc > > All release artifacts were signed with key 72AF0CC22C4CF320. > KEYS file is available here: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS > > How to verify the artifacts can be found at: > https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the > +release+checklist+and+vote+on+OpenWhisk+modules+under+Apache > > Please vote on releasing version 2.0.0-incubating of Apache OpenWhisk > Package Alarm, Package Cloudant, and Package Kafka as described above. > > The vote will be open for at least 72 hours. > [ ] +1 Release Apache OpenWhisk Package Alarm, Package Cloudant, and > Package Kafka 2.0.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. > [ ] 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. > > regards, > > --dave >
Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)
+1 for all three. > rcverify.sh openwhisk-package-alarms 'OpenWhisk Package Alarms' 2.0.0 rc2 working in the following directory: /var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.ZajqkKjc fetching openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz fetching openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz.asc fetching openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz.sha512 fetching release keys import keys gpg: key 72AF0CC22C4CF320: "Vincent Hou (Release manager of OpenWhisk) < houshen...@apache.org>" not changed gpg: key 22907064147F886E: "Dave Grove " not changed gpg: Total number processed: 2 gpg: unchanged: 2 unpacking tar ball cloning scancode Cloning into 'incubator-openwhisk-utilities'... remote: Enumerating objects: 52, done. remote: Counting objects: 100% (52/52), done. remote: Compressing objects: 100% (35/35), done. remote: Total 52 (delta 23), reused 34 (delta 15), pack-reused 0 Unpacking objects: 100% (52/52), done. computing sha512 and validating... passed verifying asc... passed verifying disclaimer... passed verifing notice... passed verifying license... passed verifying sources have proper headers... passed scanning for binaries... failed (/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.ZajqkKjc/incubator-openwhisk-package-alarms-2.0.0-incubating/package.json) scanning for archives... passed scanning for packages... passed > rcverify.sh openwhisk-package-kafka 'OpenWhisk Package Kafka' 2.0.0 rc2 working in the following directory: /var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.zTgeICHZ fetching openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz fetching openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz.asc fetching openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz.sha512 fetching release keys import keys gpg: key 72AF0CC22C4CF320: "Vincent Hou (Release manager of OpenWhisk) < houshen...@apache.org>" not changed gpg: key 22907064147F886E: "Dave Grove " not changed gpg: Total number processed: 2 gpg: unchanged: 2 unpacking tar ball cloning scancode Cloning into 'incubator-openwhisk-utilities'... remote: Enumerating objects: 52, done. remote: Counting objects: 100% (52/52), done. remote: Compressing objects: 100% (35/35), done. remote: Total 52 (delta 23), reused 34 (delta 15), pack-reused 0 Unpacking objects: 100% (52/52), done. computing sha512 and validating... passed verifying asc... passed verifying disclaimer... passed verifing notice... passed verifying license... passed verifying sources have proper headers... passed scanning for binaries... passed scanning for archives... passed scanning for packages... passed > rcverify.sh openwhisk-package-cloudant 'OpenWhisk Package Cloudant' 2.0.0 rc2 working in the following directory: /var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.tWXoOujD fetching openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz fetching openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz.asc fetching openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz.sha512 fetching release keys import keys gpg: key 72AF0CC22C4CF320: "Vincent Hou (Release manager of OpenWhisk) < houshen...@apache.org>" not changed gpg: key 22907064147F886E: "Dave Grove " not changed gpg: Total number processed: 2 gpg: unchanged: 2 unpacking tar ball cloning scancode Cloning into 'incubator-openwhisk-utilities'... remote: Enumerating objects: 52, done. remote: Counting objects: 100% (52/52), done. remote: Compressing objects: 100% (35/35), done. remote: Total 52 (delta 23), reused 34 (delta 15), pack-reused 0 Unpacking objects: 100% (52/52), done. computing sha512 and validating... passed verifying asc... passed verifying disclaimer... passed verifing notice... passed verifying license... passed verifying sources have proper headers... passed scanning for binaries... passed scanning for archives... passed scanning for packages... passed On Fri, Mar 22, 2019 at 5:14 PM David P Grove wrote: > > > This is a call to vote on releasing version 2.0.0-incubating of Apache > OpenWhisk Package Alarm, Package Cloudant, and Package Kafka. This is the > first Apache release of these OpenWhisk components. > > These three Apache OpenWhisk packages provide basic event-based programming > capabilities to an OpenWhisk deployment. > > This release comprises of source code distribution only. There are three > components (git repos) included in this release of the OpenWhisk Packages > Group. All release artifacts were built by PR#251 in the openwhisk-release > repo from the following Git commit IDs: > * openwhisk-package-alarms: dd6ab4d81c8893436e7242170d57951c089d5185 > * openwhisk-package-cloudant: ce5dac9cb0204fb2f78195d9e3f9364236613a31 > * openwhisk-package-kafka: 49820dd24170f24a37c02fae6ba7ec06e190423f > > openwhisk-package-alarms (C158D76 B5D9A53A AC10AC42 4CD5060C 7A6467D5 > E9624519 117E9C8C AB171590 CCC3505D 5C7E630D C41769B4 44F85F03 BBA40A6A > E04D2264 79FFA78B B3C5BFB8) >
Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)
James Thomas wrote on 03/25/2019 07:53:18 AM: > > One small issue... the LICENSE.txt files in all the repos have the > boilerplate text still included at the bottom of the files. > > APPENDIX: How to apply the Apache License to your work. > > To apply the Apache License to your work, attach the following > boilerplate notice, with the fields enclosed by brackets "[]" > replaced with your own identifying information. (Don't include > the brackets!) The text should be enclosed in the appropriate > comment syntax for the file format. We also recommend that a > file or class name and description of purpose be included on the > same "printed page" as the copyright notice for easier > identification within third-party archives. > >Copyright [] [name of copyright owner] > > This is correct. Per the Apache release process all releases must contain a full copy of the Apache license which is exactly http://www.apache.org/licenses/LICENSE-2.0.txt --dave
Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)
+1 Release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0-incubating 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. One small issue... the LICENSE.txt files in all the repos have the boilerplate text still included at the bottom of the files. APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [] [name of copyright owner] On Fri, 22 Mar 2019 at 21:14, David P Grove wrote: > > > This is a call to vote on releasing version 2.0.0-incubating of Apache > OpenWhisk Package Alarm, Package Cloudant, and Package Kafka. This is the > first Apache release of these OpenWhisk components. > > These three Apache OpenWhisk packages provide basic event-based programming > capabilities to an OpenWhisk deployment. > > This release comprises of source code distribution only. There are three > components (git repos) included in this release of the OpenWhisk Packages > Group. All release artifacts were built by PR#251 in the openwhisk-release > repo from the following Git commit IDs: > * openwhisk-package-alarms: dd6ab4d81c8893436e7242170d57951c089d5185 > * openwhisk-package-cloudant: ce5dac9cb0204fb2f78195d9e3f9364236613a31 > * openwhisk-package-kafka: 49820dd24170f24a37c02fae6ba7ec06e190423f > > openwhisk-package-alarms (C158D76 B5D9A53A AC10AC42 4CD5060C 7A6467D5 > E9624519 117E9C8C AB171590 CCC3505D 5C7E630D C41769B4 44F85F03 BBA40A6A > E04D2264 79FFA78B B3C5BFB8) > src.tar.gz: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz > sha512 checksum: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz > .sha512 > signature: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz > .asc > > openwhisk-package-cloudant (380E1BA8 EC3C72A8 09B10DCF 03BC1D2D 4BFA7E4F > 892995EE 39D26BBE 758AFD5D FA680E81 54A9C726 A0D386C5 B447C947 70D26385 > 2A8D07BF 5848318A 42A3BBDD) > src.tar.gz: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz > sha512 checksum: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz > .sha512 > signature: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz > .asc > > openwhisk-package-kafka (303B8286 AA9B945D 1A740FCB 0DE908D5 A287FAF5 > C20A9DF9 4BBD2F16 C488DF4B 3E82A75B 9D071B1A E1CCDB54 7B623A36 5AC88E5D > 9994539B 00ECEA5D A066D156) > src.tar.gz: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz > sha512 checksum: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz > .sha512 > signature: > > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz > .asc > > All release artifacts were signed with key 72AF0CC22C4CF320. > KEYS file is available here: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS > > How to verify the artifacts can be found at: > https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the > +release+checklist+and+vote+on+OpenWhisk+modules+under+Apache > > Please vote on releasing version 2.0.0-incubating of Apache OpenWhisk > Package Alarm, Package Cloudant, and Package Kafka as described above. > > The vote will be open for at least 72 hours. > [ ] +1 Release Apache OpenWhisk Package Alarm, Package Cloudant, and > Package Kafka 2.0.0-incubating > [ ] +0 no opinion > [ ] -1 Do not release and
The Rust runtime is almost ready
Hello, to let people know what happened in Slack, yesterday Roberto Diaz with a little help from my side, completed the mandatory tests for the Rust runtime (ActionLoop based ...). So it is basically... ready. We need to setup the travis pipeline, integrate in the list of available runtimes...and write some docs :) -- Michele Sciabarra mich...@sciabarra.com
Re: [DISCUSS] graduation from the incubator
Hi, On Tue, Mar 19, 2019 at 7:27 PM Matt Sicker wrote: > ...My suggestion as to how to improve this wouldn't be the daily digest. > My suggestion would be to ensure any development conversations that > take place on Slack should be recreated on the mailing lists... I agree with the intention, but having to "recreate" conversations can be counter-productive, I'd rather say that any "important" conversation needs to move out of Slack into a place which is fully open (as in findable with a Google search), asynchronous and has a persistent URL. Git tickets or pull requests fit the bill for that IMO, but the problem is that they are scattered among multiple Git repositories and it's hard to follow them "from afar" while not missing important things. To me, the essence of "if it didn't happen on the dev list it didn't happen" is being able to follow the project without missing anything important by just subscribing to this list. It doesn't mean everything has to really happen here (which I understand would not be popular) but everything important has to be reflected here, one way or another, so as to raise people's attention. The automated Slack digests are useful for archiving things here but as Matt Sicker says not really usable to quickly skim things. I think the following should help convince the Incubator that this project is ready to graduate as far as Apache-style communications are concerned: a) Guidelines (on http://openwhisk.apache.org/community.html probably) on how to use Slack as opposed to more persistent and async channels. That's basically "anything important needs to be fully open and discoverable from the dev list, with a persistent URL", doesn't need to be complicated but should reassure the Incubator that the project is clear about this. b) Weekly news on this list about what's going on generally and which PRs and tickets one should look at to stay informed. Might be automated or semi-automated but I suppose some redactional content helps. As I suppose the "full-timers" on this project are all on Slack, maybe a bot that collects /news items and sends them once a week would make this easy? -Bertrand
Re: Added a "Security" page to website with simple, OW-specific instructions for vuln. reporting
On Fri, Mar 22, 2019 at 3:37 PM Matt Rutkowski wrote: > ...Changed it yesterday to use the gen. ASF security email ... Thanks! https://openwhisk.apache.org/security.html and https://openwhisk.apache.org/ includes a "security" link at the bottom which is good. -Bertrand
[slack-digest] [2019-03-24] #general
2019-03-24 11:06:22 UTC - Matthias Riml: If I invoke an action as blocking, then after 60s i will get the activationID of that action, because it's not finished yet. Can I increase the limit of the blocking timeout? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553425582383400?thread_ts=1553425582.383400=C3TPCAQG1 2019-03-24 12:41:24 UTC - Rodric Rabbah: from the cli use -t N where N is in milliseconds +1 : Dominic Kim https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553431284384000?thread_ts=1553425582.383400=C3TPCAQG1 2019-03-24 14:35:54 UTC - Carlos Santana: Using the CLI you can increase the timeout but not the 60 blocking or webaction invoke https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553438154385100?thread_ts=1553425582.383400=C3TPCAQG1 2019-03-24 14:36:58 UTC - Carlos Santana: Well you can on your own deployment changing the values in the nginx I think is set to 70s and then in the controller increase from 60 on the time that the connection between client and controller is kept alive. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553438218387200?thread_ts=1553425582.383400=C3TPCAQG1
[slack-digest] [2019-03-24] #random
2019-03-24 08:12:15 UTC - Michele Sciabarra: I did a simple thing: I extracted
the test from the source and I tried to invoke it
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553415135311600
2019-03-24 08:12:22 UTC - Michele Sciabarra: it works:
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553415142311800
2019-03-24 08:12:47 UTC - Michele Sciabarra: ```
$ invoke run '{"delimiter": "❄"}'
{"winter":"❄ ☃ ❄"}
```
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553415167312100
2019-03-24 08:12:59 UTC - Michele Sciabarra: however I see there are 2
newlines...
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553415179312500
2019-03-24 08:15:36 UTC - Michele Sciabarra: however there is something odd in
the handling of the encoding
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553415336313000
2019-03-24 08:15:53 UTC - Michele Sciabarra: if I deploy the
I see this:
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553415353313400
2019-03-24 08:16:03 UTC - Michele Sciabarra: ```
$ invoke run '{"delimiter": "❄"}'
{"delimiter":"�"}
```
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553415363313700
2019-03-24 08:19:13 UTC - Michele Sciabarra: I think the problem it receives
the snowflake wrong
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553415553314300
2019-03-24 10:08:48 UTC - Roberto Diaz: it is curious
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553422128314600
2019-03-24 10:09:40 UTC - Michele Sciabarra: I think I found the core problem
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553422180315300
2019-03-24 10:10:32 UTC - Roberto Diaz: it could be the 2 newlines and for that
reason in scala it tries to assert against ""
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553422232315500
2019-03-24 10:13:28 UTC - Michele Sciabarra: they are actually 2... or maybe 3
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553422408315900
2019-03-24 10:13:47 UTC - Michele Sciabarra: first, in the test you have to
output something in the log
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553422427316400
2019-03-24 10:14:18 UTC - Michele Sciabarra: second, in the image the default
encoding is not UTF-8
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553422458317000
2019-03-24 10:15:00 UTC - Michele Sciabarra: it has nothing to do with scala
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553422500317400
2019-03-24 10:20:17 UTC - Michele Sciabarra: for the first problem I fixed the
source code
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553422817317800
2019-03-24 10:29:07 UTC - Michele Sciabarra: Here you go!
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553423347318000
2019-03-24 10:30:39 UTC - Michele Sciabarra: fix number one: add this to the
Dockerfile
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553423439318500
2019-03-24 10:30:49 UTC - Michele Sciabarra: ENV PYTHONIOENCODING=utf8
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553423449318700
2019-03-24 10:31:12 UTC - Michele Sciabarra: fix number 2: add a log command to
the example (and leave the snowman in unicode):
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553423472319300
2019-03-24 10:31:50 UTC - Michele Sciabarra: ```
override val testUnicode =
TestConfig(
raw"""|extern crate serde_json;
|use serde_derive::{Deserialize, Serialize};
|use serde_json::{Error, Value};
|#[derive(Debug, Clone, PartialEq, Serialize, Deserialize)]
|struct Input {
|delimiter: String,
|}
|#[derive(Debug, Clone, PartialEq, Serialize, Deserialize)]
|struct Output {
|winter: String,
|}
|pub fn main(args: Value) - ResultValue, Error {
|let input: Input = serde_json::from_value(args)?;
|let msg = format!("{} {} {}",
input.delimiter,'☃',input.delimiter);
|println!("{}", msg);
|let output = Output {
|winter: msg,
| };
| serde_json::to_value(output)
|}
""".stripMargin)
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553423510319600
2019-03-24 10:36:57 UTC - Roberto Diaz: Awesome Thanks!! :tada: :tada:
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p155342381732
2019-03-24 10:37:18 UTC - Michele Sciabarra: submit your changes so I can test
and approve the PR
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553423838320300
2019-03-24 10:46:45 UTC - Roberto Diaz: submitted
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1553424405320900
2019-03-24 10:47:05 UTC - Roberto Diaz: one question where is the scancode.sh
script?
