I ran some basic checks and things look OK here. As far as your public GPG key goes - please export your public key (gpg --armor --export y...@example.com > mykey.asc) you used to sign the release and email it to me so I can verify signatures of all the artifacts are valid.
In addition to that, I need to sign it and add it to the KEYS file ( https://www.apache.org/dist/libcloud/KEYS) which is used by the users to verify the origin and integrity of the releases (this is a blocker for the release). [+1] Release Apache Libcloud 2.4.0 Thanks again for working on this release! P.S. Thread title says "2.3.0" instead of "2.4.0", but this shouldn't be an issue because "2.4.0" is mentioned in all other places where it matters :) On Sat, Oct 27, 2018 at 9:04 AM Quentin Pradet <quentin.pra...@gmail.com> wrote: > This is a voting thread for Libcloud 2.4.0. It includes all the > changes from trunk which have landed there since v2.3.0. > > The most notable change is Python 3.7 support. There is also a new > Scaleway driver, and various improvements, mostly for compute drivers. > > Full list of changes can be found at > > https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-apache-libcloud-240 > > Release artifacts can be found at > http://people.apache.org/~quentinp/libcloud/2.4.0/ > > Not sure how to send my GPG key! > > Please test the release and post your votes. > > +/- 1 > [ ] Release Apache Libcloud 2.4.0 > > Vote will be open until November 2nd. >
