[RESULT][VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-31 Thread John McCane-Whitney
Hi, Re: Apache Milagro (incubating) Crypto-C V2.0.1 Release Tag: https://github.com/apache/incubator-milagro-crypto-c/releases/tag/2.0.1 The vote to release the above is now closed and has passed with 3 x +1 binding votes: -Justin McClean -Nick Kew -Jean-Frederic Clere Vote thread:

Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-30 Thread jean-frederic clere
On 13/01/2020 12:25, John McCane-Whitney wrote: Hi, This is a call to vote on the release of the Apache Milagro (incubating) Crypto C Library v2.0.1 The Apache Milagro (incubating) community has voted to approve this release with 5 x +1 votes. The vote result thread can be found here:

Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-30 Thread Nick Kew
> On 17 Jan 2020, at 14:41, John McCane-Whitney wrote: > > Hi Justin/Nick, > > Thanks for clarification around the chain of trust - of course we're happy to > follow further guidance if required. OK, it would be good for Milagro folks to get yourselves into the Strong Set. And for the ASF

Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-17 Thread Justin Mclean
Hi, > Also, just to clarify re: the signature file - it's currently being staged in > the relevant subdirectory here: > > https://dist.apache.org/repos/dist/dev > > When/if this vote passes, we'll move it to: > > https://dist.apache.org/repos/dist/release > > From where it automatically gets

RE: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-17 Thread John McCane-Whitney
ure. We believe this is the Apache Way, but also happy to amend if required. Regards, John > -Original Message- > From: Justin Mclean > Sent: 16 January 2020 20:28 > To: general@incubator.apache.org > Subject: Re: [VOTE] Release Apache Milagro (incubating) Crypt

Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-16 Thread Justin Mclean
Hi, > Couple of apparent problems with the PGP signature: > > (1) Shouldn't it be visible from the download page? It is [1] (apache-milagro-crypto-c-2.0.1-incubating-src.tar.gz.asc) > (2) I wasn't able to establish a chain of trust. That a nice to have not a requirement for a release. And

Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-16 Thread Nick Kew
On Mon, 13 Jan 2020 11:25:35 + John McCane-Whitney wrote: > Hi, Apologies for the round tuit coming so late here. > > This is a call to vote on the release of the Apache Milagro > (incubating) Crypto C Library v2.0.1 > >

Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-15 Thread Justin Mclean
Hi, > Most of the author tags are leftover from the initial software grant from > CertiVox and have no IP consequences. All good changing my vote to +1 (binding). For future releases I’d leave the ones that where in there before the donation and just remove the ones added since. > Please can

RE: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-15 Thread John McCane-Whitney
; From: Justin Mclean > Sent: 15 January 2020 02:04 > To: general@incubator.apache.org > Subject: Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1 > > Hi, > > Currently I’m -1 on this release due to the author tags, which may imply it > contains 3rd party c

Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-14 Thread Justin Mclean
Hi, Currently I’m -1 on this release due to the author tags, which may imply it contains 3rd party code, whose licenses not listed in LICENSE. There's probably an explanation for why they are there and if given I’ll change my vote. I checked: - incubating in name - signatures and disclaimer

[VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1

2020-01-13 Thread John McCane-Whitney
Hi, This is a call to vote on the release of the Apache Milagro (incubating) Crypto C Library v2.0.1 The Apache Milagro (incubating) community has voted to approve this release with 5 x +1 votes. The vote result thread can be found here: