Moving my vote to the right thread.

+1
Downloaded the source, verified signatures and ran some unit tests.

On 5/21/18, 3:09 PM, "Venkat" <[email protected]> wrote:

    +1
    
    Checked sigatures/hashes.    The archive name does not have  apache
    prefix -  already raised in this vote thread.
    
    Built and ran tests - there were some timeouts running ratis servers
    tests in a couple of runs (could be environmental issues) ,  but all
    tests passed in a subsequent execution.   .
    
    Venkat
    
    On Mon, May 21, 2018 at 1:48 PM, Jakob Homan <[email protected]> wrote:
    > +1 (binding)
    >
    > * Checked sigs/hash
    > * Spot checked tests
    > * Checked on the copyright year (thanks)
    > * Built per instructions, which worked this time.
    >
    > Nit:
    > * Didn't notice this last time, but the artifacts should
    > apache-ratis-incubator-0.2.0-src.tar.gz rather than
    > ratis-incubator-0.2.0-src.tar.gz.  The IPMC will likely let this slide
    > until the next release.
    >
    > -Jakob
    >
    >
    > On 18 May 2018 at 11:20, Tsz Wo Sze <[email protected]> wrote:
    >> Thanks Marton.
    >>
    >> We can generate mds by "gpg --print-mds <file>".  See also
    >> ratis/dev-support/make_rc.sh
    >>
    >> Tsz-Wo
    >>
    >> On Fri, May 18, 2018 at 5:49 AM, Elek, Marton <[email protected]> wrote:
    >>> I just found (thanks to RATIS-241) that the previous release provided 
mds
    >>> files as checksum. So I just added mds files as well (you can see that 
the
    >>> sha hash is the same).
    >>>
    >>> But as I don't know any easy method to verify the mds files [1] I would 
link
    >>> the sha-512 from the ratis web page.
    >>>
    >>> Please check the release candidate and vote.
    >>>
    >>> Thanks
    >>> Marton
    >>>
    >>> [1]
    >>> 
https://superuser.com/questions/1117048/how-to-verify-checksum-in-a-mds-file-format
    >>>
    >>>
    >>>
    >>> On 05/16/2018 11:50 PM, Elek, Marton wrote:
    >>>>
    >>>>
    >>>> Hi all,
    >>>>
    >>>> I'd like to restart the vote to release Apache Ratis (incubating) 
0.2.0 as
    >>>> we fixed all the previously discussed issues.
    >>>>
    >>>>
    >>>>
    >>>> This is the second incubator release and it includes more than 120
    >>>> improvements and fixes since the previous 0.1.0-alpha release. This is 
the
    >>>> first release
    >>>> which includes a binary package with ready to use example project.
    >>>>
    >>>> All distribution packages, including signatures, digests, etc. can be
    >>>> found at:
    >>>>
    >>>> https://dist.apache.org/repos/dist/dev/incubator/ratis/0.2.0/rc1
    >>>>
    >>>> Staged artifacts can be found at:
    >>>>
    >>>> https://repository.apache.org/content/repositories/orgapacheratis-1004
    >>>>
    >>>>
    >>>> This release has been signed with PGP key 0EE79B28, corresponding to
    >>>> [email protected], which is included in the repository's KEYS file
    >>>> (https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS).
    >>>>
    >>>> This key can be found on keyservers, such as:
    >>>>
    >>>> http://pgp.mit.edu/pks/lookup?op=get&search=0x0EE79B28
    >>>>
    >>>> Or in the apache phonebook:
    >>>>
    >>>> https://people.apache.org/keys/committer/elek.asc
    >>>>
    >>>>
    >>>> The release candidate has been tagged in git with ratis-0.2.0-rc1
    >>>> (bd234f25c29e918ad3db88bfedcc2d6931221a3e)
    >>>>
    >>>> https://github.com/apache/incubator-ratis/releases/tag/ratis-0.2.0-rc1
    >>>>
    >>>>
    >>>>
    >>>> Please review and vote. The vote will be open for at least 72 hours.
    >>>>
    >>>> If the vote passed, the second stage vote will be called on the Apache
    >>>> incubator mailing list to get approval from the Incubator PMC.
    >>>>
    >>>>
    >>>>
    >>>>   # Review/testing
    >>>>
    >>>> You can check the usual requirements of an apache release:
    >>>>
    >>>>   • Signatures
    >>>>   • Checksums
    >>>>   • License and notice files
    >>>>   • Disclaimer file (incubator!)
    >>>>   • Build the project from the source code package (mvn clean install
    >>>> assembly:single -DskipTests=true )
    >>>>   • Licence headers
    >>>>
    >>>> The binary papckage can be smoketested with:
    >>>>
    >>>> ./examples/bin/start-all.sh
    >>>> ./examples/bin/client.sh assign --name a --value 2
    >>>> ./examples/bin/client.sh get --name a
    >>>>
    >>>>
    >>>>
    >>>> Starting with my vote: +1
    >>>>
    >>>> Thanks,
    >>>> Marton
    
    

Reply via email to