Justin, thanks for voting and for your suggestions for enhancements to
OpenWhisk's rcverify script for improved transparency.
This vote is now closed. It has passed with 3 binding +1 votes from Justin
Mclean, Matt Sicker, and Bertrand Delacretaz. There were no other votes.
We will proceed wit
I read through the source of rcverify before voting. Looks sufficient to
cover the release checks.
On Fri, Apr 26, 2019 at 18:48, Justin Mclean
wrote:
> Hi,
>
> +1 (binding)
>
> I checked:
> - Incubating in name
> - signatures and hash file fine
> - DISCLAIMER exists
> - LICENSE and NOTICE good
Hi,
+1 (binding)
I checked:
- Incubating in name
- signatures and hash file fine
- DISCLAIMER exists
- LICENSE and NOTICE good
- code in release candidate matches code in version control
- No unexpected binary files
- Source files have correct header except one which has been fixed.
Thanks,
Just
Hi,
One issue I see with the instructions script is that you are asking people to
download it from head, this may make it hard to verify old releases or may give
different results during the voting process if changes are made. It may be
better to package the verifying script inside the release
Hi Dave,
Thanks! I’m glad Bertrand has been a help. OpenWhisk is similar to Sling in
that there are a number of repositories and release artifacts.
Regards,
Dave
> On Apr 22, 2019, at 3:14 PM, David P Grove wrote:
>
>
>
>
> On 2019/04/22 19:09:36, Dave Fisher wrote:
>> Hi -
>>
>> I am co
We do still need one more binding +1 vote from an IMPC member to be able to
close this vote and finally make this release.
If someone would be willing to either use the rcverify.sh script we use in
the OpenWhisk project as described below or otherwise check the artifacts
at
https://dist.apache.o
Justin Mclean wrote on 04/25/2019 10:41:28 PM:
>
> Hi,
>
> > If that URL was missing what where people actually voting on?
> Looking at the vote thread on the dev list it seem it was a GitHub hash??
>
> Can anyone answer this?
Per the original dev list vote email [1]
> You can use this UNIX s
Hi,
> If that URL was missing what where people actually voting on? Looking at the
> vote thread on the dev list it seem it was a GitHub hash??
Can anyone answer this?
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr..
Hi,
> The vote remains open. Or I can cancel the whole thing are start over if
> you want the URL in the email.
No need to cancel just leave it open.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apach
Justin Mclean wrote on 04/22/2019 05:59:24 PM:
>
> > The voting is now closed. The vote has passed with 3 +1 binding votes
from
> > Matt Sicker, Bertrand Delacretaz, and Justin Mclean and no +0 or -1
votes.
>
> Sorry but no it didn’t as I didn't vote +1 on the release.
>
Apologies, I misread
On 2019/04/22 19:09:36, Dave Fisher wrote:
> Hi -
>
> I am concerned about an overly automated release process. Please explain
what the role of the Release Manager is in your process? How does the
release manager sign these automatically generated artifacts? How are
release artifacts moved from
Hi,
> The voting is now closed. The vote has passed with 3 +1 binding votes from
> Matt Sicker, Bertrand Delacretaz, and Justin Mclean and no +0 or -1 votes.
Sorry but no it didn’t as I didn't vote +1 on the release.
Thanks,
Justin
---
Hi,
> We've been automating more of our release process (including generating the
> call-to-vote email) and in had streamlined out the list of URLs from the
> call-to-vote email.
If that URL was missing what where people actually voting on? Looking at the
vote thread on the dev list it seem i
The voting is now closed. The vote has passed with 3 +1 binding votes from
Matt Sicker, Bertrand Delacretaz, and Justin Mclean and no +0 or -1 votes.
As corrected by Justin in the voting thread, the URL for the artifact being
voted on was [1] ( with asc/sha512 of [2] and [3]). Apologies for th
Hi -
I am concerned about an overly automated release process. Please explain what
the role of the Release Manager is in your process? How does the release
manager sign these automatically generated artifacts? How are release artifacts
moved from https://dist.apache.org/repos/dist/dev/incubator
Hi,
Yes the artifact being voted on was [1].
We've been automating more of our release process (including generating the
call-to-vote email) and in had streamlined out the list of URLs from the
call-to-vote email. From your feedback, it seems like that was not
appropriate. I will open an iss
Hi,
Can someone please confirm this is the case and the vote was not just on the
GitHub repo?
> Assuming the artefact voted on was [1].
>
> 1.
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.11.0-incubating-rc2/
Thanks,
Justin
--
Hi,.
Assuming the artefact voted on was [1].
I checked:
- Incubating in name
- signatures and hash file
- DISCLAIMER exists
- LICENSE and NOTICE good
- No unexpected binary files
- Source files have correct header except [2]
This file [2] has an incorrect header [3], please fix for the next rel
Hi,
It unclear what is being voted on here, please post a link to the actual
artefacts being voted on not the GitHub repo.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional comma
While running the verification script I got an error..
$ ./rcverify.sh openwhisk-composer 'OpenWhisk Composer' 0.11.0-incubating
rc2
rcverify.sh (script SHA1: 80DC 4134 B419 D699 1E19 9BBC 847A E346 EB63
57D1)
working in the following directory:
/var/folders/vw/1bd7pypn3qn295bdyvqrbx4c
We need 1 more binding +1 vote on this release to proceed. Thank you for your
help.
--dave
On 2019/04/08 17:32:05, "David P Grove" wrote:
>
>
> The Apache OpenWhisk community has voted to release Apache OpenWhisk
> Composer (incubating) version 0.11.0.
> Apache OpenWhisk Composer is a progr
The Apache OpenWhisk community has voted to release Apache OpenWhisk
Composer (incubating) version 0.11.0.
Apache OpenWhisk Composer is a programming model for composing cloud
functions built on Apache OpenWhisk. This will be the third Apache Release
of OpenWhisk Composer.
The voting thread ca
22 matches
Mail list logo
