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/iss
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 wi
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 ba
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 Som
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:
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 threa
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-
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-bas
+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 fi
+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-
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
+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 f
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.
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, bu
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
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=1
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/archiv
17 matches
Mail list logo
