Hi,

Apologies, but we've just found a small bug on MacOS.  We're fixing this and
I'll send out a new vote email shortly.

Regards,

John

-----Original Message-----
From: John McCane-Whitney 
Sent: 06 January 2020 10:29
To: d...@milagro.apache.org
Subject: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.0

Hi,

This is a call to vote on the release  of the Apache Milagro (incubating)
Crypto C Library v2.0.0 from the following repository tag:

https://github.com/apache/incubator-milagro-crypto-c/releases/tag/2.0.0

OVERVIEW:
   
Apache Milagro Crypto C 2.0.0-incubating is the second Apache Software
foundation release of this library. 

There are two main additions to the library and they both impact the API
hence the jump from v1.0.0 to v2.0.0:

Shamir's Secret Sharing (SSS) has been added to the library. There is also
functionality combining the existing BLS solution with SSS to enable
signature aggregation without revealing the secret key share. This change is
required by the Milagro DTA
(https://github.com/apache/incubator-milagro-dta) and will allow subsequent
releases of the DTA to be built from an official Apache release of the
crypto-c library.

The Paillier additively homomorphic cryptosystem has also been added to the
library which will be required by subsequent releases of the DTA to enable
Multi-Party Computation of cryptocurrency wallet addresses and subsequently
to create transaction signatures for these wallets.

The library now also supports Python 3 and formulas in the documentation are
now rendered using MathJax.

Please see the README (https://github.com/apache/incubator-milagro-crypto-c)
for build/test instructions, a list of contributors and guidelines on how to
contribute yourself.  The README also includes instructions on how to build
the documentation, and the online version of the documentation
(http://milagro.apache.org/docs/amcl-c-api/) will be updated once the
release is complete (as will the download page on the same site).

RELEASE:

The repo has the required DISCLAIMER, NOTICE and LICENSE file in its root
directory.  All source files have the appropriate license header.  No
binaries are included in this release.

I have successfully built and ran the tests as per the instructions in the
README on Ubuntu, Fedora, MacOS and Windows

The compressed archives from this release along with a SHA512 checksum, PGP
signature and PGP key file are being staged here:

Source code archive:
https://dist.apache.org/repos/dist/dev/incubator/milagro/apache-milagro-cryp
to-c-2.0.0-incubating/apache-milagro-crypto-c-2.0.0-incubating-src.tar.gz   
SHA512 checksum:
https://dist.apache.org/repos/dist/dev/incubator/milagro/apache-milagro-cryp
to-c-2.0.0-incubating/apache-milagro-crypto-c-2.0.0-incubating-src.tar.gz.sh
a512   
PGP Signature:
https://dist.apache.org/repos/dist/dev/incubator/milagro/apache-milagro-cryp
to-c-2.0.0-incubating/apache-milagro-crypto-c-2.0.0-incubating-src.tar.gz.as
c   
Keys: https://dist.apache.org/repos/dist/dev/incubator/milagro/KEYS   

This round of voting will remain open for at least 72 hours.  All committers
are welcome to vote.  3 x [+1] votes are required to move forward.  If the
vote is passed, a second vote will be requested from the IPMC.  

Please vote:   
[+1] Signatures and checksums verified. Releases built and tests completed.
Release approved.   
[0] No opinion   
[-1] Release rejected - please include your reasoning.   

Many thanks to all the contributors,   

Regards,   

John McCane-Whitney
Director of Product at Qredo Ltd
T: +44 7966 490687
Kemp House
152 - 160 City Road
London
EC1V 2NX
https://qredo.com
Qredo Ltd is a limited company registered in England and Wales (registered
number 7834052). This e-mail and any attachments are confidential, and are
intended only for the named addressee(s). If you are not the intended
recipient you may not copy, disclose to anyone else or otherwise use the
content of this e-mail or any attachment thereto and should notify the
sender immediately and delete them from your system.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to