I'm +1 for all the three.
I used the rc verification script to verify all three.
I found some minor nits with the wskdeploy artifact for which I opened
https://github.com/apache/incubator-openwhisk-wskdeploy/issues/1044.
> rcverify.sh openwhisk-wskdeploy 'OpenWhisk Wskdeploy' 0.10.0
computing
Another minor point, the NOTICE refers to "Apache OpenWhisk" not the
'OpenWhisk JavaScript Client Library'.
-r
On Tue, Mar 19, 2019 at 4:50 PM Rodric Rabbah wrote:
> +1
>
> I wrote a script to verify this release. The gist is here
>
+1
I wrote a script to verify this release. The gist is here
https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041
You'll see sample output at the bottom. It detected the same issue raised
by Matt wrt the license, otherwise everything checked out.
computing sha512 and validating...
+1
Notes:
* LICENSE has incorrect boilerplate example at bottom. It seems to
have been replaced with a concrete example of IBM. This should
probably be reverted to the original text of the ASLv2.
* NPM says there are a few vulnerable dependencies. Neat feature,
though unclear if they're real
Oh, and if you all figure out a way to easily digest the notification
info for dev@, that would be really cool, though I wouldn't consider
it necessary for graduation. Other ASF projects I've either worked
with or observed will all have their own spammy notification email for
archiving all the
Matt Sicker wrote on 03/19/2019 02:09:36 PM:
>
> * I haven't really combed through literally every file to ensure
> license headers and notice are correct, though I'm assuming this has
> been kept up to date so far. If that's not the case, then I'll have to
> dig through these releases in more
So I have some agreements with Bertrand here. I obviously don't work
on this project full time (my full time work is involved in developing
Jenkins), and the Slack digests, while useful, are nearly impossible
to read whenever a large amount of discussion happens during a day,
particularly because
+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
I'd like to show my new web action http proxy - it'll only take 5 - 10 mins.
On Tue, 19 Mar 2019 at 17:26, Priti Desai wrote:
> Hi Dragos,
>
> Please reserve 10 to 15 minutes for Knative buiid.
>
> Cheers
> Priti
>
>
>
> From: Dascalita Dragos
> To: dev@openwhisk.apache.org
> Date:
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
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://zoom.us/my/asfopenwhisk
- Wednesday March 20th
11AM EST(Eastern US)
5PM CET (Central Europe),
4PM
Thanks Dave for raising graduation as a topic.
To be clear... +1 (with stars) from me on moving to graduate...
It is my belief that this project has reached a maturity level, with credits to
its devoted community, over the last 2 plus years to graduate. It has been no
small task to bring
> On 19 Mar 2019, at 15:21, David P Grove wrote:
>
> Bertrand Delacretaz wrote on 03/19/2019 11:01:30
> AM:
>
>>
>> Send a summary here, as a single message, with links, of which tickets
>> and pull requests are being actively worked on, aggregating all
>> OpenWhisk repositories. Based on
Bertrand Delacretaz wrote on 03/19/2019 11:01:30
AM:
> From: Bertrand Delacretaz
> To: OpenWhisk Dev
> Date: 03/19/2019 11:04 AM
> Subject: Re: [DISCUSS] graduation from the incubator
>
> Hi,
>
> On Tue, Mar 19, 2019 at 3:57 PM Rodric Rabbah wrote:
> > On Tue, Mar 19, 2019 at 10:41 AM
On Tue, Mar 19, 2019 at 11:01 AM Bertrand Delacretaz
wrote:
> Send a summary here, as a single message, with links, of which tickets
> and pull requests are being actively worked on, aggregating all
> OpenWhisk repositories. Based on activity stats (assuming the GitHub
> API provides them) as
> On 19 Mar 2019, at 14:50, David P Grove wrote:
>
> Bertrand Delacretaz wrote on 03/19/2019 10:40:51
> AM:
>
>> From: Bertrand Delacretaz
>>
>> On Tue, Mar 19, 2019 at 3:34 PM Rob Allen wrote:
>>> ...The activity on the GitHub PRs and issues is, I suspect,
>> overlooked as one of the
On Tue, Mar 19, 2019 at 10:41 AM Bertrand Delacretaz
wrote:
> Maybe running a query on all repositories for items with recent
> activity or with a specific label and sending the results here would
> help expose that?
>
Do you mean as a one off?
The stats per repository are available on github
Bertrand Delacretaz wrote on 03/19/2019 10:40:51
AM:
> From: Bertrand Delacretaz
> To: OpenWhisk Dev
> Date: 03/19/2019 10:41 AM
> Subject: Re: [DISCUSS] graduation from the incubator
>
> On Tue, Mar 19, 2019 at 3:34 PM Rob Allen wrote:
> > ...The activity on the GitHub PRs and issues is, I
Thank you Bertrand for the input.
With respect to Slack and how this project uses it, I think I can make the
case that it fits the criteria you quoted from Mark Thomas.
> ...The criteria that the ASF looks for in communication channels used by
projects are (in no particular order):
> - open to
>With my incubation mentor hat on, I think the role of the project's
>communications channels needs to be clarified before graduating. It is
>easy to get the impression that the vast majority of the project's
>business happens on Slack - maybe it's not really the case but I think
>having
+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
+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
+1.
Make it happen!
Am Di., 19. März 2019 um 07:02 Uhr schrieb Michele Sciabarra <
mich...@sciabarra.com>:
> Actually it looks to me pretty unusual that a project of this size has not
> yet graduated.
>
> --
> Michele Sciabarra
> mich...@sciabarra.com
>
>
>
> - Original message -
>
2019-03-18 14:05:50 UTC - Michele Sciabarra: I do not see the image
openwhisk/actionloop-v2 but the change has been merged and it is in the
official repo
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1552917950313300
2019-03-18 14:06:00 UTC - Michele Sciabarra: any reason because it
Actually it looks to me pretty unusual that a project of this size has not yet
graduated.
--
Michele Sciabarra
mich...@sciabarra.com
- Original message -
From: David P Grove
To: OpenWhisk Dev
Subject: [DISCUSS] graduation from the incubator
Date: Friday, March 15, 2019 11:06 PM
25 matches
Mail list logo
